Search Issue Tracker
Fixed in 5.3.4
Votes
1
Found in
5.2.4p1
Issue ID
756820
Regression
No
[VR] In Play mode moving input focus away then back to the Editor makes VRSettings.enabled true
In a VR-enabled scene with the Oculus Rift connected and VRSettings.enabled false, you can make VRSettings.enabled become true simply by clicking in another application (such as your web browser) then clicking back in the Unity Editor. Changing application input focus like this should have to effect on VRSettings.enabled.
I set the Severity high because this is one of the use cases defined by Unity VR devs (test G.2) in the Oculus Integration Verification Tests.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Mobile] Developer Console does not appear when an error is thrown
- [HDRP] Game view renders artifacts when Camera's Component "Post Anti-aliasing" is set to "TAA" and Dynamic Resolution's "Forced Screen Percentage" is changed
- A deactivated Prefab's name color becomes white when a GameObject in the scene is deactivated
- The Game view becomes blank when using Frame Debugger with MSAA and Texture binding enabled in Play Mode
- NullReferenceException is thrown when changing the Inspector preview selection
Add comment