|
mame not reading system *.ini files
#380653 - 01/11/19 07:14 PM
|
|
|
I've created a cps2.ini with my custom settings for cps2 games, but mame don't seem to be able to find it for some reason, I've put it inside the "ini" folder and mame working directory, no success.
Say, set "samplerate" to "22000" (to make it damn obvious to spot), the verbose output still show the default "48000".
It works if this settings are set inside "arcade.ini" or "raster.ini", but not cps2.ini.
|
|
|
|
Re: mame not reading system *.ini files
[Re: 7n004]
#380654 - 01/11/19 07:23 PM
|
|
|
There is no system called "cps2". A CPS2 with no game cartridge has no main CPU so it doesn't make sense to emulate it. Please read https://docs.mamedev.org/advanced/multiconfig.html
edit: After checking that page again, the examples are bad. I'm not sure what "System-specific INI files" are supposed to be - just ignore item 4 until the page is updated to fix this. But there's no system called "cps2" in MAME, so it won't ever load "cps2.ini" as you've seen.
Edited by Vas Crabb (01/11/19 07:28 PM)
|
|
|
|
Re: mame not reading system *.ini files
[Re: Vas Crabb]
#380655 - 01/11/19 07:48 PM
|
|
|
|
|
|
Re: mame not reading system *.ini files
[Re: 7n004]
#380656 - 01/11/19 08:42 PM
|
|
|
I updated the page - the examples match MAME's beahviour now.
|
|
|
|
Re: mame not reading system *.ini files
[Re: Vas Crabb]
#380657 - 01/11/19 08:43 PM
|
|
|
|
|
|
Re: mame not reading system *.ini files
[Re: 7n004]
#380662 - 01/12/19 12:42 PM
|
|
|
Inside the 'ini' folder, create a new subfolder named 'source', and put these particular ini files there (cps2.ini, cave.ini, whaterver system).
Guessing which source system doesn't require command line either, the info window tells you which one it is every time you launch a game.
|
> MAME isn't about playing the games anyway.
|
|
|
Re: mame not reading system *.ini files
[Re: LensLarque]
#380663 - 01/12/19 12:48 PM
|
|
|
> Guessing which source system doesn't require command line either, the info window
> tells you which one it is every time you launch a game.
Yeah, but what if you want to know all the systems in a source file are? It's easiest to use -listbrothers for that.
|
|
|
|
Re: mame not reading system *.ini files
[Re: Vas Crabb]
#380664 - 01/12/19 05:19 PM
|
|
|
By the way,is there any category for handhelds? AS far I know, there are arcade, console and computer.ini.
|
RETRODANUART.COM
|
|
|
Re: mame not reading system *.ini files
[Re: Vas Crabb]
#380665 - 01/12/19 07:42 PM
|
|
|
> I updated the page - the examples match MAME's beahviour now.
Thanks for updating that page. That info is very useful.
|
"Note to Noobs:
We are glad to help you but simply posting that something does not work is not going to lead to you getting help. The more information you can supply defining your problem, the less likely it will be that you will get smart-alec replies.
C.D.~"
|
|
| John IV |
|
IV/Play, MAME, MAMEUI
|
|
|
|
|
Reged: 09/22/03
|
|
Posts: 1970
|
|
Loc: Washington, USA
|
|
|
|
Send PM
|
|
|
Re: mame not reading system *.ini files
[Re: Sthiryu]
#380667 - 01/12/19 10:39 PM
|
|
|
Their source is typically prepended with hh_*.
So you could make a driver level *.ini with \source\hh_sm510.ini for example.
|
john iv
http://www.mameui.info/
|
|
|
Re: mame not reading system *.ini files
[Re: John IV]
#380668 - 01/13/19 12:43 AM
|
|
|
|
|
Index 
Threaded 
mame not reading system *.ini files
Reply
[Re: 
