I currently have a mamewah driven arcade cab. It sports a 2 player 6 button CP wired to an ipac2 USB. I also have a pass-through usb kayboard and a ubs mouse connected. Ive set up various ipac configurations for each of the emus as well as mamewah itself and these are written to the ipac by the 'pre' and 'post' Mamewah command lines.
(The mamewah ipac file doesnt have any Switch keys.)
Everything worked fine - until tonight. I must have done something; i know its not likely that a computer will suddenly just 'not work' as it did before; but i cant think of anything ive done.
Each time i use the player1 start button on the CP to start a game (its mapped to '1' in the mamewah ipac config file) it starts the game as usual - but then that key press is continually pressed for the next few seconds.
In a NES game like 'Batman (U)!' this just skips straight past the start and intro screens and starts the game. Leave the game running for a few seconds, exit with escape, and everything is fine.
In the PC games that i have running from Shortcuts instead of rom files, it creates a loop where i cant get out of the game in question. Instead of pressing '1' several times during the game intro, it presses it again when the game exits.
Take Virtua Tennis for example. Start the game using the control panels 1p start button ('1') and it starts fine. Exit the game using escape and it goes straight back in again. It doesnt matter how long i leave the game running, it just goes straight back in. Actually, there is a tiny burst of the Mamewah background music - but pretty much straight back in.
The only way to prevent this is the enter key presses during the transition from the game exiting and starting back up again - left/right/left/right on the joystick for example. This seems the disturb it and mamewah comes back up.
Heres the really strange part - if i start the games from the pass-through Keyboard i never get this problem. It works fine everytime. This leads me to point at the Ipac, but im not sure whats going on yet so im not going to be to hastey.
I dont think ive got anything set wrong - as last week it was fine!
Ever heard of this problem before?