View Full Version : TankStick button mapping prob
Drakin
07-31-2009, 08:24 AM
OK I have a prob with mapping the "Q" button on my tankstick to Mame games...I have 3 keyboards being registered in my hardware...one being the USB wireless keyboard, Led Wiz, and the Tankstick....Whats weird is when I hit tab while in a Mame game to map buttons its only the Q that wont read, yet it works fine and its registered in the Tankstick utility that check the buttons.....any ideas?
the Q button would be for player 2, 3rd button on the left top row. FYI
Does it really matter how many keyboards I run?
mk211
07-31-2009, 02:17 PM
I had the exact same problem. I fixed mine by going in and editing Hyperlaunch.ahk. I changed "q" in the "exitScriptKey" to another letter. (remember to compile with AutoHotKey). MAME would then recognize the q on the tank stick. However, this caused my 2 player coin (i.e. 4) to stop working. Therefore, I just changed to normal launch in HyperHQ and everything was back workiing. I know this isn't a very good solution, but I figured it might help.
Drakin
07-31-2009, 06:28 PM
Thanks for the help...I however don't have a Hyperlaunch.ahk file....is that wierd or what....how can I make one?
mk211
08-01-2009, 12:34 PM
Sorry, I just assumed you were using hyperlaunch to load MAME. If you use hyperlaunch, there is a file (hyperlaunch.ahk) to change the settings for hyperlaunch. I guess it was just a coincidence that we both had problems with the q button on the tankstick.
Drakin
08-01-2009, 02:58 PM
no I do use Hyperlaunch to load mame....I am however using a command line version of mame with Hi Score support.
Drakin
08-01-2009, 04:12 PM
I had the exact same problem. I fixed mine by going in and editing Hyperlaunch.ahk. I changed "q" in the "exitScriptKey" to another letter. (remember to compile with AutoHotKey). MAME would then recognize the q on the tank stick. However, this caused my 2 player coin (i.e. 4) to stop working. Therefore, I just changed to normal launch in HyperHQ and everything was back workiing. I know this isn't a very good solution, but I figured it might help.
Well did what you suggested and walla I got a "Q" key working!!
Thanks mk211:)