This bug was confirmed in Windows port, ver 1.42 official and the 2/10 WIP.
When you specify a relative path for freeze files and other things, zSNES screws up a little bit.
To reproduce:
1. Have ROM in a directory not the same as zSNES executable.
2. Have save states and/or srm files in a directory not the same as the ROM or zSNES.
3. Specify the RELATIVE path to the save states/srm files either using zsnesw.cfg or in the "Saves" line of the Paths dialog within zSNES.
4. Check "auto incrmnt save slot" and "start at latest save" in the Saves dialog.
5. Load a game for which you have save states and/or srm files in your save state directory.
Results:
1. Pressing F3 will show you all save states you have for that game, contained in the save state directory, but the selector box will NOT be on the latest save.
2. Attempting to load an srm file for the game will show you no in-game saves. This is because:
3. zSNES does not recognize the relative path to the save state directory for in-game saves. Instead, it creates a new SRM file in the same directory as the game.
4. Save states still get saved to the correct relative path for save states.
Also, I tested this bug with and without spaces in the directory names. Lastly, I tested with two games: Chrono Trigger and Secret of Mana.
Relative paths not working quite right
Moderator: ZSNES Mods
Relative paths not working quite right
[url=http://zsnes-docs.sf.net]Official ZSNES Docs[/url] | [url=http://zsnes-docs.sf.net/nsrt]NSRT Guide[/url] | [url=http://endoftransmission.net/phpBB3/viewtopic.php?t=394]Using a Wiimote w/ emulators[/url]