Enter Key Not Working

[Cerebral]

Can't figure this out so maybe someone else has figured it out... Game runs fine and all but when I go into a terminal or computer in the game I can type just fine but pressing the Enter key has no effect (which means I can't really play)... any ideas???

[Erik]

What operating system are you on?

[Cerebral]

The offending machine is Windows 8.0. I've run it on Windows 10 (my other PC) with no problems.

[Erik]

Strange... I've got no idea what could be causing this. Are you using some kind of special key mapping on the problematic computer?

[Cerebral]

not using any key mapping or macros... I'll poke around on it a bit more and see if I can get you more info. Thanks so much for taking the time though to respond and try to help. I wish more developers did that for their player base... very refreshing. Also, I love the game. A friend suggested it to me and I am enjoying it greatly.

[Erik]

Have you tried the return key on the numpad?

[Cerebral]

Thanks... yeah, tried that... didn't work.

[phlummox]

Cerebral, a suggestion: Install passmark's KeyboardTest on both PCs, press the main Enter key and the number pad Enter key and compare the results.

http://www.passmark.com/products/keytest.htm

My main Enter key returns "Enter" and "13 (0xd)"
My num pad Enter key returns "EnterN" and "13 (0xd) E"

In-game, my number pad Enter key does NOT work even though all the other number pad keys work. Your OS or keyboard may not be differentiating between the two or they're both set to EnterN.

You can find a keymapper utility to probably fix this issue if you really want. But either way this info might help Erik. It would be really nice if any ol' Enter/Return key worked.

[dunbaratu]

Erik, this souds suspiciously similar to a bug I've seen before with Unity4 and Linux.

We were looking for the keycode 0x000d for the Enter key, but on some Linuxes it failed to work because the key is really sending code 0xff0d instead of 0x000d (the high byte padded with 1's instead of with 0's). In the end we just punted and gave up trying to figure out why and just made the code accept either 0x000d or 0xff0d as both meaning Enter.

This doesn't seem to be a thing caused by the OS itself, but rather by something Unity is doing in its Linux port for some reason.

If you want to see the long description from our own project, here's the whole issue:
https://github.com/KSP-KOS/KOS/issues/206

It wasn't just the ENTER key that was affected. It was pretty much any control key with ascii code less than 32 (all the "control characters" like backspace (ctrl-H) , tab (ctrl-I), etc).

In the end our fix was just to make sure that for any keycode we were testing in the range 0x0000 through 0x0020, we also allowed it to count if it the high byte was 0xff instead of 0x00.

[Erik]

@dunbaratu That's some seriously awesome help! Splendid, thanks a lot, I'll try that!

[Cerebral]

OK, on my windows machine that it DOES work on, my Enter key (the one on the main keyboard not on the number pad) returns Windows Key code 13 (0xd)... I think this is what you are asking for... I know when I program I use Chr(13) for charrige returns... so it seems to match. I'll check the machine that it doesnt work on tomorrow as I left that laptop at work.

Thanks again Erik for the great support and also thank you to the community for your assistance! Full disclosure: I'm a little tilted to like your game... my RL name is Eric... LOL!

[Cerebral]

Hmm... on my laptop it also reads 13 (0xd)... I did notice however that when I press the return key KeyTest is highlighting the number pad Enter key....????

[phlummox]

Hm, sounds like an issue with your laptop then Cerebral.. both keys are being interpreted as a numpad enter. You may want to edit your registry or download SharpKeys to remap your Enter key(s) until Erik can fix for the numpad enter issue.

[Cerebral]

Thanks Ƥhi Ȥerøth, that fixed the issue for me. Not sure why the key would have been mapped the same for both keys, I bought the system brand new and never remapped a key in my life...

Erik, not sure if this will help you on your end of not but my Return key was originally mapped to E0_1C and I remapped it to 00_1C which corrected the problem.

Thanks to everyone again!

[Erik]

@Cerebral OK, thanks! Glad you found a workaround.