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
- UI Overlay Image gets darker on each Camera when multiple Cameras are used
- Assertion failed on expression: 'scriptedImporterClass == SCRIPTING_NULL error when opening the standalone profiler window
- Disabled assets in Import Unity Package window aren't tracked but count as being selected by user
- [Windows] Crash on GetManagerFromContext when video is playing and creating High Definition 3D Projects after FMOD failed to switch back to normal output Error appeared
- GC Alloc produced when adding items to MultiColumnListView with Auto Assign Binding
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