I’m working on a VR project again after a while, and I’m using the Quest 2 as a test device. I’ve encountered an issue where the controllers are not showing up after first entering VR mode. The same issue occurs in both the VR Kit and WebXR VR Lab. Has anyone else experienced this problem?
Am I really the only one experiencing this issue? If it’s working fine for others, could someone please leave a comment? At least then I’ll know there’s a problem with my device.
I took my old Quest 2 and updated it for a controller test. I tested the »WebXR VR Lab« and »WebXR Tracked Controllers« examples from the PlayCanvas tutorials. On the first attempts opening the scenes the controllers did not show neither did buttons nor triggers react. I remembered to have had such issues before with PlayCanvas and opened and closed the scenes alternatively some times and after some trials the controllers did show and buttons/triggers worked.
You may try to switch scenes several times and check if the controllers are shown with your Quest 2.
Thank you so much for sharing your experience. As you mentioned, I also tried opening and closing the browser or tabs, but it didn’t work for me. Although the Quest 2 is an older device model, it was sold at a reasonable price and I believe many people are still using it (though I don’t have any statistical evidence, haha).
The best solution I could think of to suggest to my client is to enter VR mode, then press the power button to put the device into sleep mode and wake it up again. Doing this always makes the controllers appear.
I suspect this issue may be caused by a Meta OS or browser update, so I don’t want to blame the PlayCanvas team. That said, it would be really helpful to get some feedback from the PlayCanvas team — especially because I believe WebXR is one of the core values of PlayCanvas.
As you’ve tested older content, which was not changed and experienced an issue, then this is definitely related to Meta Browser updates, that they might have broken something.
Especially taking into the account that restarting a device - fixes an issue.
With the nature of their development, they do break some stuff sometimes, but they fix it usually within reasonable time.
A good thing would be is to use “panic button” - press oculus button 5 times quickly, it brings bug report window, and there you can specify a browser and webxr. Make sure you mention that content did not change, and used to work, but stopped now. So they can know that it is a regression on their side.
If they do change that they don’t fix, but we can fix on our side (some workaround due to change of WebXR APIs behavior changes, or something like that), I sometimes make small PR’s to PlayCanvas Engine with workarounds, they should be reasonable though.