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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
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