Search Issue Tracker
Won't Fix
Won't Fix in 2023.1.X
Votes
0
Found in
2021.3.29f1
2022.3.7f1
2023.1.7f1
Issue ID
UUM-45918
Regression
No
[XR] Hiding the built Player Window stops HMD from rendering
Steps to reproduce:
1. Create a new project or a VR template
2. Add the attached script "HideUnityWindow.cs" to a GameObject
3. Connect Oculus Link to Quest 2
4. Build a Standalone Player
5. Observe in the headset how the view no longer renders or begins to flicker
Expected results: Hiding the built Player Window does not stop HMD from rendering
Actual results: Hiding the built Player Window stops HMD from rendering
Reproducible in: 2021.3.29f1, 2022.3.7f1, 2023.1.7f1, 2023.2.0b4
Environment tested on: Windows 10
Notes:
-Issue is not reproducible in the Editor
-Only reproducible when building a Standalone Windows Player
-Issue reproduces with both OpenXR and OculusXR plugins
-Issue reproduces with Vulkan and Direct3D11
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- "Layer Palette Profile" Asset is automatically applied to the second Terrain but doesn't load any layers
- "Terrain Tools" shortcut conflicts with the Overlays shortcut by default
- Longer Shader Graph Property Reference names breaks VFX Graph Output Particle Node
- Inconsistent hotkeys in the Terrain tool with the "Terrain Tools" installed and not installed
- "DebugAllocatorMode" option changes when changed in another Editor instance
Resolution Note:
Using windows commands to disable the player window is not a supported use case or intended usage for XR in Unity.
Resolution Note (2023.1.X):
Using windows commands to disable the player window is not a supported use case or intended usage for XR in Unity.