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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment