10-29-2023 08:15 AM
There are a few glaring issues with the boundary problem currently on the Quest 3.
1. Disabling boundary in developer settings disables passthrough / mixed reality.
I have always used my Quests with boundary disabled entirely so I can utilize my space properly. With mixed reality it is even more useful to turn off boundary as you can see your space anyway - why are we forced to have this safety setting that only makes it more difficult to use your space?
In addition to this - the passthrough still actually does work for some things. In Virtual Desktop if you use their passthrough mode with boundary off in developer mode it still functions. The only issue with this is recording or taking photos through the Quest directly will cause all of the passthrough content to be blacked out.
Please allow us to capture mixed reality content with the boundary disabled!
2. Size limit for creating your own boundary.
I have a large warehouse space which I use for XR music events. It will not let me map out a large enough boundary area for my space. Can this size limit be removed or increased?
3. Microphone bugging out when exiting boundary
If you move even slightly outside of the boundary, sometimes it will mute your mic in the quest menu. Other times it doesn't mute in the quest menu, but just bugs out some other way. Fixes by walking out of boundary even further then back in after the UI / quest ambient sound has ended. This is extremely annoying and another reason to want to disable boundary.
4. Boundary ruining steam vr full body tracking
If you exit the boundary at all your orientation is reset on the headset which throws all of your trackers out of sync with the headset (using OpenVR-SpaceCalibrator method) requiring a full re-calibration.
TLDR - the boundary causes more issues than it is intending to solve and frequently bugs out. Let us disable it without blocking off mixed reality / AR. A boundary should not be required when you can see your real life space in passthrough.
11-06-2023 07:31 PM - edited 11-06-2023 07:39 PM
@hadean_uk wrote:In addition to this - the passthrough still actually does work for some things. In Virtual Desktop if you use their passthrough mode with boundary off in developer mode it still functions. The only issue with this is recording or taking photos through the Quest directly will cause all of the passthrough content to be blacked out.
try disabling the boundary in mqdh instead of in headset. if done while in a PT app it will continue to work for any other app until your headset resets. That said, my headset just updated to v59 and unless me using that bug carried over to a fresh restart after the update, it seems you can now separately toggle boundary and passthrough without needing this glitch. They seem to be mutually exclusive options now
for video capture you'll have to use scrcpy
11-28-2023 06:10 PM
Hey there, @hadean_uk! I saw your post, and I wanted to see if you still needed help with the boundary for your Quest 3. If the workaround that @lobotomyx provided isn't able to help, I recommend sending a private message to our support page, @MetaQuestSupport, or creating a case with our support team so this issue can be looked into further. I hope this information helps!
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.
Check out some popular posts here:
Getting Help from the Meta Quest Community
Tips and Tricks: Charging your Meta Quest Headset