This morning I tried to use Quest 3 in app that required boundary set. Boundary setup started, the usual, however I immediately noticed something off. With me standing in the middle of 4x5m empty floor it was suggesting stationary boundary (which was never the case before) and instead of nicely mapping the floor and boundaries like walls it struggled properly detecting the floor to "cover it" with these blue polygons.
I then tried to set it up manually - but after creating the roomscale boundary manually setting the floor level by touching with the controller, the obvious failure to detect depth/height properly caused all of my boundary to be red - reported as object in the boundary.
What's going on? Something screwed up in the recent update?
@KashMoneyBishh just a small update on my issue - it looks like when attempting to automatically create the roomscale boundary, it draws a circle around me - detecting possible stationary boundary - and the floor level detected (marked by blue triangle polygons ar-drawn on the flooe) is correct right under me, but 50cm from me it goes up about 20cm, and it never "Expands" like it used to before, to cover the whole flat area of the floor. I'll try to screenshot that when I get back for the reference.
Another update - looks like the headset / hardware is all right, as Mixed reality room mapping works perfectly - both floor, floor level, edges and walls, so I assume distance sensor is fine. Only the boundary seem no longer to detect possible roomscale boundary instead detecting floor ~25 cm too high and marking it as an obstacle. Cleaned boundary data, cleaned point data cloud, even factory reset the headset - issue persist.
03-01-202408:25 AM - last edited on 03-01-202408:34 AM by BlueberrieSmoothie
Thank you both for reaching out to us! We'd like to start by thanking you for being a loyal Meta Quest user, @Geezik , and by welcoming you to the Meta Quest family, @KashMoneyBishh! We understand that you both are experiencing difficulty setting your boundaries, but due to the potential of dealing with private and sensitive information, we kindly request that you both send us a private message.
Please make sure you sign in to the community before sending us a private message. To access our profile page, either select our name or clickhere! Next, click on 'Send Message' to send us a private message.
Additionally, the articles below have been proven to be successful in dealing with boundary issues in the past:
May you please try them and let us know if they work? We're looking forward to hearing from both of you soon. We hope you both have a great rest of your day!
If you're the author of a thread, remember to mark a reply as the Accepted Solution to help others find answers!
Hey, @Geezik and @KashMoneyBishh! We're here to make sure that both of you were able to send us a private message. We also want to ensure that there are no other issues we can assist either of you with. We appreciate both of your time and wish you both a wonderful day!
If you're the author of a thread, remember to mark a reply as the Accepted Solution to help others find answers!
Looks like after an update issue fixed "itself", so probably a bug, but I'm glad it's working now.
Still need help?
Did this answer your question? If it didn’t, use our search to find other topics or create your own and other members of the community will help out.
If you need an agent to help with your Meta device, please contact our store support team here.
Having trouble with a Facebook or Instagram account? The best place to go for help with those accounts is the Facebook Help Center or the Instagram Help Center. This community can't help with those accounts.
