Search Issue Tracker
Duplicate
Votes
1
Found in [Package]
2019.4
2019.4.2f1
2020.2
Issue ID
1262799
Regression
No
Mouse position is not updated when locking the cursor and it causes the mouse to snap unpredictably when entering the Play Mode
How to reproduce:
1. Open the attached project's Scene labeled "SampleScene"
2. Enter the Play Mode (don't move the mouse after clicking the Play button)
3. Observe the Game View
4. Move the mouse a little
Expected result: Mouse position is updated when locking the cursor and doesn't cause the mouse to snap unpredictably when entering the Play Mode
Actual result: Mouse position is not updated when locking the cursor and it causes the mouse to snap unpredictably when entering the Play Mode
Reproducible with: 2018.4.26f1, 2019.4.4f1, 2020.1.0b16, 2020.2.0a18
Note: Mouse position is updated for a brief moment and then reset to zero (0, 0)
-
Resolution Note:
This is a duplicate of another issue we're looking at. Similar behavior exists when using a standalone build and locking the cursor on first mouse down.
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
This is a duplicate of issue #1283506