Tafoid wrote: ↑
Wed Jun 07, 2017 1:54 pm
What game in particular are you attempting? Save States should largely work on most games, but are not given a clean bill of health until they flag gets added. NVRAM shouldn't be interfering (the STA folder is what needs to be cleared if you are autosaving a game).
If you can give us a specific example, it would help a great deal in being able to duplicate your issue and offer a possible fix.
Sorry for the delay, I tried some more things to make this work in the mean time.
I am trying to run a game I made for Neogeo myself, no surprise the save states doesn't work.
NVRAM shouldn't be interfering (the STA folder is what needs to be cleared if you are autosaving a game).
Maybe the save states isn't the problem then? What is sure is that removing the nvram folder solves the issue.
What is the STA folder? I don't see any folder with this name.
Anyway, I :
- checked that all .ini files used by MAME have "autosave" set to 0 in "CORE STATE/PLAYBACK OPTIONS".
In particular, [mydriver].ini file has "autosave" set to 0, which should override everything according to http://docs.mamedev.org/advanced/multiconfig.html
- launched MAME.exe, went to "configure options" -> "Advanded options" and checked that autosave was set to OFF
- then launched MAME through command line with the option "-noautosave"
Yet, when the game is halted, it creates a savestate in nvram/[mydriver], and MAME tries and loads it when the game is restarted.