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
- 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
This is a duplicate of issue #1187377