Search Issue Tracker
Fixed in 1.1.0-preview.2
Votes
2
Found in [Package]
1.0.0-preview.5
Issue ID
1253034
Regression
Yes
"Map index on trigger" and IndexOutOfRangeException errors when using multiple Interactions on the same Action
How to reproduce:
1. Open attached project "Input_Bug_Stripped.zip" and scene "SampleScene"
2. Enter Play mode
3. Click and release once and fast
4. Observe Console window
Expected result: no errors are thrown
Actual result: 3 errors are thrown
Reproducible with: 2019.4.0f1, 2020.1.0b12, 2020.2.0a14 (1.0.0-prev.5, 1.0.0)
Not reproducible with: 2019.4.0f1, 2020.1.0b12, 2020.2.0a14 (1.0.0-prev.3, 1.0.0-prev.4)
Could not test with: 2018.4 (package was not yet released)
Thrown errors:
Map index on trigger does not correspond to map index of trigger state
Exception 'IndexOutOfRangeException' thrown from state change monitor 'InputActionState' on 'Button:/Mouse/leftButton'
IndexOutOfRangeException: Index was outside the bounds of the array.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- 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
- GUI Skin Asset dropdowns show expanded arrow icon but do not display content when opened with arrow keys
- Seams are visible in reflective surfaces when using box projection in Android Build Profile
- Bloom post-processing effect in URP is missing in a Build when Dirt Texture is enabled in the Bloom override of a Global Volume
Add comment