Search Issue Tracker
Fixed in 0.3.10
Votes
4
Found in [Package]
0.1.2-preview
Issue ID
1136357
Regression
No
[UI] When using detect input to bind an Action, the mouse scroll is picked up automatically
From GitHub: https://github.com/Unity-Technologies/InputSystem/issues/383
Note: this happens when the Input Action's Type is set to "Any", "Axis" or "Vector2", a.k.a the ones that can take mouse scroll input as Binding path. It does NOT happen to the other Types.
Repro:
1. Download package and project at: https://github.com/Unity-Technologies/InputSystem
2. Open SimpleControls Input Action at: Assets -> Demo -> SimpleDemo
3. In the middle section, create a new Input Action and select it
4. In the right section, set the Type to Any, Axis or Vector2
5. In the middle section, select the Empty Binding under the new action
6. In the right section, click the "O" button next to the drop down menu for Path
7. Observe the Binding change
8. If nothing happens, cancel the binding. Scroll the mouse a little, then repeat step 6.
Actual: As soon as the user clicks the "O" button, the Binding is set to mouse scroll.
Comments (1)
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
- Some UXML Template Asset foldouts appear enabled when all fields inside are disabled
- URP Terrain Demo crash on burst_signal_handler after Generating lighting
- Project window button icons are poorly visible and their shades differ in Light theme
- GC.Alloc called by HDRenderPipeline.LensFlareMergeOcclusionDataDrivenPass() when playing the default HDRP Sample Template project
- Automatic LOD fails and SRP Batcher incompatibility occurs when using spline-based quad-topology meshes
Wokarol
Apr 10, 2019 09:22
Scroll setted as binding reacts to any mouse movent, not only scrolling.