Search Issue Tracker
Fixed
Fixed in 2021.3.28f1, 2022.3.2f1, 2023.1.0f1, 2023.2.0a14
Votes
1
Found in
2020.3.39f1
2021.3.9f1
2022.1.17f1
2022.2.0b8
2022.3.2f1
2023.1.0a11
2023.2.0a1
Issue ID
UUM-15023
Regression
No
Numpad Equals key is not recognised correctly or not recognised at all
How to reproduce:
1. Open the attached project “IN_14911”
2. Open “Start” Scene in Scenes
3. Enter Play Mode
4. Connect a keyboard that has a Numpad with an equal key (i.e.Mac Magic 109 Keys Keyboard)
5. Press the “N” key on a keyboard
6. Press the “=” key on a keyboard
7. Observe the Game View
8. Press the “L” key on a keyboard and repeat steps 5,6
Expected results: “=” key gets recognised
Actual results: “=” key gets recognised incorrectly or not recognised at all
Reproducible with: 2020.3.39f1, 2021.3.9f1, 2022.1.17f1, 2022.2.0b8, 2023.1.0a11
Reproducible on: Windows 10 Pro
Notes:
- Start scene will allow you to select the New Input test Scene by pressing N or the Legacy Input test scene by pressing L
- Issue not reproducible with “+/=” key
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
- Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
Add comment