Search Issue Tracker
Fixed in 1.0.0-preview.1
Votes
0
Found in [Package]
preview - 1.0.0
Issue ID
1190096
Regression
No
"IndexOutOfRangeException" is thrown when pressing both controls which are binded to the same action in the new Input System
How to reproduce:
1. Open the attached project ("case_1190096-Project.zip")
2. Open the SampleScene in the Scenes folder
3. Enter the Play Mode
4. Press the controller's "Left Stick" and the keyboard's "A" Key at the same time
Expected result: There are no errors thrown
Actual result: Errors are thrown
Reproduced in Unity versions: 2019.2.9f1, 2019.3.0b6, 2020.1.0a8
Reproduced in Package version "preview - 1.0.0"
Couldn't test with Unity versions: 2017.4, 2018.4 (Problems with the Package Manager)
Couldn't test with Package versions lower than "preview - 1.0.0" (There's no InputActionMap.FindAction function)
Note: Exception "Should not get here" is thrown on any input from the controllers after the "IndexOutOfRangeException".
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Redoing creation of Sub Scenes and Cube GameObjects in Hierarchy throws “Assertion failed on expression: 'targetScene != nullptr’” error in Console window
- Selecting “New Sub Scene” after assigning “New Scene” in Sub Scene Script Component throws “Destroying GameObjects immediately is not permitted” in the Console window
- Shader Graph "Zoom Step Size" can be set to 0 even though the zoom still works
- Enabling/Disabling the Deprecated Nodes doesn't apply to the opened Shader Graph unless any Variable is added to the Blackboard
- Group Selection title text size is smaller in renaming than the actual font size
Add comment