Build Your Own Arcade Controls Forum

Main => Software Forum => Topic started by: jets on February 21, 2003, 11:07:50 pm

Title: Mame ctrlr setup
Post by: jets on February 21, 2003, 11:07:50 pm
I'm just making some ini files for my joystick configs. I know that it's possible to have a specific setup for each different system. For example, I have a neogeo.ini that has a config that I edited to suit my cabinet. My question is what are the names for all the other systems? I know of cps2 but thats about it.
Title: Re:Mame ctrlr setup
Post by: Jakobud on February 22, 2003, 03:51:36 am
Hmmm...I wasn't aware you could setup different ctrlr files for each system...I do it for every game (which admitedly sorta sucks)....can you set this up for different systems?
Title: Re:Mame ctrlr setup
Post by: Howard_Casto on February 22, 2003, 09:24:21 am
Yes and no.... you can set it up for each speicality control you have available(e.g. lightgun.ini mouse.ini ect) or by the parent rom name or by the driver used..... all neogeo's use the neogeo driver(how aptly named) so you can make a neogeo.ini that applys to all of them.  All first generation capcom games use the cps1, second gen use cps2.... ect.....  you can look up a game in mame by typing:

mame.exe romname -listdetails  

and it will give you the driver information so you'll know what to name the file.  
Title: Re:Mame ctrlr setup
Post by: jets on February 22, 2003, 12:51:19 pm
Thanks to you I finally understand this.
Title: Re:Mame ctrlr setup
Post by: Jakobud on February 23, 2003, 02:49:00 am
Hmmm...so having a cps1.ini ctrlr file will apply that to every cps1 game?  What if I have another ini file for that specific game? Which ini file is excuted first?  The rom specific one or the system one?
Title: Re:Mame ctrlr setup
Post by: Howard_Casto on February 23, 2003, 08:56:32 am
the answer is they all are.. but they are overwritten in order, from the most vague to the most specific....

in other words you only have to define changed keys from the default.ini as it gets read first, then the input.ini then the driver.ini then the parent.ini then the romname.ini

however mame's internal config files can sometimes give it heck, so it's best to delete those.