Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
1.3.0
1.4.1
Issue ID
ISXB-265
Regression
No
InputAction.GetBindingDisplayString returns WASD when the controller is used even if the current keyboard is not WASD layout
Reproduction steps:
# Open the user attached project
# Open the “RebindingUISampleScene” scene
# Connect a gamepad
# Switch the keyboard to AZERTY layout (French language)
# Press the Play button
# Press any button on the keyboard
# Observe that in the Game view in section “Keyboard & Mouse” field “Move” is set to “Z/Q/S/D”
# Press any button on the gamepad
# Observe the Game view, section “Keyboard & Mouse”, field “Move”
Expected result: Field “Move” is set to “Z/Q/S/D”
Actual result: Field “Move” is set to “W/A/S/D”
Reproducible with: 1.3.0, 1.4.1 (2020.3.37f1, 2021.3.8f1, 2022.1.12f1, 2022.2.0b4, 2023.1.0a4)
Reproduced on: Windows 10
Note: the issue is also reproducible with the Russian keyboard layout, but instead of Z/Q/S/D in step 7 it will display Ц/Ф/Ы/В
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
- “ValidateSchema Error2” error is thrown in the Player when using IL2CPP Scripting Backend
- Symbolic links disappear when a .xcframework file is added through the Unity Editor
- Errors regarding importing occur upon opening a project when the "Library" folder is deleted
- MeshRenderer.sortingLayerID cannot be changed when change is being done in a built Player
- Warnings related to App Icon are being thrown when building project to VisionOS Platform
Resolution Note:
I tested the same sample from v1.4.2 of the Input System package and was unable to reproduce the issue there anymore. (However I could see the issue was present in the v1.3.0 sample provided).