Search Issue Tracker
Fixed in 1.0.0-preview.6
Votes
1
Found in [Package]
preview - 1.0.0, preview.4 - 1.0.0
Issue ID
1213085
Regression
No
[Input System] Input Actions cause exceptions and 'Should not get here' errors to appear after deleting an Action Map
How to reproduce:
1. Open user-submitted project (Pokemon Clone.zip)
2. Enter Play Mode
3. Use the WASD keys to move the player around
4. Check the Console window
Expected result: no errors are thrown
Actual result: multiple exceptions are thrown
Reproducible with: 2019.2.20f1, 2019.3.0f6, 2020.1.0a21
Could not test with: 2017.4.36f1, 2018.4.16f1(project incompatible)
Reproducible with package versions: preview - 1.0.0, preview.4 - 1.0.0
Could not test with package versions: preview - 0.9.6(project incompatible)
Notes:
Opening Assets/ControllerInput/InputActions.inputactions, creating a new Action Map, copying the Actions from 'UI' and then deleting the 'UI' Action Map prevents these errors from being thrown
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
- 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
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version 1.0.0-preview.6):
Fixed by https://github.com/Unity-Technologies/InputSystem/pull/1063