Search Issue Tracker
Fixed in 2021.3.16f1
Fixed in 2021.3.X, 2022.2.X, 2023.1.X, 2023.1.0a26
Votes
0
Found in
2021.3.13f1
2022.1.22f1
2022.2.0b15
2023.1.0a18
Issue ID
UUM-19010
Regression
No
Input.GetKey doesn’t read all Shift + Alpha keys non-US keyboard layouts
Reproduction steps:
1. Open the user’s attached project
2. Open the “Assets/Scenes/SampleScene.unity” scene
3. Enter the Play Mode
4. Set Keyboard Layout to English (US)
5. In Game View, Click Shift + 3
6. Observe the Console window
7. In Game View, Click Shift + 4
8. Observe the Console Window
9. Set Keyboard Layout to Swedish
10. Repeat steps 5-8
11. Set Keyboard Layout to English (UK)
12. Repeat steps 5-8
Expected result: Input.GetKey reads Shift + Alpha keys on non-US keyboard layouts
Actual result: Input.GetKey doesn’t read all Shift + Alpha keys non-US keyboard layouts
Reproducible with: 2021.2.0a12, 2021.2.19f1, 2021.3.13f1, 2022.1.22f1, 2022.2.0b15, 2023.1.0a18
Couldn’t test with: 2020.3.41f1, 2021.2.0a11 (Shift + 3 or Shift + 4 is not supported)
Reproducible on: Ubuntu 20.04.5
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- "Unable to find style 'VideoClipImporterLabel' in skin 'GameSkin' " warning thrown when converting the Video Clip Inspector to a floating window in Play mode
- Unclear "Failed to start primary listening socket" error when launching the Multiplayer Play Mode second player and many Unity instances are running
- The cogwheel button in the Build History window gets distorted when the Build History window is resized or options are ticked in the toolbar
- Unity Hub (Arm64) fails to start when installed on Windows 11 (Arm64)
- “This version of Unity is not currently available for use with Build Automation” warning is shown only after setting up Cloud and Version Control warnings when adding Build Automation to a Build Profile
Add comment