v. 1.42n

Dartagnan · Post by **Dartagnan** » Mon May 29, 2006 10:44 pm

If I download 1.42n, will I still be able to keep all my saves?

Joe Camacho · Post by **Joe Camacho** » Mon May 29, 2006 10:46 pm

It depends the version of the emulator you are using, if you are using a really old version, chances are savestates won't work.

.srm files are compatible with all versions, they are even compatible with other emulators.

Firon · Post by **Firon** » Mon May 29, 2006 10:49 pm

Savestates often aren't portable across versions. Half my savestates from one of the SVN revisions after 5/14 don't work in the latest revision (they crash ZSNES without error dialogs when I load them).

I learned that lesson long ago, hence why I ALWAYS use native saves whenever possible.

adventure_of_link · Post by **adventure_of_link** » Mon May 29, 2006 10:51 pm

iirc it was the savestate code that changed sometime last year, so that's where those problems come from.

Firon · Post by **Firon** » Mon May 29, 2006 11:37 pm

It seems like it was changed again recently, because savestates I made a week ago or so just crash the latest SVN revision.
Can't really see anything in the log that would indicate changing of savestates, though... Unless the last 3 changes in zstate.c caused it unintentionally.

xamenus · Post by **xamenus** » Tue May 30, 2006 2:20 am

Firon wrote:It seems like it was changed again recently, because savestates I made a week ago or so just crash the latest SVN revision.
Can't really see anything in the log that would indicate changing of savestates, though... Unless the last 3 changes in zstate.c caused it unintentionally.

Welcome to the dangers of using unstable ZSNES versions.

creaothceann · Post by **creaothceann** » Tue May 30, 2006 6:55 am

You don't even have to change the savestate format much to break things... the timing of the emulator is also important.

Firon · Post by **Firon** » Tue May 30, 2006 7:57 am

Ah, I didn't know that. There's been a lot of timing/core changes lately, so I guess it'd be no surprise then.

Post by **grinvader** » Thu Jun 01, 2006 12:46 am

Using PSR-based save states could prevent immediate crashes (usually caused by an offset mismatch) but wouldn't be very useful against timing differences - even if the old timing-critical vars were stored in.

Cope with it, use SRAMs.
Also remember that any game without SRAM/passwords can be cleared under 3 hours - hell, even most of SRAM-using games can be cleared under 3 hours... with some skills.

adventure_of_link · Post by **adventure_of_link** » Thu Jun 01, 2006 1:42 am

grinvader wrote:hell, even most of SRAM-using games can be cleared under 3 hours... with some skills.

in the case of Zelda III, moar like 3 minutes

Firon · Post by **Firon** » Thu Jun 01, 2006 4:32 am

I use native saves whenever possible because of it, though it would be nice if ZSNES would not crash and instead just say "NO WAI" when loading the savestates.

Post by **grinvader** » Thu Jun 01, 2006 4:42 am

There's no way to know if the state will load right or not. Why prevent it altogether, when you have a tiny chance of success ?

Deathlike2 · Post by **Deathlike2** » Thu Jun 01, 2006 4:44 am

Firon, if you saw that code that used before PSR, it would make maintaining ZSNES seem like shooting yourself in foot. Right now it is better to make things more flexible in the future by removing the old and adding in the new... at least with the future code that it won't crash horribly like this.

Firon · Post by **Firon** » Thu Jun 01, 2006 8:27 am

I assumed it was possible to know if it would crash or not and prevent the load/crash, but I guess I assumed wrong! Nevermind me!

And Deathlike2, there isn't any PSR for savestates right now, it's just something grinvader mentioned to help reduce the crashes when loading savestates from older builds.
As far as changing the code to make it more flexible, it's something I've seen for quite a long time in the changelogs now, and I'd say it's a good thing. It apparently used to be a living hell just to add another item to the options, from what I remember.

All these changes (especially the ones to make it more accurate) are for the better, even if they break stuff.

Deathlike2 · Post by **Deathlike2** » Thu Jun 01, 2006 11:32 am

Firon wrote:And Deathlike2, there isn't any PSR for savestates right now, it's just something grinvader mentioned to help reduce the crashes when loading savestates from older builds.
As far as changing the code to make it more flexible, it's something I've seen for quite a long time in the changelogs now, and I'd say it's a good thing. It apparently used to be a living hell just to add another item to the options, from what I remember.
All these changes (especially the ones to make it more accurate) are for the better, even if they break stuff.

PSR will be used for savestates.. it's a matter of converting the current format to PSR..