Search Issue Tracker
Fixed
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note:
Fixed by https://issuetracker.unity3d.com/product/unity/issues/guid/ISXB-254