Search Issue Tracker
Won't Fix
Votes
0
Found in
2020.3.39f1
2021.3.10f1
2022.1.17f1
2022.2.0b8
2023.1.0a10
2023.2.0a1
Issue ID
UUM-15720
Regression
No
Right Alt is registered as Left Ctrl when the keyboard layout is not English US
How to reproduce:
1. Open the user-attached project “KeyboardInputTest”
2. Open the “Start” scene
3. Enter the Play Mode
4. Press the L key to register Input via Legacy Input System
5. Set the keyboard layout to English UK and press Right Alt
Expected result: The prompt in the Game Mode says “Right Alt”
Actual result: The prompt in the Game Mode says “Left Ctrl”
Reproducible with: 2020.3.39f1, 2021.3.10f1, 2022.1.17f1, 2022.2.0b8, 2023.1.0a10
Reproducible on: Windows 11 Pro
Note:
-The following issue was tested and reproduced with the following keyboard layouts: English UK, English International, Lithuanian and Russian.
-The issue is not reproduced with the New Input System
-Also reproduced 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
- TextShadow properties are not applied when displayed in a custom MenuItem Window
- Memory leak occurs when focused on Player while using Direct3D12
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
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 "Won't Fix".This does not mean that the issue isn’t a legitimate bug, but instead that we are not able to prioritize the fix, at this time.
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.
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 "Won't Fix".This does not mean that the issue isn’t a legitimate bug, but instead that we are not able to prioritize the fix, at this time.
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.