Search Issue Tracker
Fixed
Fixed in 1.8.0
Votes
0
Found in [Package]
1.4.4
Issue ID
ISXB-371
Regression
No
Input System Action execution order is determined by the order of Bindings in the input.asset file instead of Actions
How to reproduce:
# Open the attached project “IN-23357.zip“
# Open the “SampleScene” Scene
# Enter the Play mode
# Press the “Spacebar“ key
Expected result: Input Action 2 is fired first and the Input Action 1 is fired second
Actual result: Input Action 1 is fired first and the Input Action 2 is fired second
Reproducible with: 0.2.10-preview, 1.4.4 (2020.3.43f1), 1.4.4 (2021.3.16f1, 2022.2.2f1, 2023.1.0a23)
Couldn’t test with: 0.2.8-preview and lower - due to errors in the Console window
Reproduced on: Windows 10 Enterprise
Note: The Input2 Input Actions Asset holds the actions in this order - Action 2, Action 1. Both have the “Spacebar“ key as their binding
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
- [UI Builder] Viewport's gizmos for Margin and Padding disappear when dragging to modify the value and the cursor leaves the Spacing section
- "Multiplayer Center" window does not reflect changes made in "Other Packages" section
- Crash on D3DKMTOpenResource when capturing with RenderDoc while GPU Skinning is set to GPU(Batched)
- Editing and saving Curve changes in UI Builder window throws multiple errors in the Console
- [UI Builder] Value is not selected when left clicking on Spacing/Border Widget values
Resolution Note (fix version 1.8.0):
This have been resolved by providing clarifying information regarding action execution order in the manual.