Search Issue Tracker
Fixed
Fixed in 1.9.0
Votes
0
Found in [Package]
1.9.0
Issue ID
ISXB-704
Regression
Yes
"GetDevice<Mouse>().scroll.ReadValue()" method returns a 1-digit value when using the mouse's scroll value
How to reproduce:
1. Open the “MouseScrollReadValueIssue“ project
2. Open the “SampleScene“
3. Enter Play Mode
4. Use the mouse’s scroll wheel
5. Observe the Console
Expected result: A 3-digit number is printed in the second element, e.g. “(0.00, 120.00)”
Actual result: A 1-digit number is printed in the second element, e.g. “(0.00, 8.00)”
Reproduced with: 1.4.4 (2023.2.0a22), 1.8.0-pre.2 (2023.2.0a22, 2023.2.3f1, 2023.3.0a17)
Not reproduced with: 1.4.4 (2023.2.0a21), 1.8.0-pre.2 (2023.2.0a21, 2022.3.15f1, 2023.1.20f1)
Reproduced on: Windows 11
Not reproduced on: No other environment tested
Note: The regressed version is not in the package version, but the Editor version → The FAV is 2023.2.0a22
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
Add comment