Search Issue Tracker
Feature Request
Votes
0
Found in [Package]
1.5.1
Issue ID
ISXB-482
Regression
No
InputAction.GetBindingDisplayString always returns WASD when the controller is used
Reproduction steps:
1. Open the attached “Test Project” project
2. Open the “Samples/Input System/1.5.1/Rebinding UI/RebindingUISampleScene” Scene
3. Switch the Windows keyboard to AZERTY layout (French language)
4. Entert the Play Mode
5. Press any button on the keyboard
6. Press any button on the gamepad (used Xbox360 controller)
7. 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, 1.5.1 (2020.3.48f1, 2021.3.25f1, 2022.2.18f1, 2023.1.0b16, 2023.2.0a14)
Reproducible on: Windows 10
Notes:
- The issue is also reproducible with the Russian keyboard layout, but instead of “Z/Q/S/D” it will display “Ц/Ф/Ы/В”
- Related issue ISXB-265.
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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Resolution Note:
Thank you for your bug report.
After reviewing the issue and the impact it has on our users our team has decided that this case will be resolved as "Feature Request" and added into our feature backlog for future consideration.
The case will now be closed, and will not be reopened unless new information arises that would change the issue’s impact. Please let us know if you have additional information relating to the severity of this bug.