v85/v2.1.1034 Passthrough Loop
I put this on Reddit also posting here in case it's a bugged update?
Ok so this is my issue after Feb 27th v2.1.1034 Update:
1. The Problem: v85/v2.1 "Passthrough Loop"
AI advises: This specific flickering issue (cycling between Home and Passthrough) is a known bug associated with the v85/v2.1 update. It appears to be tied to a conflict between the new "Navigator" UI and the headset's tracking/boundary service.
Why it happens: The OS is essentially "crashing" the immersive home environment and falling back to Passthrough as a failsafe, then attempting to reload the environment again.
The "Double Tap" Fix: Manually forcing Passthrough works because it tells the OS to stop trying to render the immersive environment, which bypasses the crash loop.
2. Process: Meta Software Update Tool
Attempted resolution: I proceeded with the Sideload Update - update successfully loaded but....
Issue persists > Goto 1. LOL.
So right now I will perhaps await the next meta update which may fix my problem before attempting a factory reset and linking accounts up etc...
> If I manually enable pass through, I can get to quick access menus etc. so could update from there when next update available.
> I haven't tried - PC Wired Link yet, so hopefully can get to MSFS SIM I use.
> For the moment, standalone usage is a no go.
Note:
> I do have WhatsApp on the Quest which I know is active and in past updates I've seen this crashing in the background via notifications message things popping up. That has not happend this time but I think the Q2 may be struggling in my case as per above, something is causing it to crash.
> I recently starting testing the 3rd party Immersive App on Q2 with it's version of remote desktop and virtual second monitor feature it can use with a laptop, as native Meta RD can't do that.....but I'm assuming nothing is running in BG with that app if it's not being used......
META / Anyone - any thoughts?
I've just installed update: v2.1 5210......150, this has resolved my problem of UI crashing within the home environment, unless passthrough was enabled manually (or by default at boot which it started to do by itself), YeeHaaa...