Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
How to transfer PCSX2 save states version 0.9.8 to PCSX2 1.0.0?
#1
This might be a noob question, but how do I do this? Every time I try to load a save state, it says that it can't load since it's a different version. Thanks in advance!
Reply

Sponsored links

#2
You can't,save states are version\revision(from - to )dependent.
You need to save your progress into the memory card if you want to switch to pcsx2 1.0.0
Reply
#3
(02-17-2013, 07:03 PM)Ophidian Wrote: This might be a noob question, but how do I do this? Every time I try to load a save state, it says that it can't load since it's a different version. Thanks in advance!

What vsub said. Don't be used to rely on sstates as main way to keep save games. Sstates are very useful to keep intermediary saves in between save points and can be used even middle of battle. That's because the sstate is a snapshot of the actual memory PCSX2 (and the game is using), on the other hand that's the reason the sstate becomes useless if the emulator changes.

The answer to your question is: find the old emulator version you did the sstate, go to the nearest save point and do a normal save. Then you can load this new save from the memcard at the new emulator's version.

The main lesson from this is: use sstates at will but don't skip normal saves. Be aware the memcard save is the only secure way to do keep long term savegames.

----------------------------------------------------------------------------
PS: the following is just a simple information about the differences between the memcard and the sstate.

The normal save (on the memcard) is not controlled by the emulator (as PS2 itself has not control over this) but by the game itself. So there is no way to foresee what a game will store in it's save, more yet, that save stores only enough information that allows to recover the game at that last save point and the actual information about the characters statuses and inventory (and any other information the specific game may need). One important consequence of this is the game is reconstructed from the disc image and so eventual memory corruption of any nature is gone. For that reason is good idea to reload a game from the normal save ar least once and again.

The sstate on the other hand, for not knowing what to save does save the entire memory (it is using) and then it "saves" whatever corruption of whatever nature and most commonly created by wrong cheat codes (notice that once the sstate is created, removing the cheat code does not delete the corruption on sstate).

Finally, if the memory structure changes in anyway with the emulator's change, that makes previous sstates useless and can't be used anymore.
Imagination is where we are truly real
Reply
#4
(02-18-2013, 12:09 AM)nosisab Ken Keleh Wrote: What vsub said. Don't be used to rely on sstates as main way to keep save games. Sstates are very useful to keep intermediary saves in between save points and can be used even middle of battle. That's because the sstate is a snapshot of the actual memory PCSX2 (and the game is using), on the other hand that's the reason the sstate becomes useless if the emulator changes.

The answer to your question is: find the old emulator version you did the sstate, go to the nearest save point and do a normal save. Then you can load this new save from the memcard at the new emulator's version.

The main lesson from this is: use sstates at will but don't skip normal saves. Be aware the memcard save is the only secure way to do keep long term savegames.

----------------------------------------------------------------------------
PS: the following is just a simple information about the differences between the memcard and the sstate.

The normal save (on the memcard) is not controlled by the emulator (as PS2 itself has not control over this) but by the game itself. So there is no way to foresee what a game will store in it's save, more yet, that save stores only enough information that allows to recover the game at that last save point and the actual information about the characters statuses and inventory (and any other information the specific game may need). One important consequence of this is the game is reconstructed from the disc image and so eventual memory corruption of any nature is gone. For that reason is good idea to reload a game from the normal save ar least once and again.

The sstate on the other hand, for not knowing what to save does save the entire memory (it is using) and then it "saves" whatever corruption of whatever nature and most commonly created by wrong cheat codes (notice that once the sstate is created, removing the cheat code does not delete the corruption on sstate).

Finally, if the memory structure changes in anyway with the emulator's change, that makes previous sstates useless and can't be used anymore.

Thanks, helped alot!
Reply




Users browsing this thread: 1 Guest(s)