Virtual Reality

1931 readers

20 users here now

Virtual Reality - Quest, PCVR, PSVR2, Pico, Mixed Reality, ect. Open discussion of all VR platforms, games, and apps.

founded 1 year ago

MODERATORS

[email protected]

Quest 3 controllers disconnect and won't reconnect until restarting the whole system. (yiffit.net)

submitted 3 months ago by [email protected] to c/[email protected]

2 comments fedilink hide all child comments

Just curious if anyone else with a Quest 3 (or even 2 I guess) is having this issue. Seems to have only started after v68 dropped. Is there a fix? The patch notes said I should be able to handle the connection from the system menu, but there's nothing to force them back on or turn them off; it's the same shit that's been in there since I got the thing.

top 2 comments

sorted by: hot top controversial new old

[–] [email protected] 2 points 3 months ago

Quest 2 here and never experienced anything like this.

I’ve had slight issues where the controllers don’t seem to connect at first but after playing around with them for a while (just moving them around over and over for under a minute) they are recognized.

I do have hand tracking on too which I think you should use as a backup so you can still access in case you need to navigate menus.

I had an issue with one controller that admittedly was probably my fault after hitting a wall too hard. The controller wouldn’t turn on anymore and I filed a support case with Meta and they sent me a replacement controller at no extra cost from me. They do ask for your Quest’s serial number which is how they know if it’s still under warranty which I’m sure yours still is.

[–] [email protected] 1 points 2 months ago

I’ve had a similar issue with Q3 and the pro controllers (the same thing happened with the Q3 controllers as well). The reset view bottom will work but nothing else. Restarting fixes it but my current work-around it to put the controllers down and what for hand tracking to start. Then I can pick up the controllers press some buttons and they’re back. It’s been an issue for many versions now.