Search Issue Tracker
Fixed in 5.5.0
Votes
0
Found in
5.5.0a6
Issue ID
822487
Regression
Yes
VR support settings persist across Editor sessions but UI does not indicate actual setting
Changes made to the VR Support toggle in Player settings appear to not persist the next time you open the project and look at the toggle in the UI. But when you enter Play mode whether or not the scene actually appears in your VR headset does depend on how you set the VR Support toggle during your previous Editor session.
So, there are situations where VR Support behaviour does not match the VR Support toggle state in the Player settings UI.
This is a regression compared to Unity 5.4.0p1.
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
Add comment