Search Issue Tracker
Fixed
Fixed in 1.9.0
Votes
0
Found in [Package]
1.8.0
1.9.0
Issue ID
ISXB-804
Regression
Yes
trying to delete the last composite of a composite binding throws exceptions
Steps to reproduce:
1. create new action map
2. add new action
3. add a composite binding to the action
4. expand the composite binding
5. start deleting the composite parts of the bindings
Actual results: Notice an exceptions is being thrown when trying to delete the last compisite. Subsequent exceptions are thrown when selecting the binding again.
??ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection.??
??Parameter name: index??
??type is not a supported string value??
??UnityEngine.GUIUtility:ProcessEvent (int,intptr,bool&)??
Expected results: No exceptions are thrown and I can delete all parts of the binding
Reproducible with versions: 1.8.0-pre.3
Not reproducible with versions: 1.7.0
Tested on (OS): Win11
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.9.0):
Fixed in upcoming Input System version 1.9.0