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
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
- White lighting artifact when a point light with a small emission range and "Hard Shadows" touches an object while a directional light with "Soft Shadows" and another point light are present
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