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
- [AI Assistant] UI Overlap: Permission dropdown menu persists and obstructs "Allow" / "Deny" buttons in AI Assistant window
- Dragging an object under another to set it as the child will rename the parent object if we trigger a rename and start dragging immediately
- UITK WorldSpace ScrollView behaviour on Mobile
- [VisionPro] WebCamTexture fails to capture Persona stream frames
- Some shader variants are not collected when tracing with GraphicsStateCollection
This is a duplicate of issue #1187377