If we have turned off Num Lock and we click on the arrows, then put Print Screen.
At the same time, everything works fine in the editor (Shortcuts), the problem is in the Input System.
On the screenshot of tanks demo.
Version 1.0.0
Unity 2019.3.0f3
?
Same issue here: was fixed by pressing the NUM LOCK key
1 Like
I’m also looking at the new Input System, and so far I’m a little perturbed by some of the inconsistencies. I get that it’s a new system and will take some time to iron out, but NumLock should NOT affect the detection of Arrow Keys. No Operating System in the world changes the Arrow Key input based on NumLock’s status… This is a bug, and I hope Unity addresses this soon. In the meantime however, thanks for the workaround, it works for me… although I’ll be sticking to anything but this new system for now.
This post is one year old and still no solution?
Seems so… but knowing coding it might be more intricate of a problem then we think… hopefully we get something soon.
1 Like
Ok, but at least someone from unity should have acknowledged the bug, said they are working on it.
They seem pretty active here on the forums, not sure why this one was ignored.
1 Like
I haven’t checked if it’s fixed for myself as I’m just staying away from the New Input System until I hear of big changes, but as far as I’m aware, it does almost seem to be getting ignored… maybe more people have to bring this to their attention as well.
Out of curiosity, are you using the old system or some other third party system? I’m thinking of ditching the new system too, too many bugs and some things are unnecessarily hard…
1 Like
We’ve been using Unity 2018 for our projects, and we recently made the switch to the latest LTS (Long Term Support) of Unity (which right now is 2019), and continue to update when a newer version of the LTS comes out. During our time using Unity 2018, we 've made the switch to a package called “Input Manager CC”, by “VersionMaybe.” since it lets you change controls at runtime.
“Input Manager CC” still uses the old Input System, and even when we don’t use that, we use the old Input System. If we create a project with Unity 2019, we tend to use both so that way we can use the old Input System, AND parts of the New Input System, like the native Gamepad and Rumble support.
I wish to stress however that this is not at all permanent and when the New Input System becomes satisfactory to us, we will be switching to it more or less full time. We also are not the creators of “Input Manager CC”, AND aren’t sponsored by them… but we love the package and hope you might find some use out of it too
Here’s to hoping this issue gets resolved, and that everything Unity makes in the future being great
~ Shaggy39
Hi, I’m the author of this thread. I recommend you to forget about InputSystem and buy asset “InControl”, which works fine with both gamepads and keyboards
1 Like
I’m planning on buying rewired, but it sucks that i have to rely on a paid asset to have some basic functionality
Same issue here.
1 Like
Issue still present in Input System 1.1.0 pre.5.
There’s no way they still haven’t addressed this
I just ran into this issue due to a player report. I can’t believe this bug. 2020.3.15, Input System 1.0.2, etc.
I can’t believe they still didn’t fix it… it’s only been TWO YEARS
1 Like
Just ran into this issue myself with the latest version of input system…
Did you file a ticket?
Just opened Case 1359217.