Search Issue Tracker
By Design
By Design in 1.1.X
Votes
1
Found in [Package]
1.1.0-pre.6
Issue ID
ISXB-31
Regression
Yes
[Input System] CompositeBinding doesn't work with Mouse Scroll Wheel
How to reproduce:
1. Open user-submitted project
2. Press Play
3. Scroll Mouse Wheel Down
Expected result: Text changes from 1 to 2
Actual result: Text remains at 1
Reproducible with: 1.1.0-pre.6, 1.1.1 (2021.2.0b16, 2022.1.0a12)
Not reproducible with: 1.1.0-pre.5 (2021.2.0b16, 2022.1.0a12)
Could not test with: 1.1.0-preview.3 (error CS1061: 'InputSystemUIInputModule' does not contain a definition for 'AssignDefaultActions'), 2019.4.31f1 (SerializationException: Unable to find assembly 'UnityEditor.CoreModule), 2020.3.20f1, 2021.1.25f1 (The list of \[SerializeReference] objects being deserialized is from a more recent version of Unity. This is not supported and objects will be skipped.)
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
- Shader warning in 'Hidden/Core/DebugOccluder' thrown after building High Definition 3D Sample Template
- Audio Mixer “+” buttons overlap with UI when the Audio Mixer window layout is set to Horizontal
- "Clear" button in the "Set project display name" closes all the pop-up instead of clearing just a name from the field
- Video Player renders no video on specific devices when using Vulkan
- The Editor slows itself down by showing tons of warnings when the majority of TransformAccessArrays content are NullRefs
Resolution Note:
Project binds to an inverted scroll/y axis and then uses WasPressedThisFrame()/WasReleasedThisFrame() on the value. The axis will go [-1..1] and thus, given that "pressed" is evaluated by magnitude, will trigger both on scrolling up and down. Adding a clamp with [0..1] fixes that and press detection works as expected. In 1.4, we have added up/down/left/right controls to bind to scroll directions easily without having to apply processors.
The behaviour change between 1.1.0-pre5 and 1.1.0.-pre6 is is a result of fixing behaviour where minimum and maximum values were not respected in Axis Composite Bindings https://issuetracker.unity3d.com/issues/inputsystem-1d-axis-composite-binding-will-return-a-incorrect-value-if-minvalue-and-maxvalue-is-not-1-and-1
Resolution Note (1.1.X):
Project binds to an inverted scroll/y axis and then uses WasPressedThisFrame()/WasReleasedThisFrame() on the value. The axis will go [-1..1] and thus, given that "pressed" is evaluated by magnitude, will trigger both on scrolling up and down. Adding a clamp with [0..1] fixes that and press detection works as expected. In 1.4, we have added up/down/left/right controls to bind to scroll directions easily without having to apply processors.
The behaviour change between 1.1.0-pre5 and 1.1.0.-pre6 is is a result of fixing behaviour where minimum and maximum values were not respected in Axis Composite Bindings https://issuetracker.unity3d.com/issues/inputsystem-1d-axis-composite-binding-will-return-a-incorrect-value-if-minvalue-and-maxvalue-is-not-1-and-1