It seems to affect all games. The 2 that i play the most(and would like a config file for) are ikari warriors and boot hill(i used to use rotary joysticks for boot hill, works really well!).
Okay. I don't know why then. If I have time I'll look into it. (Some other stuff has
just grabbed my interest, and I mean ten minutes ago. Analog+ related, but won't be visable for a little while, if anyone's interested in what grabbed me)
This may sound like a stupid question but how hard would it be to writeconfig files for games? (off road for 1, emu + didn't support it). that would solve all the problems.
Thanks Todd
Well, each game has it's own .cfg file "layout". The layout of the file depends on:
- what inputs the game uses
- how many of each input
- the order they are listed in the game driver
This is
very game dependent. Also, the .cfg file is not saved in text, so editing by hand, while possible, is hard, needs a hex editor, knowledge of what the hex numbers mean to mame, and you need to know the layout of each .cfg file you want to edit so you can edit the correct spots.

If someone wants to write a mame .cfg file editor, though, mame already has the layouts of the .cfg files (in the game drivers), functions that get the info out of the game drivers, and functions to load and save .cfg files (in inptport.c and input.c), so you can steal a lot of the needed code. And the .cfg file layouts will be updated for you with each release of Mame, if you don't edit the code from you use. You just need to design a (G)UI that edits the information. I have thought about doing this, but don't have the time and experence in user interfaces, and I'm using my free time (what little I have) in Mame:Analog+. Any takers?