Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2019.4.X
Votes
4
Found in
2018.2.0b4
2018.4
2019.3
2019.3.0f6
2020.1
Issue ID
1219781
Regression
Yes
[Linux] [Editor] Input.GetAxis("Mouse ScrollWheel") always returns 0 when Cursor.lockState is set to CursorLockMode.Locked
How to reproduce:
1. Open user's attached project (EditorScollWheelBugDemo.zip)
2. Open SampleScene and enter Play mode
3. While Play mode is focused, scroll the mouse wheel forward and back, observe that Input.GetAxis("Mouse ScrollWheel") does not always return 0
4. Press 1 to lock cursor
5. Repeat step 3
Expected result: Input.GetAxis("Mouse ScrollWheel") returns values regardless of what state the cursor is in
Actual result: Input.GetAxis("Mouse ScrollWheel") always returns 0 when cursor is locked
Reproducible with: 2018.2.0b4, 2018.4.17f1, 2019.3.2f1, 2020.1.0a23
Not reproducible with: 2017.4.36f1, 2018.2.0b4
Regression from 2018.2.0b3 to 2018.2.0b4
Note: Not reproducible in Player.
Comments (1)
-
oobartez
Apr 30, 2020 15:58
The same problem appears on macOS with Unity 2019.3.10 in full-screen standalone builds, works fine in windowed mode and in editor.
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
- UnityYamlMerge.exe doesn't correctly handle merge conflicts in modified properties on a prefab variant
- Inconsistent color scheme in "Details" section of "Select Presets" inspector window
- Crash on __pthread_kill when launching Editor via command-line with "-disableManagedDebugger" argument
- [VFX] Deleting “New Group Node” name doesn’t allow to type or add new name
- [VFX] Creating a long Group Node name breaks nodes boarders
Resolution Note (fix version 2020.1):
Fixed scroll events not being passed to the Linux editor when cursor was set to CursorMode.Locked.
Resolution Note (fix version 2020.1):
Fixed in version 2020.1.0b10
Resolution Note (fix version 2019.4):
Fixed in version 2019.4.0f1