Search Issue Tracker
Fixed
Fixed in 1.4.4
Votes
0
Found in [Package]
1.4.3
Issue ID
ISXB-309
Regression
Yes
Inputs are not registered on one Map when two Action Maps have the same bindings
Steps to reproduce:
1. Open the user’s project
2. Enter Play mode
3. Press any key of WASD
Expected result: Both maps coordinate changes and Map1 is equal to Map2
Actual result: Only Map1 coordinate changes
Reproducible with: 1.4.3 (2020.3.40f1, 2021.3.11f1, 2022.1.18f1, 2022.2.0b10, 2023.1.0a13)
Works with: 1.3.0
Reproduced on: macOS Monterey 12.5.1 (Intel) & Win11
Notes:
- There are two Action maps with a Movement Action. The first one has WASD bindings. The second one has WASD and arrow key bindings. WASD keys are only triggering on the last Action Map to be enabled. So using the WASD keys will only result in inputs being received to Map1
- Input Actions file is in the Assets folder (InputTest.inputactions)
- Also reproducible in the Player
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
Resolution Note:
Fixed by https://issuetracker.unity3d.com/product/unity/issues/guid/ISXB-254
Resolution Note (fix version 1.4.4):
Fixed by https://issuetracker.unity3d.com/product/unity/issues/guid/ISXB-254