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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment