My Quest 3 is having issues detecting/creating boundaries since I updated to v63 (Same room / same lighting conditions) It starts off with incorrectly detecting the floor level (which wasn't a problem before) so I have to resort to manually setting the boundary and manually setting the floor level. It is also having trouble suggesting a boundary when I ask it to (after manually setting the floor level) so I also have to draw the boundary manually. When I select the 'suggest boundary' option, it keeps scanning and drawing polygons but they keep disappearing so the boundary lines keeps shifting and re-adjusting.
Is there a known issue? Any suggestions on things to try to resolve this?
Update: I tried boundary again yesterday and it seems to be working fine now. I didn't change any settings but I have seen the headset mention that it was applying update when I was shutting it down a couple of days ago (I was on v63 before and am still on v63 though... so I'm not sure if there are minor/patch version updates).
Either way, I've tried it twice yesterday and it worked fine both times.
Are there minor version updates on the Quest 3 ? is it possible that one of these updates fixed the issue ?
UPDATE: I set the floor level through settings and that seems to have addressed the floor level issue.
As for detecting the boundary, that still doesn't work but I found that if I kneel to bring my head/headset closer to the floor then it works better. if I'm standing up (I'm 5'8") it seems to only scan/detect the floor around me in a 2.5 ft radius, nothing outside of that.
Hey @Fadius77! Thank you for explaining the troubleshooting steps you have already taken. Have you tried to clear the boundary history? If not, here are the steps to clear that boundary history:
Press the Meta/Oculus on your right Touch controller to pull up your universal menu.
Hover over the clock on the left side of the universal menu. When Quick Settings appears, select it to open the Quick Settings panel.
Select Settings in the top right corner.
Select Boundary from the left menu.
Select Clear Boundary History
Also, a hard reboot should clear the device cache. Let us know if it was helpful. We would love to hear back from you!
If you're the author of a thread, remember to mark a reply as the Accepted Solution to help others find answers!
I have already tried clearing the boundary history and the hard reboot (Had gone through the pinned discussion about boundary issues other people were having). Unfortunately none of that helped. I have to crouch to get the headset near the floor (and turn around) for the boundary to take shape (from a circle). Even then, I have to manually adjust it because it wont reach the edge of the play area.
To be clear, this is not an intermittent issue. I have it every time I need to re-create the boundary. Very strange.
Hello again @Fadius77, thank you for updating us on your continued troubleshooting efforts. Just to make sure we exhaust all of our possible solutions we have a few more things to try. Can you make sure tracking is ticked on in your headset? Here's How you do that:
Click on the clock on the left side of the universal menu
Select Settings
Select System from the Settings panel
Select Headset Tracking from the left side panel
Make sure Headset Tracking is ticked
We are committed to figuring this out with you, so let us know if this helped!
If you're the author of a thread, remember to mark a reply as the Accepted Solution to help others find answers!
Yes headset tracking is enabled and set to 'auto'. FWIW, when I move my body/head, the menus don't move with me, which I believe also confirms that headset tracking is working...
Hey there @Fadius77! Thank you for providing us with that information, and just to be clear, are you saying tracking is working? Also, can you verify whether you're in a stationary boundary setting or a room-scale boundary setting?
If you're the author of a thread, remember to mark a reply as the Accepted Solution to help others find answers!
Update: I tried boundary again yesterday and it seems to be working fine now. I didn't change any settings but I have seen the headset mention that it was applying update when I was shutting it down a couple of days ago (I was on v63 before and am still on v63 though... so I'm not sure if there are minor/patch version updates).
Either way, I've tried it twice yesterday and it worked fine both times.
Are there minor version updates on the Quest 3 ? is it possible that one of these updates fixed the issue ?
Hello @Fadius77! That's awesome to hear, and it is definitely possible that that could've taken place. To stay up-to-date on the latest software releases, check out this blog. In this article, it gives steps on how to update your Meta Quest 3, and it also has a link to the latest software release notes. We are so happy to hear your issue has been resolved. Just know we are always here to help!
If you're the author of a thread, remember to mark a reply as the Accepted Solution to help others find answers!
