Search Issue Tracker
Fixed
Fixed in 2020.3.47f1, 2021.3.19f1, 2022.2.6f1, 2023.1.0b3, 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
- [Android][BiRP] Depth processing is handled incorrectly on certain Android devices when using 2 camera's
- [APV] Cancelling Display Dialog Error is thrown after Adaptive Probe Volumes tab is open in Lighting Window
- [APV] NullReferenceException is thrown when baking Adaptive Probe Volume for a Terrain with Non-GI Contributing Tree Prototypes and multiple APV objects with different LayerMasks are present on the scene
- Hands are not recognized when using Hololens 2
- "OnTriggerExit2D" is called before "OnTriggerEnter2D" when object is destroyed immediately
Add comment