Feature Request / UX Discussion: Separate Immersive App Control UI From 2D Apps
``` I’d like to discuss an issue with how immersive apps interact with running 2D apps when switching contexts using the Meta button on Quest. The problem is not the immersive app itself, but the 2D control window that appears for immersive apps (the window with Resume, Close, and other controls). When this window is shown, it is treated like a normal 2D app, and its appearance often causes currently running 2D apps to be minimized, closed, or refreshed. This behavior makes multitasking unreliable and forces users into specific app-launch sequences just to avoid losing state in their 2D apps. Proposed Behavior Change The idea is that the immersive app control window should not behave like a standard 2D app and should not interfere with other running 2D apps. Specifically: - Showing the immersive app’s control window should not minimize, close, or replace existing 2D app windows - The immersive app control UI should exist in a separate system layer, not the same layer as user-launched 2D apps - Running 2D apps should remain exactly as they are when the immersive app control UI appears - Access to Resume, Close, and related immersive controls should be possible without disrupting active 2D workflows - Ideally, immersive app controls could be accessed via a dedicated icon, overlay, or system-level panel rather than a standard 2D window In short: Viewing or interacting with immersive app controls should not be treated as “launching a 2D app.” Why This Matters - Prevents active 2D apps from being kicked out or refreshed - Makes switching between immersive and 2D contexts predictable - Improves productivity and multitasking - Reduces frustration caused by forced app restarts - Allows immersive apps to coexist cleanly with 2D workflows This could be implemented as an optional setting or as a revised default behavior for immersive app control UI, without removing any existing functionality. I’m interested to hear if others experience the same issue and whether separating immersive app controls from the 2D app system would improve overall usability. ```
V81 Bug? Menu won't appear when turning on Quest 3
Recently got access to the PTC for V81, and all seemed fine. But I turned on my Quest 3 and the menu won't appear at all, even after holding down the right controller button and even testing it with hand tracking... HOWEVER... This issue seems to be hit and miss. When I was ready to give up and do a factory reset, turned my headset on and randomly the menu appeared again. It sometimes disappears if I leave my headset on standby for a while, and sometimes disappears if I turn it off and on, and sometimes just randomly appears. Is this a common bug or does anyone have any potential fixes? I have tried launching games from the app and it did work one time, despite it showing the launch and install on headset, even when the app is already installed. I understand it's a beta and could be a bug but wondering if it's just me. Also, when the menu doesn't appear, if I were to hold the power button, it just shuts down, it doesn't give me the option to reset or anything. Any help greatly appreciated 😁