Search Issue Tracker
Duplicate
Votes
0
Found in [Package]
1.0-preview
Issue ID
1189909
Regression
No
[Input System] Empty part binding on composite causes subsequent parts to no longer work
Repro:
1. Create an input action with a Vector2 composite.
2. Bind "Up" to "W", "Left" to "A", and "Right" to "D".
3. Do NOT bind "Down" to anything.
4. Add a PlayerInput to the scene and link it to the actions.
5. Set it's behavior to "Invoke Unity Events" and hook up the action from above to PlayerInput.DebugLogAction.
6. Go into play mode.
7. Hit "W" and observe that a message is logged to the console.
8. Hit "A" and "D" and observe that in both cases no message is logged, i.e. the inputs aren't functional.
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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
This is a duplicate of issue #1187377