Am I crazy or does input not register sometimes?

[Lorethys]

Admittedly my keyboard can be finicky when I play rhythm games, but I've noticed there's times where my input is not registered well outside of the very specific circumstances that cause my keyboard to act up.
During the tutorials especially, it seems like I have to mash all the keys after closing a dialogue box to get the game to register them again.

At first I thought it was just me discovering that my arrow keys don't work very well but even after remapping to WASD I encounter the same trouble. Has anyone else noticed this and/or does anyone maybe know a solution I could implement my end?

[Brace Yourself Games]

Hi Lorethys! Sorry to hear you're having trouble :( It's possible that keyboard ghosting is the culprit here. Can you go to this site and check what happens when you hold down all arrow keys or all WASD keys at the same time?:

https://www.microsoft.com/applied-sciences/projects/anti-ghosting-demo

It's possible that your keyboard is simply not capable of registering all keys simultaneously.

[Lorethys]

Originally posted by Brace Yourself Games:

Hi Lorethys! Sorry to hear you're having trouble :( It's possible that keyboard ghosting is the culprit here. Can you go to this site and check what happens when you hold down all arrow keys or all WASD keys at the same time?:

https://www.microsoft.com/applied-sciences/projects/anti-ghosting-demo

It's possible that your keyboard is simply not capable of registering all keys simultaneously.

Well, I only have so much hand to test with but I can indeed hold down both WASD and arrow keys at the same time and have them all register. Alternatively, I can hold down WASD + at least 14 other keys.
I do often have a controller connected, but outside of an uncommon occurence of stick drift leaching to my M+KB controls, it hasn't interfered with keyboard input prior.

Admittedly it could be my imagination that input doesn't work during standard gameplay, but I have certainly had unresponsive input during the tutorials. I'd press a key to confirm/close the dialogue box and then each key would be down for a few inputs.

[Clone Fighter]

Originally posted by Lorethys:

<...> but I have certainly had unresponsive input during the tutorials. I'd press a key to confirm/close the dialogue box and then each key would be down for a few inputs.

Ahh, this is a known issue. Holding down a key while a tutorial dialogue box opens up makes that key's first input not register. (It's as if the key still thinks it's held and is waiting for a release).

"But I'm not holding down anything?" - Technically, you are. The textbox triggers so fast after the last necessary input that I found myself often outright unable to release the key before it popped up. This must be what's happening here.

[alexa_byg]

Originally posted by Clone Fighter:

Originally posted by Lorethys:

<...> but I have certainly had unresponsive input during the tutorials. I'd press a key to confirm/close the dialogue box and then each key would be down for a few inputs.

Ahh, this is a known issue. Holding down a key while a tutorial dialogue box opens up makes that key's first input not register. (It's as if the key still thinks it's held and is waiting for a release).

"But I'm not holding down anything?" - Technically, you are. The textbox triggers so fast after the last necessary input that I found myself often outright unable to release the key before it popped up. This must be what's happening here.

Clone Fighter is correct here - this is something we have eyes on to fix, but we have some backend architectural work that takes priority right now :) If you have unresponsive inputs during regular gameplay (not tutorials) that would be a different bug entirely and I'd love to hear more!