Apologies if this has already been discussed in another thread; haven't been able to find it. I am being prompted to download & install an update, but there's a warning about losing my save states (attached). I've been through this already for a previous update, and it was annoying to have lost my place in a few games because I just have no idea how to "save your progress to your memory cards".
Can anyone point me to instructions on how to do this & be able to update the app without losing my saves or how to replace them afterwards? This doesn't mean I have to manually re-add save files for each game, does it? That would really be a huge pain in the ass...especially if this is something that is going to keep happening.
(10-02-2023, 07:25 AM)jesalvein Wrote: how do you save the game when playing on your real console ?
I see where you're going with this, but yeah, "saving to a memory card" doesn't quite answer the questions I have. I'm looking for is a way the developer might be expecting users to accomplish this - copying files over in a batch & then back again... or if I need to launch every single game & change the save path for each. Then I am wondering what the best practice would be moving forward, as this has happened twice already & if I do have to handle each game's save file individually, I would like to keep the saves on some external media or just separate so I don't have to worry about it. If there's a way to know if this will be the last time, and saving those files would indeed require messing with each path/file, I may decide to just blow them away.
to make it short and simple : saving on a memcard is the way you should save your games.
Relying on savestates only is a bad idea as they can be unstable, or even sometimes break your game saves (some games react very badly to savestates).
Moreover, savestates aren't cross-version compatible whereas memcards are and always will be.
best practice is to save on memcard always, and on savestates sporadically
CPU : AMD Ryzen 7 3800X
Mobo : Asus PRIME B450-PLUS
GPU : NVIDIA GeForce RTX 3070
RAM : 16 Go
(10-04-2023, 06:34 PM)jesalvein Wrote: to make it short and simple : saving on a memcard is the way you should save your games.
Relying on savestates only is a bad idea as they can be unstable, or even sometimes break your game saves (some games react very badly to savestates).
Moreover, savestates aren't cross-version compatible whereas memcards are and always will be.
best practice is to save on memcard always, and on savestates sporadically
99% of the time when I'm using this machine to play PS2 games, I'm not traveling with a memory card reader. Saving stuff in a different location on my HD should have the same benefit I assume; but it sounds like the primary question, having to tend to each game separately, is the issue... if I only have to do it once, changing the paths, I guess I could get around to that .. but otherwise I'm more likely to just limit my PS2 gaming to my portable device using Aether where I haven't run into this. Thanks.
of course, because Aether isn't updated since 1 year, so no risk.
You don't need a "memcard reader".
Aethersx2 saves to memcards just as pcsx2 does.
But those are (of course) virtual.
Real ps2 memcard usb readers are quite rare and very few people have it. When it's advised to save to "memory card", it means "make an ingame save, juste the same way you would do it on your PS2".
This ingame save will be on a virtual memcard
CPU : AMD Ryzen 7 3800X
Mobo : Asus PRIME B450-PLUS
GPU : NVIDIA GeForce RTX 3070
RAM : 16 Go
I got that part; so "memcards" - Mcd002.ps2 & 001 hold all of them, and if I just copy those files over to a new directory, then back again after the update, in theory all should be well?
