(Resolved) Boundary not saved | Stuck in Passthrough

[adgilcan]

I have a brand new Quest 3. But it is giving me problems with boundary settings. 

often when I turn it on it comes up in pass through with no settings or way to get into the apps or settings. Rebooting eventually gets me a message to create a boundary which normally works but sometimes just results in a black screen and I have to reboot again. Once I am able to get a boundary set and commence whatever app I am wanting to play, it often comes up, after a couple of minutes, with “Boundary not saved” and I have to reboot again!  I have cleared all boundaries in settings in case there was a problem there but it didn’t change anything.

is there a fault with the headset?  I never have this problem with my Quest 2. 

Help would be much appreciated

D

[TheLegend27 · Accepted solution]

Not a Solution - Marking for visibility

 

Update:

I just got word from our internal team that they've successfully replicated the issue, and they're now working towards finding a fix. I appreciate everyone's patience while the team continues to look into possibilities, and I hope to have another update for everyone again soon!

Update 2:

After consulting with our engineering team again, it seems like this issue has since been resolved! For those still affected, it's recommended to restart your headset by powering it off, then powering it back on. If you still experience issues after that, I highly recommend reaching out to our support team! Alternatively, you can always PM @MetaQuestSupport for more assistance.

---------------------------------------------------------------------------------------------------------------

Hey everyone! I just came across this one and noticed you were all having very similar boundary related issues across the Quest line. I wanted to see if I was able to help out, along with collect a bit of info to see if our team can look into it.

Some of you may not be able to access this due to the inability to open up your menu, but for anyone else who's able to, try clearing your boundary history:

1. Press the Meta/Oculus on your right Touch controller to pull up your universal menu.
2. Hover over the clock on the left side of the universal menu. When Quick Settings appears, select it to open the Quick Settings panel.
3. Select Settings in the top right corner.
4. Select Boundary from the left menu.
5. Select Clear Boundary History

A hard reboot should clear the device cache, which should also clear up Guardian related issues. This one should be available for anyone to try:

1. Turn off your headset.
2. Hold the power and volume (-) button on your headset down simultaneously until the boot screen loads on your headset.
3. Use the volume buttons on your headset to highlight Boot Device and press the power button.
4. Use the volume buttons on your headset to highlight Yes and press the power button.

As for the info I'd like to get from everyone to bring to the team:

• Which device are you using?
  • Quest 2, Quest Pro, Quest 3?
• Do you remember which software version your headset was on?
  • V62, V63, V63 PTC?
• Which hardware version is your headset on?
  • Found in the Meta Quest Mobile app. Menu > Devices > Pick Device > Headset Settings > About Headset
• How long ago did this start happening?
• Has anyone found any successful workarounds?

•  

[Omesjo]

Glad to hear you found a fix.

This did not work for me unfortunately

[stealthc.face]

Hello, I'm just having the same problem with my device:

Which device are you using?
Quest 3

Do you remember which software version your headset was on?
63.0.0.397.363.579007360

Which hardware version is your headset on?
49872870063700510

How long ago did this start happening?
Today 03-27-2024

Has anyone found any successful workarounds?
Nope, tested all things posted.

Just PM'ed those details and the mac address to you.

[Das.Bearski]

A few of commenters remarked two potential work arounds:

Try to make your room as bright as possible, the boudary creation may then work.

Otherwise,

Try to go to developer settings, enable custom settings, and disable physical space features. 

I havent encountered the error so I can't confirm if either "fix" will work. 

Good luck!

[undlsclos3d]

I updated yesterday or this morning and now none of my passthrough or boundaries are working, causing the headset to ask me to reboot, I reboot and it asks me to reboot again. Nothing works on the headset. 500 dollar paperweight. 

[Das.Bearski]

Could you try one of these fixes?

Try to go to developer settings, enable custom settings, and disable physical space features.  

The other potential fix is to make your room as bright as possible.

I can't confirm if either fix works, as my headsets aren't experiencing the issue. But if you could "test and see" for me. That would be awesome.

[Mr.Hawk]

Quest 3 running on V63. Unable to set up boundry like 2 hours ago. Before that it was working fine left device idle for a while then change to seated location and tried to put stationary boundry that is when it started acting up. It says to fix you need to restart tried a couple of things nothing worked inculding clearing history and changing cloud settings. If you press continue menu does not pop up but you are in immersive mood unable to do anything except press power button and restart.

[Maccie25]

So today i turned on my oculus quest 2. And i couldn't make a new guardian. It says guardian not saved restart to solve. (translated by myself so it's not litteral) And when i restart it the same happens again and again. I tried searching how to turn the guardian off but i didn't understand. So does anybody know how to solve it?

[WhyDoIHaveAMetaAccount]

Same here, quest 2 on latest version (v63), started yesterday  and still doesnt work after a factory reset

[Omesjo]

Hello Das.Bearski,

Thanks for your suggestions.

I have tested your recommendations.

o Increasing the lighting did not resolve the issue.

o Enabling developer mode and disabling physical space features allowed me to at least use apps. No prompt asking me to set a boundary thus keeping me out of the bad loop.

I have tried enabling physical space again after to see if it had changed anything, however the issue was back.

So no solution, unfortunately.

However thanks for your workaround; that allows me to atleast get some use out of the quest while I wait / try untill the issue is resolved.