06-13-202406:22 AM - last edited on 06-14-202407:32 AM by TheLegend27
Hello all, I recently updated the Quest3 and the latest version of the standard browser freezes after a minute when I visit an immersive FrameVR environment in 360 like https://framevr.io/chatterdale
What happens... I first visit the environment in 2D, then I click on the headset icon in the right bottom corner. Then I can walk around in 360 immersive. After 1 minute it stutters and freezes. I go out of 360 mode, see a white browser screen, I refresh it and then it mentions "This page requires WebGL to run. Make sure you are on the latest version of your browser and that hardware acceleration is enabled in its system settings."
It worked fine in the past, but now it is terrible. We are using 22 Quest 3 headsets for research in the educational field and this is very disappointing. We can't use them now.
Hey there, @nixward! We see that you are having issues with the Meta Quest Browser freezing in 360vr immersive experiences. We understand how this can disrupt an amazing VR experience, so we would love to take a closer look into this to get you back to a smooth VR experience. That being said, listed below are some troubleshooting steps we'd like for you to try to see if they do the trick for you.
Please try clearing your cookies and cache in your browser.
Try using your headset closer to your router.
If your router has a dual-band feature, please disable it. That way, your headset can be on the same channel as the headset's moving channels, which can impact the Wi-Fi signal.
Try connecting your Meta Quest to a different network, whether that be a hot spot or another Wi-Fi.
If, after trying the following, you are still experiencing issues with the browser, please don't hesitate to reach out to us again so we can continue to look into this issue for you. We look forward to hearing back from you soon!
If you're the author of a thread, remember to mark a reply as the Accepted Solution to help others find answers!
Hello again, @nixward! We wanted to check in on you to see if you still need help with this issue you are currently having with the Meta Quest Browser error or if there is anything else we can help you with. If so, please feel free to reach out to us again so we can continue to help you!
If you're the author of a thread, remember to mark a reply as the Accepted Solution to help others find answers!
I cleared the cookies, I checked my WIFI, I am already close to the router, tried a different WIFI transmitter, I even did a complete factory reset. Still the problem occurs. Somehow WebGL stops on the browser and will not start again, only after I have restarted the Headset.
Thank you for getting back with us, @nixward! Are you only experiencing this when you visit the website you mentioned previously, or is it happening with other websites you visit as well? Please let us know so we can get a better understanding and know what steps are best to take next. We can't wait to hear back from you soon!
If you're the author of a thread, remember to mark a reply as the Accepted Solution to help others find answers!
Well, I have never really tried any other website that has 360 immersive mode, so I do not know where to begin. I will try some tomorrow, it is getting late now overhere and it is weekend.
I tested it on another website called vrland.io on this environment; https://vrland.io/ANTO5M/chatterdale but that did not load at all in VR mode. And I tested the FrameVR again on another environment that I created https://framevr.io/fectio there it was running fine, but when I switched to https://framevr.io/chatterdale the problem was there again. It stutters and freezes. I tested also with a Quest2 and that was ok.
I also asked FrameVR to have a look at it but they say that they did not change anything on VR mode in the past weeks. It was running fine then.
Hey @nixward, thank you for following up! We know you're eager to resolve this issue, and we truly appreciate your patience. However, these are great concerns to share with our engineering team. Reporting this bug ensures that your feedback is brought to our attention and helps our engineering team quickly start the investigation process. Please remember that reporting a bug is one-way only, meaning you will not get a direct reply to your report.
We hope you found this helpful. If you have any further questions, please feel free to let us know!
If you're the author of a thread, remember to mark a reply as the Accepted Solution to help others find answers!
