Search Issue Tracker
Fixed in 2017.1.X
Votes
8
Found in
5.4.3p2
Issue ID
857999
Regression
Yes
Custom input stops working in Unity 5.5 when Cursor lock state is set to locked
Custom input module stops working in Unity 5.5 when Cursor lock state is set to locked.
To reproduce:
1. Open example in Unity 5.4.3f1
2. Enter play mode.
3. Hover the cursor over one of the cubes.
Looking at any of the cubes will turn that cube red.
4. Repeat these steps with Unity 5.5.0f3
Moving the mouse still works, but when hovering over cubes they stay white.
Note: When replacing line 17 in CameraControl script with these lines:
Cursor.lockState = CursorLockMode.Confined;
Cursor.visible = false;
The problem seems to disappear.
Project is attached to this letter.
Reproduces with: 5.5.0f3; 5.6.0a6
Doesn't reproduce with: 5.4.3f1; 5.4.2f2; 5.4.1f1; 5.4.0f3; 5.3.0f4;
Comments (2)
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
- Texture Map Viewer shows "Loading..." text instead of indicating users that Baked Texture Maps are missing
- "Analyze Import Process" button misaligned in Import Activity window
- Text in “Baked Shadowmask” mode is difficult to read in Baked Lightmap Viewer when Editor theme is set to Light
- Mesh wireframe is difficult to see in Baked Lightmap Viewer window when texture opacity is maximized
- Informational text does not wrap and does not fit when the Viewer Window is opened by default
onurozcan
Jul 18, 2017 17:57
Does happen in 5.6.1f1 too. Cursor is always locked at lower left, and fires on mouse click using that.
Strayer
Mar 14, 2017 22:52
This appears to still be happening in Unity 5.5.1f1 on a Window 10 machine. We have discovered that click events and such are still firing for the locked and hidden cursor, but the cursor is locked to the lower left of the game window.