Search Issue Tracker
Won't Fix
Votes
1
Found in [Package]
1.4.1
1.4.2
Issue ID
OXRB-59
Regression
No
XRDisplaySubsystem.displayOpaque is true when deployed on HoloLens 2
How to reproduce:
1. Open the attached project "URPBlit2021.2.17.zip"
2. Build And Run for HoloLens 2
3. Open HoloLens 2 Windows Device Portal
4. Open System>File Explorer>User Folders>LocalAppData>URPBlit2021_1.0.0.0_arm64__pzq3xp76mxafg>TempState>UnityPlayer.log
Expected results: "displayOpaque" is false
Actual results: "displayOpaque" is true
Reproducible with: 1.4.1 (2020.3.35f1), 1.4.2 (2020.3.35f1, 2021.3.4f1, 2022.1.4f1, 2022.2.0a17)
Could not test with: 2019.4.40f1 (OpenXR unavailable)
Reproducible on: Windows 10
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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Resolution Note:
This is likely caused by checking displayOpaque in Start() when the underlying device hasn't yet finished startup and we don't yet know if the display is opaque or not.
You can follow the pattern here to find out displayOpaque as early as possible: https://forum.unity.com/threads/how-can-i-get-actual-screen-resolution-of-vr-while-using-pc-streaming.1370292/#post-8655894