This wasn’t happening before but now it is, asked other people and they have the same issue.
Doing a simple
shows us that both the I and O keys don’t show up, this could be related to zoom in and out feature, binded to the same buttons, but other roblox system commands don’t share the same problem. This is definitely a bug
May 16, 2021, 1:01am
Most likely what you stated about the zoom buttons.
This may be because users could easily get stuck in GUI’s while in first person.
How’d I go about fixing this? It wasn’t a problem until recently
May 16, 2021, 1:05am
zoom in and out feature
then detect the camera zooming out and in
Can’t tell if you are joking or not, but I’m not using roblox’s base camera
May 16, 2021, 1:08am
Pretty odd, tried it my self and it does the same or doesn’t print “I” and “O” not even GetMouse() would. All though the keycode enums do exist for them (
funny enough it works in an older versions, rblx.lua is wild
that’s not a fix either way though
This should’ve been put in
This began happening to me too, just today actually. The i key does not register at all when testing in studio, whereas it does register when in the Roblox player.
May 16, 2021, 12:40pm
An impractical ‘do this alongside this’ bandaid solution for something that shouldn’t be an issue in the first place is NOT how you fix things xd
Yep along with this other post it definitely seems to be a bug especially with input began for the IO keys.
@colbert2677, @nin900500 and I are getting the same issue but for context action services for the IO keys definitely seems related.
I’ve done some testing within studio, seems like for some reason even with a high priority the keycode for the IO keys only prints when the user input state is ended.
Definitely has sometihng to do with the IO camera key binds. But not sure why it only allows for InputStateEnd and not InputStateBegin.
Reference IO core buttons: