save location bug with zsnes 1.42

chronomitch · Post by **chronomitch** » Sun Jan 30, 2005 8:14 pm

I currently have zsnes set so that my game saves are in the folder "C:\UNZIPPED\SNES\SAVES". Most of the time the save state files are saved correctly in this folder. However, sometimes the save state files are saved to my zsnes directory instead. This seems to happen randomnly.

It seems that zsnes temporarily changes where it looks for the save states when this happens. For example, if this problem occurs while I am playing, I won't notice it. The save states will be loaded from wherever they were last saved (i.e. the sznes folder or my saves folder). However, when I quit zsnes and play later, it tries to load the save states from the correct directory (my saves folder). In this case, the save state is an older version than the one in the zsnes directory.

I have tried playing with the "don't save current path" setting in the options menu, but this doesn't help.

Aerdan · Post by **Aerdan** » Sun Jan 30, 2005 10:11 pm

Do you save with the GUI or use the hot keys?

chronomitch · Post by **chronomitch** » Sun Jan 30, 2005 10:38 pm

I use hot keys. (f2 to save and f4 to load)

snkcube · Post by **snkcube** » Sun Jan 30, 2005 11:41 pm

Don't always rely on save states. If they get corrupted, you're pretty much screwed.

chronomitch · Post by **chronomitch** » Mon Jan 31, 2005 12:43 am

snkcube wrote:Don't always rely on save states. If they get corrupted, you're pretty much screwed.

ok? Thanks for the advice, I guess. That still doesn't fix the problem.

Noxious Ninja · Post by **Noxious Ninja** » Mon Jan 31, 2005 3:13 am

This is a known problem. It hasn't been fixed yet. It may be fixed in the future.

For now, you should be able to get rid of the problem by disabling SRAM Check+Save.

frankbrodie · Post by **frankbrodie** » Mon Jan 31, 2005 4:56 pm

Haha.

I wondered where that Super Mario All Stars save had gone.
(It wasn't THAT bad. I only lost 15 minutes worth of play)

Will disabling the 'SRAM Check+Save' option have any detrimental effect?
I just checked, and I did indeed have that checked. (by default yes?)

Useful info anyway if any other saves go MIA...

Noxious Ninja · Post by **Noxious Ninja** » Mon Jan 31, 2005 5:13 pm

frankbrodie wrote:Will disabling the 'SRAM Check+Save' option have any detrimental effect?

Basically, with it off, ZSNES only writes SRAM data (in-game saves) to the hard drive when you quit the game. With it on, ZSNES saves it to disk whenever you save it in-game. If ZSNES quits improperly with it off, you lose your in-game saves.

Deathlike2 · Post by **Deathlike2** » Mon Jan 31, 2005 10:18 pm

Related Link:
http://board.zsnes.com/phpBB2/viewtopic ... 83&start=0

It still occurs in the 1/31 WIP version...

To reproduce in the WIP (and 1.42 official) version:

1) Load ZSNES
2) Make sure SRM Check+Save is not enabled, the Snapshots directory can be undefined or defined to any other valid directory other than the ZSNES directory, and that there are no savestates in the ZSNES directory
3) Load a game (best to use a game that does use SRM aka "battery backup" like FF2)
4) Save a state
5) Quit ZSNES
6) Load ZSNES
7) Enable SRM Check+Save

Load same game used in Step 3
9) Load save state immediately (not necessary, but it will work at this point)
10) Wait approximately 10 secs
11) Attempt to load save state

You will get an error message at this point. Seems to only occur in the Windows+DOS port.

If you attempt to save a savestate at this point, you will find a savestate in the ZSNES directory.

Note: All load/save savestate operations are done via their hotkeys (F2/F4)

Post by **grinvader** » Mon Jan 31, 2005 11:21 pm

It *should* now be fixed. You'll have to test it once ipher produces a new WIP, since I can't reproduce it here.

Deathlike2 · Post by **Deathlike2** » Mon Jan 31, 2005 11:28 pm

It *should* now be fixed. You'll have to test it once ipher produces a new WIP, since I can't reproduce it here.

It still occurs in the 1/31 WIP version...

Noxious Ninja · Post by **Noxious Ninja** » Mon Jan 31, 2005 11:35 pm

Deathlike2 wrote:
It *should* now be fixed. You'll have to test it once ipher produces a new WIP, since I can't reproduce it here.

It still occurs in the 1/31 WIP version...

The 1/31 WIP does not count as "new". This fix just went in in the last hour or so.

Deathlike2 · Post by **Deathlike2** » Mon Jan 31, 2005 11:37 pm

The 1/31 WIP does not count as "new". This fix just went in in the last hour or so.

Ah, ok. I'll wait until then.

Deathlike2 · Post by **Deathlike2** » Fri Feb 04, 2005 7:12 am

The 2/02 WIP does not fix the problem I have described. In fact, it seems to have generated a new bug altogether (which I have described and cited in the main WIP bug thread). What happens instead is that you cannot even read the savestate as defined by the save directory (or snapshot directory for that matter), because the save directory CHANGES after closing ZSNES for a second time w/o saving to the .cfg file via the GUI.

Deathlike2 · Post by **Deathlike2** » Mon Feb 07, 2005 8:02 pm

The bug that I have referred to has still not been fixed in the 2/07 WIP...

I also have a different bug though.. I'll report both bugs in the main bug thread...