Save States from one version to another?

[SSBM/SK]

Could I have the IRC info?

[MayImilae]

Yea... apparently that is so old it is from before Dolphin tagged the savestates with the version. There is no way to find out other than randomly trying old revisions and getting lucky. Sorry.

If you really want to do that, you could of course try 3.0 and 3.5 and others. If the build is further back than what is on our download page, you can use https://dl.dolphin-emu.org/oldbuilds/ to get REALLY old builds.

EDIT:

SSBM/SK Wrote:Could I have the IRC info?

#dolphin-emu on freenode.net

[SSBM/SK]

Thanks for everything major <3 , and fireboot </3 (who insisted and went out to imply ToS was not worth the struggle)

[JosJuice]

Actually, it is possible to get the approximate Dolphin version even from savestates that are that old. If you look at the beginning of the hex view, there should be a value that looks like "BAADBABE", but with the last byte different. In the screenshot MaJoR posted, it's at 0x1F. I thought it would be compressed in some way, but apparently not... Once you have that value, subtract 0xBAADBABE from it, and you'll have the revision number as seen in State.cpp. I can do that last part if you want to, you just need to post the value that's in the savestate.

[SSBM/SK]

(08-17-2015, 05:41 PM)JosJuice Wrote: Actually, it is possible to get the approximate Dolphin version even from savestates that are that old. If you look at the beginning of the hex view, there should be a value that looks like "BAADBABE", but with the last byte different. In the screenshot MaJoR posted, it's at 0x1F. I thought it would be compressed in some way, but apparently not... Once you have that value, subtract 0xBAADBABE from it, and you'll have the revision number as seen in State.cpp. I can do that last part if you want to, you just need to post the value that's in the savestate.

Problem has been solved, someone suggested 3.5-367 as a joke and someone else did for legits, so I gave 367 a shot and it worked.

[JooLeeAnh]

(08-17-2015, 05:41 PM)JosJuice Wrote: Actually, it is possible to get the approximate Dolphin version even from savestates that are that old. If you look at the beginning of the hex view, there should be a value that looks like "BAADBABE", but with the last byte different. In the screenshot MaJoR posted, it's at 0x1F. I thought it would be compressed in some way, but apparently not... Once you have that value, subtract 0xBAADBABE from it, and you'll have the revision number as seen in State.cpp. I can do that last part if you want to, you just need to post the value that's in the savestate.

I was in the same situation than the post's author, and I want to thank you for giving us that information.
To clarify (because it wasn't super obvious to me at first), to get my version number, I did:
- Found my hexadecimal number like JosJuice said.
- Did the substraction: (BAADBA42) - BAADBABE.
I used an online hexadecimal calculator (calculator dot net / hex-calculator dot html)
- I personally got the value -124, so I downloaded that dolphin version, transferred the save states to ./User/StateSaves, launched the game and the load worked perfectly.


Thank you JosJuice ! Just signed up to say that

[JosJuice]

I'm suspecting that my instructions weren't entirely correct, because you should be getting a positive value. Maybe the compression algorithm decided to leave BAADBA unmodified but did modify the byte that comes afterwards (because like my previous post says, the data is supposed to be compressed). Anyway, Dolphin gained the ability to display this version data somewhere around the 4.0-5xxx range, so if you try to load the savestate in a version that's newer than that, Dolphin will automatically show an OSD message telling you what (approximate) version you can load the savestate in. But I guess this doesn't matter for you, since you've resolved your problem already.