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
- Non-multisampled texture binding errors are logged when running the DepthBlit URP scene with MSAA enabled on Vulkan
- The Editor does not recognize code errors in generic classes when using C# Source Generator to generate serialization code
- Long Sprite names are not truncated in the Inspector window name label and the preview labels when a Sprite with a long name is selected
- NullReferenceException is logged when undoing Deletion of a Visual Query Block of a Search Expression
- “Unsupported type MinMaxCurve” error and “Could not register property modification for animation binding…” warnings are thrown after moving playhead when Particle System Property is added to Animation window
Resolution Note (fix version 1.9.0):
Fixed in upcoming Input System version 1.9.0