Search Issue Tracker
Won't Fix
Won't Fix in 1.4.X
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
- [Tile Palette] Sprites not rendering when brush tool "Paint a filled box with active brush" is used for the first time
- Adding available Nodes with longer names in Fragment Context window overflow Fragment Context window in Shader Graph
- "Layer Palette Profile" Asset is automatically applied to the second Terrain but doesn't load any layers
- "Terrain Tools" shortcut conflicts with the Overlays shortcut by default
- Longer Shader Graph Property Reference names breaks VFX Graph Output Particle Node
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).
Resolution Note (1.4.X):
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).