Search Issue Tracker
Fixed
Fixed in 1.6.3
Votes
17
Found in [Package]
1.4.3
1.4.4
1.6.1
Issue ID
ISXB-361
Regression
No
[Windows] InputValue of the scroll wheel changes with the step of ±120 when scrolling using Input System
Reproduction steps:
- Open the attached “InputSystem” project
- Open the “InputManager” scene
- Enter the Play Mode
- Scroll the mouse wheel and observe the Game view
Expected result: The scroll wheel value changes with step of ±1
Actual result: The scroll wheel value changes with step of ±120
Reproducible with: 1.4.3, 1.4.4 (2020.3.42f1, 2021.3.15f1, 2022.1.24f1, 2022.2.1f1, 2023.1.0a22)
Reproduced on: Windows 10
Note: The issue is only reproducible on Windows. This is the result of how Microsoft implemented scroll wheel handling in their OS. More here: https://learn.microsoft.com/en-us/windows/win32/inputdev/wm-mousewheel
Comments (1)
-
Tymianek
May 29, 2024 11:51
I can't find a WebGL issue for this.
This issue is also reproducible while playing WebGL builds using a Windows machine.
I'm using Unity 6000.0.1f1 and input system 1.8.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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
fixed in 2023.2.0a22