Main > Main Forum
Lazy button
farmecologist:
I had a similar problem and it turned out to be the microswitch. I replaced it and all is well now.
Ponderosa:
I have noticed a very similar problem with my IPAC setup. One button on my panel behaves like it is being toggled on and off. However, it only appears to do this immediately following the loading of a game. I use a key combination lalt+1+2 to exit from mame back to ArcadeOS. Then, I press 1 to load a different game. The lalt button does not register until it is pressed twice. I have tried with a couple of different microswitches -- same result. I have been just sorta living with this for about a year or so, but it does kind of bug me. It's like the lalt button gets stuck when you exit a game (using the key combination) and has to be unstuck when you launch a new game. Very strange. I do not use the shift function of the IPAC, because I let mame handle all of the key combinations. There are times when I exit all the way back to DOS, and it seems like the keyboard is locked up, when actually the lalt button is locked down. Pressing it again frees up the keyboard.
PCtech:
I would try changing microswitches with another button (if possible), and see if the problem "moves" to the new button.....if the problem moves to the new button, you know it is the microswitch....if the problem stays with the original button, I would re-check the setup on the IPAC.
Good Luck.
ahofle:
Yep, I had a microswitch 'bounce' problem like this. Move the microswitch to another button and see if that button exhibits the same symptoms. If so, replace the microswitch.
newmameguy1000:
Hey guys,
Just wanted to get back to you and let you know what happened.
I tested it under test mode and the button worked perfectly. But it still only registered every second time when I was in panel layout. So I figured I'd try it in a normal gameplay situation and it worked perfectly.
So what caused the problem? I had e-mailed Andy over at I-Pac and he asked me if it was mapped to an ALT key. It is in fact mapped to an ALT key and according to Andy: "If programmed as an ALT key this is normal behaviour in the panel test. It's a Windows issue actually. Gameplay is not affected..."
Someone may want to post this in the FAQ as I'm sure other people will run into this again. Anyway, just wanted to update people on what caused this.