Open ghost opened 1 year ago
Made a new discovery here with the UI. This issue goes away if you open the mame.ini file and change this line under CORE MISC OPTIONS:
ui cabinet
to
ui simple
Seems like the cabinet ui is not playing nice. Updating the title and description now.
Same behavior on Linux (Debian Sid, kernel 6.5.0-3-amd64, X.org 1.21.1.9, Nvidia 525.125.06) with mame version 0.260.
MAME version
0.255
System information
Windows 10 Home, 64-bit, version 22H2, USA, US English Installed RAM 8.00 GB AMD A6-5200 APU with Radeon(TM) HD Graphics 2.00 GHz
INI configuration details
Emulated system/software
UI only, commandline is not affected
Incorrect behaviour
Mame when run from the UI (double-click the exe) will only output snapshots to a directory matching the built-in default "%g/%i" string. Saving different values in any .ini file, whether it is
will not matter, they will be ignored UNLESS mame is run from the commandline, OR you set
-ui simple
first.Expected behaviour
snapname values in .ini files should be respected by the UI, not ignored.
Steps to reproduce
mame -cc
snapname %g/%i
tosnapname testINImame/%g/%i
and save the file.mame sf2
for this example.ui cabinet
toui simple
and save the file.Additional details
This one keeps tripping me up every once in a while, and I think it never worked right from the UI anyway? I prefer the string "%g/%g%i" to create files like "snap/sf2/sf20001.png" and so on, and noticed this going back to the UI for a bit because files were saving as just indexed 4 digit numbers.
I might need to check some random softlist stuff and see how those are managed, so for now this is affecting all the arcade stuff.
Can anyone explain the difference between using the forward and back slashes? They do the same thing when I interchange them and your docs don't clarify either, unless those are typos?: https://docs.mamedev.org/commandline/commandline-all.html#mame-commandline-snapname