Search Issue Tracker
Feature Request
Feature Request in 1.5.X
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
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
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.
Resolution Note (1.5.X):
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.