Hagstrom KE72 and joystick diags

[(+_+)]

Hi everyone,

I finally started toying with my KE72 after months of procrastination. I was testing button and joystick contacts when I noticed that joystick diagonals seems to print both mapped letters once and then repeatedly print only one of the 2 letters afterword. Shouldn't it fire both continuously since 2 contacts are being pressed? I have my .cfg file set up to fire repeatedly for joystick movement. I play games like robotron where it is essential that diagonals fire repeatedly. Does anyone know if this is an issue or is it just because I am spitting out my test results to a notepad document.

Thanks in advance.

[TalkingOctopus]

I have a ke72 and have never done a test like that.  I have absolutely no problem with diagnols.  For my config, I mapped each button to a single key.  Have you tried playing a game and had this problem?

[(+_+)]

I haven't played a game yet. I'm in the process of building my Mame cab. I was just testing some of the contacts in a rudimentary way to see if the KE72 was working. As long as Robotron rapid fires and continously runs in all directions, I'll be a happy camper.  

Thanks.

[RandyT]

I finally started toying with my KE72 after months of procrastination. I was testing button and joystick contacts when I noticed that joystick diagonals seems to print both mapped letters once and then repeatedly print only one of the 2 letters afterword. Shouldn't it fire both continuously since 2 contacts are being pressed? I have my .cfg file set up to fire repeatedly for joystick movement. I play games like robotron where it is essential that diagonals fire repeatedly. Does anyone know if this is an issue or is it just because I am spitting out my test results to a notepad document.

Since this question pertains to all encoders and keyboards in general, I'll give this a shot.

What you are seeing is not an issue.  It's just the key-repeat in action, and like the keyboard it's emulating, only the last key pressed is ever repeated.  

Your software was written with a real keyboard in mind, and as such, has no problems ignoring the repeated key.  This repeated key will also have absolutely no negative effect on your gameplay, unless you have a very slow encoder.

Suppose the "A" key is pressed.  The controller will send a "keydown" command for the "A" key.  Once that command is received, the software ignores any future "A" key "keydown" commands until an "A" key "key release" command is issued.  Only then will it honor another "keydown" command for the "A" key.

This way, the software always knows what the state of the keys are, and since the key-repeat only uses "keydown" commands, the software never gets confused.

Hope this explains things a bit better.  

RandyT