Search Issue Tracker
Fixed in 2022.1.X
Fixed in 2019.4.X, 2020.3.X, 2021.1.X, 2021.2.X
Votes
7
Found in
2018.4
2019.4.11f1
2021.1
Issue ID
1283506
Regression
No
[Mac] Cursor.lockState registers input movement to center when mouse is moved
How to reproduce:
1. Open the attached "case_1283506-MouseHideIssues.zip" project
2. Open SampleScene
3. Press play or build a standalone player
4. Hold mouse 1 and move the mouse from the center of the screen
5. Now click and move from the side of the game view JUST A BIT. Like, a few pixels.
Expected result: Mouse movement is registered identically
Actual result: On Mac, the rotation jumps. And it jumps the amount it would rotate as if the user dragged to the center. On Windows, the rotation is smooth, just like we want.
Reproducible with: 2018.4.28f1, 2019.4.13f1, 2020.1.11f1, 2020.2.0b9, 2021.1.0a2
Comments (1)
-
itsPeetah
May 25, 2021 08:19
Not happy but alleviated that someone else is experiencing this issue. Thank you for reporting. I hope it gets fixed soon.
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
- Desktop Linux runtime does not respect -popupwindow command line argument
- Shader Graph more options dropdown button does not open the dropdown when clicked all the way to the right of the button
- “Attempting to draw with missing bindings“ warning lacks root cause indication and is thrown each frame when StructuredBuffer is accessed on DirectX12
- Shader Graph Import Settings documentation leads to "Sorry... that page seems to be missing!" page when opened through the documentation button in the Inspector window
- Unexpected Material change/transparency when switching between ShaderGraph and material at runtime in HDRP
Resolution Note (fix version 2022.1):
Fixed in 2022.1.0a1
Resolution Note (fix version 2021.2):
Fixed in 2021.2.0b13
Resolution Note (fix version 2021.1):
Fixed in 2021.1.23f1
Resolution Note (fix version 2020.3):
Fixed in 2020.3.20f1
Resolution Note (fix version 2019.4):
Fixed in: 2019.4.32f1