Search Issue Tracker
Won't Fix
Votes
0
Found in
2019.4
2020.3
2020.3.10f1
2021.1
2021.2
2022.1
Issue ID
1339271
Regression
No
Editor shortcuts and Scene navigation behaves incorrectly when using the DVORAK keyboard layout
Reproduction steps:
1. Change the keyboard layout to DVORAK through system settings
2. Open a new or an existing project
3. In the Scene view, hold the right mouse button and try navigating with WASD (,AOE when using DVORAK)
Expected result: You are able to navigate the Scene as usual
Actual result: The navigation doesn't work that way since the Editor requires actual WASD buttons to be pressed (e.g. when in DVORAK layout, you have to press "," to move forward since "," is replaced by W)
Reproducible with: 2019.4.29f1, 2020.3.16f1, 2021.1.17f1, 2021.2.0b7, 2022.1.0a5
Notes:
- Not reproducible on Windows
- Reproducible on Linux and macOS
- Shortcuts also do not work in the same manner (e.g. CTRL+C, CTRL+V, etc)
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note:
There is no plan to support DVORAK keyboard layout short or mid term.