Search Issue Tracker
Won't Fix
Won't Fix in 6000.2.X
Votes
0
Found in
6000.0.22f1
6000.1.0a7
6000.2.0a1
Issue ID
UUM-83520
Regression
No
"Input.GetKey", "Input.GetKeyDown", and "Input.GetKeyUp" functions do not detect input when passing "WheelUp" or "WheelDown" KeyCodes
Reproduction steps:
1. Open the attached “BugRepro” project
2. Enter the Play Mode
3. Scroll the mouse wheel up or down
4. Observe the Console
Expected result: The script prints out true whenever the mouse wheel is scrolled
Actual result: The script always prints out that the mouse wheel was not scrolled
Reproducible with: 6000.0.21f1
Couldn’t test with: 2021.3.44f1, 2022.3.49f1 - “WheelUp” and “WheelDown” KeyCodes are not supported
Reproducible on: Windows 10
Not reproducible on: No other environment tested
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:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
We would suggest migrating from the Input Manager to the newer Input System.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
Resolution Note (6000.2.X):
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
We would suggest migrating from the Input Manager to the newer Input System.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.