Build Your Own Arcade Controls Forum
Main => Software Forum => Topic started by: Nightmare03 on February 29, 2004, 08:05:15 pm
-
Hey
Player1 Joystick up is mapped to F4, but when editing and removing that from my controller ini file it still brings up the damn pallete, how can i stop it ???!
-
delete your cfg files in the cfg folder
-
Ive done that too but it still happens :(
-
are you running it with a frontend that overwrite ini files? (I know that was a recent answer to another problem)
put mame in verbose mode and see what ini files it is loading.
-
How do i do that dude?
-
Ok i did it,
parsing mame.ini...OK.
parsing pacman.ini...N/A
parsing mspacman.ini...N/A
Using DirectInput 7
Keyboards=1 Mice=1 Joysticks=0 Lightguns=0
trying to parse ctrlr file windows.ini
Mouse support disabled
Joystick support disabled
Keyboards=1 Mice=0 Joysticks=0
Best mode = 400x300x16 @ default Hz
Primary surface created: 400x300x16 (R=0000f800 G=000007e0 B=0000001f)
Primary buffer: 44100 Hz, 16 bits, 1 channels
SSE supported
Sound buffer: overflows=4 underflows=0
Average FPS: 9.943082 (12 frames)
-
Ok i did it,
parsing mame.ini...OK.
parsing pacman.ini...N/A
parsing mspacman.ini...N/A
Using DirectInput 7
Keyboards=1 Mice=1 Joysticks=0 Lightguns=0
trying to parse ctrlr file windows.ini
Mouse support disabled
Joystick support disabled
Keyboards=1 Mice=0 Joysticks=0
Best mode = 400x300x16 @ default Hz
Primary surface created: 400x300x16 (R=0000f800 G=000007e0 B=0000001f)
Primary buffer: 44100 Hz, 16 bits, 1 channels
SSE supported
Sound buffer: overflows=4 underflows=0
Average FPS: 9.943082 (12 frames)
I only see mame.ini (which isn't a controller config file) and possible windows.ini in the default ctrlr folder being loaded.
-
Yeah the windows.ini is what i edited for my controls, should i make a different one?
-
You should just leave windows.ini as it was. Have you edited std.ini? check in there as mame looks at that file first, then looks at any specific ctrlr files you have set (have you made any of them?)
-
Hey,
I just did what i did before ( edit the controls in mame ) and it works now ( it didnt before, obviously )
Thanks for the advice,
Nightmare
-
You should just leave windows.ini as it was. Have you edited std.ini? check in there as mame looks at that file first, then looks at any specific ctrlr files you have set (have you made any of them?)
That would be incorrect. std.ini is not used. It's there to show you what you can set (and the defaults).
Default.ini is the default. Plus it is wise to setup a ctrlr folder with your settings in and use that.
-
The pc I have at work only has default.ini located under the various crtrl folders (HotRod, SlikStik, XArcade) and nowhere else that I could see. I don't use those ctrlr folders here (have set my own up at home though) I am curious to know where would it be getting the control info from? I was under the impression mame checks std.ini first, then into specific ctrlr folder for default.ini, then to specific game.ini (ie mk.ini).
-
The std is just a printout of the hard-coded internal defaults in mame. It doesn't have to read it because they are the defaults. Actually mame reads the defaults, overridden defaults at the driver level, cfg files and then ctrlr files. This is very annoying btw.
Remember, ctrlr file saving is new. You can delete your entire ctrlr folder hierarchy and mame will still run just fine.
-
yep, at the core mame still runs ont he cfg files. Actually the cfg file inputs will override the ctrlr files.
Normally for ctrlr files you'd make your own folder and put configurations in there. Then in your mame.ini configure it to use that folder.
-
Yeah it seems to me that ctrlr files should be right after driver defaults as you have to actively make a ctrlr file and cfg files are automatically made.