I'm experiencing some serious issues with my Quest 3s when using a secondary account via the "Add Account" feature. These issues only occur when using a secondary account. Since I only own a Quest 3s, I'm not sure if this issue also occurs on the regular Quest 3.
I'm currently on software version v74.0 (build 627280171100610) and don’t know if this problem existed in previous versions, as I bought my headset recently.
Problems I’m Encountering
1) Screen Flickering When Toggling the Overlay
When I turn the overlay menu on and off using the button, there’s about a 50-60% chance that the screen momentarily flashes black.
This issue happens consistently while using a secondary account.
I tried recording it in-game, but the flickering isn’t visible in the capture, so I had to film my display with my phone.
2) Severe Freezing and UI Glitches
This is the most frustrating issue. It happens when:
- I try to close a game via the overlay menu.
- I also try to simply close the overlay menu while it's open and the game is running. Instead of just closing the menu, the game completely crashes and returns to the main screen.
- Sometimes, this happens immediately after switching to the secondary account, without me doing anything else.
What Happens Next:
A few seconds after the crash, the system stutters briefly. Then, instead of the original overlay bar, a "ghost bar" (a duplicate UI bar) appears slightly lower on the screen.
A few seconds later, the screen goes dark, and the original overlay disappears, leaving only the ghost bar.
Once in this state:
1. The overlay button stops working entirely; no matter how many times I press it, the overlay menu doesn’t appear.
2. Looking in the mirror, my avatar switches to the main account’s avatar instead of the secondary one, but it’s stuck in a T-pose with no tracking.
3. The avatar’s torso is completely invisible to me.
4. The mirror UI becomes extremely laggy and glitchy.
I’d like to know if this is happening to other people on the latest software version or if it's just my device.
If others are experiencing the same problem, it might be a software bug. But if it’s just me, I might need to send my headset in for repairs.
Has anyone else run into this issue? Any fixes or workarounds?
