Search Issue Tracker
Fixed in 2020.3.47f1
Fixed in 2020.3.X, 2021.3.X, 2022.2.X, 2023.1.X, 2023.2.X, 2023.2.0a1
Votes
0
Found in
2020.3.41f1
2021.3.10f1
2022.2.0b8
2023.1.0a9
2023.2.0a1
Issue ID
UUM-22694
Regression
Yes
[Input] Arrow keys are displayed as "Num" when using "ArrowKey.displayNames"
Steps to reproduce:
1. Open the “My project” project
2. Open “Sample Scene” scene
3. Enter Play Mode
4. Observe the Console window
Expected result: Logged arrow display names are correct (e.g. “Up”)
Actual result: Logged arrow display names are incorrect (e.g. “Num 8”)
Reproducible with: 2020.3.41f1, 2020.3.42f1, 2021.3.10f1, 2021.3.15f1, 2022.1.16f1, 2022.1.24f1, 2022.2.0b8, 2022.2.1f1, 2023.1.0a9, 2023.1.0a23
Not reproducible with: 2020.3.40f1, 2021.3.0f1, 2021.3.9f1, 2022.1.0a1, 2022.1.15f1, 2022.2.0a1, 2022.2.0b7, 2023.1.0a1, 2023.1.0a6
Reproduced on: Windows 11
Not reproduced on: macOS Monterey 12.2 (Intel)
Note: The regression is in the Editor versions and not in the Package versions
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- VFX Graph particles are not culled when using URP and Frustum Culling is enabled on VFX Mesh Output
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
Add comment