at “regular” mame (to be more specific, sdlmame at linux) i can edit ~/.mame/mame.ini and set rompath as “/where/my/roms/is;/where/my/bios/is” and the system “just works” (yeah, i know, it looks for the bios as parent rom at both directories and finds it at the bios dir) i’m trying as hard as i can to do the same with the mame core but i just can’t find how, do you guys have any clues?
hmmm we could add RETRO_SYSTEM_DIRECTORY/mame/bios as another rompath but nothing without recompiling I think
recompiling isn’t a issue for me if that’s what you mean
You can have your mame.ini in RetroArch\system\mame\ini\ with a rompath line, just like in regular Mame.
Perhaps you also need to set “Read configurations” to ON in Mame Core options.
[somatorio@tails retroarch]$ pwd
/home/somatorio/.config/retroarch
[somatorio@tails retroarch]$ cat retroarch-core-options.cfg
mame_read_config = "enabled"
mame_write_config = "enabled"
mame_saves = "game"
mame_auto_save = "disabled"
mame_mouse_enable = "disabled"
mame_throttle = "disabled"
mame_cheats_enable = "disabled"
mame_alternate_renderer = "disabled"
mame_softlists_enable = "enabled"
mame_softlists_auto_media = "enabled"
mame_media_type = "rom"
mame_boot_to_bios = "disabled"
mame_boot_to_osd = "disabled"
mame_boot_from_cli = "disabled"
[somatorio@tails retroarch]$ head system/mame/ini/mame.ini
#
# CORE CONFIGURATION OPTIONS
#
readconfig 1
writeconfig 0
#
# CORE SEARCH PATH OPTIONS
#
rompath $HOME/roms/mame;$HOME/roms/biosmame
doesn’t work
well it takes time and testing but you could achieve it easily, just look for the libretro files, basically we made a commandline loader, but we create the arguments dinamically, you can surely mess with it and add the system dir as a secondary rompath
[QUOTE=somatorio;38037] doesn’t work :([/QUOTE]
Sorry, thought it did.
It works for brightness, contrast, bios and some others.
ok, i’ll git clone and “play around” with it =p
[QUOTE=Tatsuya79;38039]Sorry, thought it did.
It works for brightness, contrast, bios and some others.[/QUOTE]
do you know if there’s a way to test if it is even reading the ini file (or the default path to it)? my ini file has skip_gameinfo set as 1, but the core isn’t skipping gameinfo with roms that doesn’t require any parent rom, so i think the ini is at the wrong path
Try:
brightness 0.2
and that should be pretty dark.
apparently the .ini is loaded after loading the parent rom
well, i’ll try the “git clone, try around and send a pull request if something work” approach (that’s why i love open source =p)