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
- “Screen position out of view frustum...” errors are thrown when zooming out in the Scene view after creating UI GameObject
- CurveTexture is not being released when unloading AssetBundle containing a Scene with ColorCurves post-processing component in Global Volume
- Crash on ExtractActiveCasterInfo when navigating the scene view in a project with specific lighting data
- Build Profile name increments when numeric suffix is removed from duplicate Profile name
- "Unrecognized block header in profiler data file, stopping deserialization" error is shown and no more profiler data is recorded when the Player is connected and profiler recording is enabled/disabled few times
Add comment