Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.3.5f1
Issue ID
1127670
Regression
No
XRSettings.enabled and XRSettings.supportedDevices return incorrect results when printing with InitializeOnLoad attribute
To reproduce:
1. Open QA attached project "XRSettingsCase.zip" on Unity with supported Android and UWP platform
2. Observe the console (or enter Play mode to print again)
Expected: XRSettings.enabled is printed as true, XRSettings.supportedDevices prints Standalone, Android and UWP XR settings
Actual: XRSettings.enabled is printed as false, XRSettings.supportedDevices prints Standalone and Android XR settings
Reproduced in: 2017.4.21f1, 2018.3.7f1, 2019.1.0b4, 2019.2.0a6
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (2019.2.X):
We are no longer updating 2019.2. If this is still an issue for you in 2019.3 or greater, please re-submit your bug.