Main Restorations Software Audio/Jukebox/MP3 Everything Else Buy/Sell/Trade
Project Announcements Monitor/Video GroovyMAME Merit/JVL Touchscreen Meet Up Retail Vendors
Driving & Racing Woodworking Software Support Forums Consoles Project Arcade Reviews
Automated Projects Artwork Frontend Support Forums Pinball Forum Discussion Old Boards
Raspberry Pi & Dev Board controls.dat Linux Miscellaneous Arcade Wiki Discussion Old Archives
Lightguns Arcade1Up Try the site in https mode Site News

Unread posts | New Replies | Recent posts | Rules | Chatroom | Wiki | File Repository | RSS | Submit news

  

Author Topic: Strange problem with MAME and start button mapping  (Read 5406 times)

0 Members and 1 Guest are viewing this topic.

UberCade

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 57
  • Last login:March 19, 2021, 11:22:32 pm
Strange problem with MAME and start button mapping
« on: April 22, 2010, 03:18:36 pm »
OK I have a very weird problem with my arcade cabinet, more specifically MAME. I have my whole control panel built and operational, using 2 GP-Wiz40 and 3 Opti-Wiz interfaces. For some reason, when I try to map the P1-P4 start buttons using the MAME config, I can never get it to work. Here's the weird part. When I enter the "general input" section, which maps the buttons for all games, I select for example the P1 start button, press the button on my control panel accordingly to map that button to P1 start, and it shows in the menu that the button is mapped, yet when I load a game, the button does not work. I have to use the number 1 on the keyboard, or number 2 for player 2, etc. The only way I've discovered so far to get around this is I have to map the P1 start button individually in the config for each and every game I load, which is a royal PITA considering the amount of games MAME supports. It seems to me that the individual game configs are overriding the general config and only allowing the number 1 key to work for player 1 start until I manually change it. Am I doing something wrong, or overlooking something? I've never had this problem on any other computer I've used MAME on, as far as I remember. Do the individual game configs override the general config? How can I make sure what I map in the general config will be inherited by every game I load?

By the way I have this problem with all the player start buttons, not just player 1. I just used player 1 as an example. I've also updated my MAME executable from 0.131 to the latest (0.137) and it still has this problem.

Howard_Casto

  • Idiot Police
  • Trade Count: (+1)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 19433
  • Last login:September 11, 2025, 10:29:12 pm
  • Your Post's Soul is MINE!!! .......Again??
    • The Dragon King
Re: Strange problem with MAME and start button mapping
« Reply #1 on: April 22, 2010, 04:17:18 pm »
Yes, the game-specific cfgs override the default.cfg

The way to ensure that they don't is to simply open your cfg directory and delete everything but default.cfg

With that being said, changing inputs in game is certainly easier, but you might want to use ctrlr files.  They are portable, and non-specific so when upgrade mame you don't have to worry about your cfgs suddenly stop working.