MAME core ignores the system folder path

Whenever i change something in a MAME game (controls for instance) it doesn’t save them. It should be saved in the system folder i think but it doesn’t happen.

Is this a known issue?

(i’m using MAME2014 as the normal one has issues with the screen size and text)

I think you need to create the structure for it. At least one/some of the MAME cores will create the structure for you but the others require you to do it yourself. I think it’s system > mame > whatever

That didn’t work. Only MAME reads and writes in those folders, MAME2014 ignores them. Unless it needs a different structure but how can i know what it is?

I would use MAME but the text graphics are messed up in all games.

You could use this MAME 2015 I saved from the buildbot last year: https://www.dropbox.com/s/tj0r36qnucii7wx/mame_libretro.7z?dl=0

It saves NVRAM and CFG stuff in <save folder>\MAME 2015.

[QUOTE=Awakened;40919]You could use this MAME 2015 I saved from the buildbot last year: https://www.dropbox.com/s/tj0r36qnucii7wx/mame_libretro.7z?dl=0

It saves NVRAM and CFG stuff in <save folder>\MAME 2015.[/QUOTE] Thank you man, it works great!

From now on, i’m going to backup all the good cores like this one before updating.

[QUOTE=GemaH;40925]Thank you man, it works great!

From now on, i’m going to backup all the good cores like this one before updating.[/QUOTE] No problem! I always test a few games after updating a core and keep a backup of the previous core dll in case I find problems later. And I report regressions on the github if they’re not already known.

The latest MAME code was integrated into the newest MAME core fairly recently and caused some regressions, so we have to be patient for those to be ironed out :slight_smile: