Question

Sometimes, a normal computer keyboard will only accept user’s inputs up to a certain key simultaneously. I got a logitech keyboard that can accept up to 3-4 key presses at the same time. The computer does not accept any more input if you press more than 4 keys for this keyboard. And it also depends on certain areas of your keyboard as well. Some locations allow more key to be pressed (like the arrow keys), while some locations permit you to press only 1-2 keys. This also differs from keyboard to keyboard as well. Some older keyboards only accept up 1-2 keys.

This isn’t problematic with usual office work, but when it comes to gaming. For instance, imagine a platform game, where you have to jump, attack, and control direction at the same time. This implies several key presses and some keyboards cannot accept such simultaneous input. However, I’ve tried this on several games and the amount of possible keyboard inputs seem to be also different. Therefore, we have two issues:

1. Keyboards have different amount of simultaneous inputs.
2. Some games can accept more keyboard inputs than other games.

At first, I thought this is hardware only problem, but why do some programs behave differently? Why some programs can accept more keyboard inputs than other programs? So how can we write our programs to accept more keyboard inputs?

Answer 1

If you want this fixed you need to purchase a pricey-er keyboard.

A program called GlovePie allows programmable input from different sources and can resolve this problem. GlovePie download page Here.~

For instance, I’m developing an RPG game, and my laptop’s keyboard cannot detect a combination of Run + Up + Left (run northeast). However, if I plug in my USB Logitech controller and map those exact keyboard keys (Up, Left, and B [to run]) to the controller’s buttons using GlovePie, I can do the command to run northeast with no issues.

As for your questions, I’m unsure exactly why programs react differently to keyboard input, but it could be with how they detect your input. For example: a Java-based game may detect DirectInput (the signature sent from your input/output devices) while an emulator (like the SNES emulator ZSNES for PC) may detect only the instance of the “Up” key being used.
Another input-emulation program, AutoHotkey, cannot control a java-based game because it doesn’t use the same form of input the game detects (it doesn’t use Java’s DirectInput).

So, in order to get more keys, I’d use a USB controller with GlovePie running.

Quote from another forum:
“It isn’t really a problem (technically). The solution is quite simple but increases the cost of the keyboard. Consider this simple problem: You have 64 keys. How many wires do you need if you want to distinguish every possible simultaneous key press. Answer: 65, One common and one for each key. However, if you arrange the keys in an array with 8×8 keys you only need 16 wires. 8 for the columns and 8 for the rows. This reduces the amount of pins on the keyboard controller chip and makes the keyboard a lot cheaper to produce. All keyboards I have ever seen are produced this way.”