Search Issue Tracker
Fixed in 1.1.0-pre.5
Votes
1
Found in [Package]
2020.2.0b8
Issue ID
1288335
Regression
Yes
[Input System] Assertation error appears when adding Action to the disabled Action map at runtime
How to reproduce:
1. Open attached "Input.zip" project and SampleScene scene
2. Enter the Play mode
3. Observe the error in the Console window
Expected result: No errors appear
Actual result: Error appears in the Console window
Reproducible with: 1.0.0-preview.7 - 1.1.0-preview.2(2019.4.14f1, 2020.1.13f1, 2020.2.0b11, 2021.1.0a5)
Not reproducible with: 1.0.0-preview - 1.0.0-preview.6(2019.4.14f1, 2020.1.13f1, 2020.2.0b11, 2021.1.0a5)
Could not test with: 2018.4.29f1(errors when downgrading)
Note:
1. Workaround: disable controls instead of Action map
2. The error that appears in the Console window:
"Action count in old and new state must be the same"
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
- Changing Signing organization on a Template still shows the same organization in the Hub
- [Android] Navigation bar does not go away when tapping on the screen to close the keyboard
- "InvalidOperationException" is thrown when clicking "Ctrl+Z" after opening Gradient Editor
- Breadcrumbs don't change names when graphs are renamed
- Adaptive Probe Volumes require a second bake for correct probe lighting data when Min Probe Spacing is changed in URP
Resolution Note (fix version 1.1.0-pre.5):
The fix for this case is that we show an error with a better explanation