Search Issue Tracker
Fixed in 2018.3.X
Fixed in 2018.2.X
Votes
0
Found in
2018.2.0b2
Issue ID
1034380
Regression
Yes
NumLock isn't working on 2018.2.0b2
To reproduce:
1) Create new project
2) Select any object
3) Try to write using numpad in any field in inspector
Expected: It works as expected depending on Num Lock setting
Actual: No matter the Num Lock setting, Numpad always works like Num Lock was disabled (special buttons instead of numbers)
Reproduced in 2018.2.0b2
Not reproduced in 2018.1.0f2
Comments (2)
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
- 'Load texture data on demand' corrupts Unity's packages Gizmos in Scene View
- "Unable to add Renderer to the Scene after Culling." error when adding a Terrain in a HDRP project
- [Vulkan] "Dont Care" LoadAction resets to "Load" when running on Mali devices
- Building the Player takes 25-50% more time in Unity 6 compared to 2022.3 when the IL2CPP scripting backend is selected
- Rigged GameObject doesn’t return to its idle state when disabling "Preview" and the GameObject has nested rigged GameObjects
GregoryFenn
May 29, 2018 16:37
P.S. the bug exists in the editor IDE too, not just within games. I need to use the alpha-numeric keys (the left to right ones) to write digits in the Inspector in 2018.1.
GregoryFenn
May 29, 2018 16:32
I have the same issue - I today installed 2018.2 and seemingly succeeded in loading and building a game made in 2018.1. But my numpad 4268 is acting like LeftDownRightUp. In my case, I had a fully working camera arm that would move or rotate with the relevant numpad digits, but now it just moves my character as if i were hitting WASD. IT worked fine this morning on 2018.1 so the bug must be new. I'm using the semi-official Linux build, released on Friday 25th May.