GroovyMAME won't work with Corsair Strafe keyboard?!

[BuckoA51]

I recently swapped the keyboard on my GroovyMAME/CRTEmudriver PC from an old Logitech Elite to a not quite as old Corsair STRAFE mechanical (Model RGP0017). This used to be my main keyboard but it broke down so I replaced it. Turns out it was just a broken fuse and my friend was able to fix it for me.

I had no problems with this keyboard until I tried to play some GroovyMAME tonight (build 0289), and GM won't see the keyboard at all. I cannot bind any controls, navigate the menus, nothing. If I go with the mouse into rebinding the controls and try to rebind, GM just doesn't see the key presses at all. It's like the keyboard isn't even connected.

I tried changing keyboard providers, turning on global inputs, deleting ini files to rebuild to defaults, no difference. the ONLY place GM sees the keyboard is if I type to search in the games list. There it'll only see letters, not the escape to quit searching.

Putting back the old keyboard on the same USB port things worked fine. Swapping for a CherryMX that I was saving for another project also worked fine, but nothing I tried could get GM to like the Corsair keyboard. Heck I even installed Corsair bl***y Strafe, no firmware updates no driver updates, waste of time.

Every other app on the PC sees the keyboard just fine, including an older build of MAME I had lying around on there.

So what exactly does GM have against my Strafe keyboard?? I'd prefer to use this keyboard as I do tend to play with the lights down low to get the best benefit from the CRT, so being able to turn on keyboard backlighting can help. If anyone has any ideas please do share!

Edit - Forgot to say I'm on Windows 10 extended support.

[Zebidee]

Try going into Device Manager. Find the USB keyboard entry for the Corsair, right-click and uninstall it. Then you'll probably get a ! icon and you can try to right-click and re-install. See if it works after that. You may need to unplug the keyboard after uninstalling it, and on re-plugging it in (perhaps try a different USB port) it should be automatically installed. If Windows is doing its job properly anyway.

You might need to repeat the process multiple times until it "sticks".

[Calamity]

You said you tried to change the keyboard provider. Could you confirm -keyboardprovider dinput and -keyboardprovider win32 don't work either? Also, does your keyboard work with current baseline MAME?

[BuckoA51]

Could you confirm -keyboardprovider dinput and -keyboardprovider win32 don't work either?

Yeah they didn't work either, unless that setting doesn't apply until you quit and re-enter?

Also, does your keyboard work with current baseline MAME?

I'll try tonight, it worked with an older build I'm sure of that.

[Calamity]

Could you confirm -keyboardprovider dinput and -keyboardprovider win32 don't work either?

Yeah they didn't work either, unless that setting doesn't apply until you quit and re-enter?

Of course, try it from command line always:

Code: [Select]

mame sf2 -keyboardprovider dinput