Build Your Own Arcade Controls Forum

Main => Software Forum => Topic started by: drventure on September 25, 2010, 12:04:53 pm

Title: Mame doesn't recognize Keys or sticks in config screens?
Post by: drventure on September 25, 2010, 12:04:53 pm
Very strange problem I'm getting. Just wondering if anyone else has ever seen it.

After my cab was knocked out by lightning, I had to replace the MOBO.

Everything else looks good.

I put it all back together, booted up, and can run MAME, MALA, etc. I've checked all the game controllers in the Windows Control panel and they all work just fine. The trackballs all control the mouse properly, spinner knob as well.

And my IPAC lights all the proper buttons in WINIPAC...


BUT

When I load MAME, and go into the config screens, and try to change the input for, say P1 UP, I hit ENTER to change it entry, and then.... nothing.

I move a stick, press buttons, even use the keyboard to enter a key and nothing happens. It's like MAME doesn't see any input at all

HOWEVER, P1 coin works, and P1 Start works

Anyone ever seen behavior like this?

I'm begining to think that maybe a lot more was damaged than just the mobo, but, like I said, everything seems to operate just fine when checked outside of MAME so, that wouldn't seem to be the case.

Any thoughts?

Title: Re: Mame doesn't recognize Keys or sticks in config screens?
Post by: abispac on September 25, 2010, 10:34:31 pm
have you try erasing the default.cfg file? sometimes that does the trick...
Title: Re: Mame doesn't recognize Keys or sticks in config screens?
Post by: drventure on September 26, 2010, 12:13:46 am
Have not, but I'll give it a whirl. Thanks!
Title: Re: Mame doesn't recognize Keys or sticks in config screens?
Post by: drventure on November 22, 2010, 07:17:08 pm
Not to necro my own thread but that fixed it. Thanks!
Title: Re: Mame doesn't recognize Keys or sticks in config screens?
Post by: drventure on November 22, 2010, 10:23:28 pm
Oddly enough, this happened again just now, hence the necro. I was searching for this behavior and had forgotten about this fix.

Very strange though.