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
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
- 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
Resolution Note (fix version 1.8.0):
This have been resolved by providing clarifying information regarding action execution order in the manual.