Search Issue Tracker
Fixed in 1.1.X
Votes
0
Found in [Package]
0.2.6
Issue ID
1228000
Regression
Yes
[Input System] Bindings get cleared for other Control Scheme Actions when reordering an Action in a specific Control Scheme
How to reproduce:
1. Open tester-attached project (ActionOrder.zip)
2. Open Controls.inputactions
3. Note that All Control Schemes contains bindings 'A' and 'B' for New Action
4. Select Control Scheme 'A'
5. Drag the New Action to the middle/bottom of the list
6. Select All Control Schemes again
Expected result: New Action contains bindings 'A' and 'B' after reordering
Actual result: New Action only contains binding 'A' after reordering
Reproducible with: 2019.3.9f1, 2020.1.0b5, 2020.2.0a7
Could not test with: 2017.4.39f1(package unavailable), 2018.4.20f1(regressed package version unavailable)
Reproducible with package versions: preview - 0.2.6, preview.6 - 1.0.0
Not reproducible with: preview - 0.2.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
- 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
Resolution Note (fix version 1.1):
Fixed by https://github.com/Unity-Technologies/InputSystem/pull/1150