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
- The name of the last string with a [TextArea] attribute is rendered in the top left corner of the Script Component when the CustomEditor class is used
- CPU & Memory usage increases over time when adding text to a Label
- Unity Version Control is not available on ARM Windows and fails with "expected ARM64 architecture, but was x64 architecture" error
- Play Mode is stuttering, and spikes are present in the Profiler when using the DX12 Graphics API with Unity Starter Assets
- [XR] Input is not recognized with multiple Meta Profiles After Device Standby/Resume When "Development Build" is Enabled
Add comment