Search Issue Tracker
By Design
Votes
3
Found in
5.4.0b19
Issue ID
800978
Regression
No
Cursor.lockState = CursorLockMode.Locked doesnt work with Native Oculus VR support
To repro:
1) Open Attached project
2) Open 'Scene' scene
3) Note that Oculus SDK is the supported SDK
4) Note that the Cursor Lock script forces the cursor lock setting to 'Locked'
5) Build and Run a Windows Standalone build
6) Observe that the cursor is not locked to the window [BUG]
Additional steps
7) Run the same scene in the editor. Note that that cursor is locked within the game view when run in the editor. [EXPECTED BEHAVIOR]
This IS a regression as it DOES NOT occur here:
Version 5.3.5f1 (958194880ab6)
Mon, 23 May 2016 21:49:30 GMT
Branch: 5.3/vr/oculus-1.4-updates
Comments (1)
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
- Crash on ExtractActiveCasterInfo when navigating the scene view in a project with specific lighting data
- Build Profile name increments when numeric suffix is removed from duplicate Profile name
- "Unrecognized block header in profiler data file, stopping deserialization" error is shown and no more profiler data is recorded when the Player is connected and profiler recording is enabled/disabled few times
- Shader error and warnings thrown when setting HDRP as an Active Target in Blank Shader Graph
- Visual Studio Code does not integrate with the project when the .slnx project is opened
phileday
Jun 26, 2016 17:13
I've discovered that if you click on the outside of the window and then back in again that the mouse becomes locked again. I've also notice that the OnApplicationFocus function returns false even though it is focused until you've done this.
I hope that helps.