Search Issue Tracker
Fixed in 1.0.0-preview.7
Votes
0
Found in [Package]
preview.4 - 1.0.0
Issue ID
1215784
Regression
Yes
Unnecessary/unwanted binding candidates are found when detecting and changing an input value of an input device
How to reproduce:
1. Open the attached 'RebindCandidates.zip' project
2. Enter Play mode
3. In the Drop-down menu select 'Mouse' and then 'Keyboard'
4. Hold any key (let's say 'v') and select 'Detect'
5. Press any other key (let's say '2') while still holding the previous key
Expected result: only 'Num 2' is added to the list
Actual result: 'Num 2', 'V' and 'Any Key' are added to the list
Reproducible with: 2019.2.20f1, 2019.3.0f6, 2020.1.0a22 (preview.4 - 1.0.0)
Not reproducible with: 2019.2.20f1, 2019.3.0f6, 2020.1.0a22 (preview - 1.0.0, preview.3 - 1.0.0)
Could not test with: 2017.4.36f1 (Input System not available), 2018.4.17f1 (Package incompatibility errors in the project)
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
- Silent crash when clicking in Scene View in a specific project
- The Player renders black on a Quest headset when MSAA, Post Processing, and Spacewarm depth submission are enabled
- Graphics Compositor breaks Unity rendering when the "Output Camera" is changed to a scene Camera and one Camera SubLayer is active
- The Editor freezes on RenderGraphViewer.Repaint when entering too many characters in search fields without character limits
- Adding a new SubLayer in Graphics Compositor renders BaseLayer darker and makes it flicker
Resolution Note (fix version 1.0.0-preview.7):
Fixed by https://github.com/Unity-Technologies/InputSystem/pull/1105
Fixed in preview.7 - 1.0.0 'Input System' package version