Search Issue Tracker
Fixed in 2022.1.X
Fixed in 2020.3.X, 2021.3.X
Votes
0
Found in
2019.4
2020.3
2021.1
2021.1.15f1
2021.2
2022.1
Issue ID
1354498
Regression
No
Linux Editor ignores mouse scroll wheel input when the cursor is locked on the new Input System
How to reproduce:
1. Open the attached project (1354498.zip) and make sure the SampleScene is open
2. Enter Playmode
3. Press on the Game view to make sure the cursor is locked
4. Try to scroll using the mouse wheel
5. Observe the console output
Expected result: The Console outputs "Scrolling +/-" messages
Actual result: The Console doesn't print any new messages
Reproducible with: 2019.4.29f1, 2020.3.15f2, 2021.1.16f1, 2021.2.0b6, 2022.1.0a3
Notes:
1. Reproducible on Ubuntu 18.04
2. Not reproducible on Windows 10
3. Only reproducible using the new Input System (Tested on package versions 1.0.0, 1.0.1 and 1.0.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
- NullReferenceExceptions are being thrown when saving a ScriptableObject with an array of a type with a CustomPropertyDrawer that uses TrackPropertyValue
- Applied velocity is inconsistent when using Rigidbody AddForce() with ForceMode.VelocityChange
- Crash on AudioUtil_CUSTOM_HasAudioCallback when exiting Play Mode while the Inspector is displaying a GameObject with an empty script attached
- Scroll offset is framerate-dependent when scrolling with velocity in the Device Simulator
- "Object.FindObjectsOfType<T>() is obsolete" warning is thrown when using "Transitions Plus" asset
Resolution Note (fix version 2022.1):
Fix Linux Editor not reporting scroll values with new input system.
Fixed in 2022.1.0a11
Resolution Note (fix version 2021.3):
Fixed in 2021.3.5f1
Resolution Note (fix version 2020.3):
Fixed in 2020.3.41f1