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
- Build and Run button greyed out for locally invalid architecture, despite remote build is specified
- Graphics Settings: “Use Defaults” checkboxes misaligned in Tier Settings section
- VFX Graph particles are not culled when using URP and Frustum Culling is enabled on VFX Mesh Output
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
Resolution Note (fix version 1.1):
Fixed by https://github.com/Unity-Technologies/InputSystem/pull/1150