Go into any game and press . (dot, period) on the numpad to observe the bug
Happens in every game all of the time
(also happens in Studio)
do you also have this problem?
- Yes
- No
0 voters
Go into any game and press . (dot, period) on the numpad to observe the bug
Happens in every game all of the time
(also happens in Studio)
do you also have this problem?
0 voters
if you watch the video you’ll see that my numpad lights are on
I did but I can’t repro the bug
I tried too and it worked just fine for me.
This problem occurs for me on my Razer Cynosa Chroma keyboard regardless of num lock enabled or not. (No macros attached to any of my keys.)
Can you submit a link to the game in which you checked it? . This is probably a mistake in the game itself and not in the Roblox because I, like 70% of voters, are all right.
Is the keyboard working correctly?
it could be my computer idk but it’s been like this since forever in every game and in studio
Well. Then, in this case, try to check the relevance of the drivers for the USB ports. Perhaps they are satisfied or not relevant.
Have you tried reinstalling Roblox and Studio or Reboot your PC ?
If it doesn’t occur on everyone’s device then you should do due diligence of adding details on your setup.
@buildthomas I definitely agree with that, I’d probably get to that when I’m free.
Thanks for notifying.
@Deezater, Yes I restart my Pc, I even re-installed windows and this still happens.
This is happening to me right now. I am in-game and my num-pad keys are not working. [EDIT] I restarted my PC and it is back to normal.
I am seeing this…on an HP laptop. Some observations:
Enum.KeyCode.Delete
when it should be gettingEnum.KeyCode.KeypadPeriod
, which it does in Studio on the same computer.The numpad works fine for me while using in-game chat. I have no problem with this situation. Maybe it’s more of an issue with the keyboard?
How about the Numpad-period–That’s what this is about? I would say that it is possible, however it’s
still a bug because there are different behaviors in Studio vs. the Desktop app in terms of the keycode
seen on the same computer, therefore there is a programming difference which causes the problem.
Closing in favor of a better written version of the report: UserInputService not reflecting Keypad inputs properly (SHIFT and KeypadPeriod)