Issue transferring gamesaves

[Krafter]

I have two Switches. S1 is my stock Switch and will not be used for any modding other than legally obtaining games that I've purchased to transfer to S2. S2 was banned a while back by my ignorance when TX came out with his mod so I'm using it to play with. My idea is to use S2 for fun things like cheats and game mods. I want to start with Skyrim. I have Skyrim running on S2 just fine. It loads and is able to save games when I start a new game but... when I transfer over my gamesave from S1 it will crash anytime that the game tries to save. I've transferred the save twice from different points in the game and it still doesn't work. What at I doing wrong?

Thanks

 

[Krafter]

Anyone have any ideas?

 

[Deleted member 413168]

Yes, this is a bug in save tools. When dumping a save, it doesn't dump enough information to correctly restore the save. Each game sets how much space is needed for it's save. They can increase the space over time if needed, Skyrim is such as example of this.

The issue here is that Skyrim increases the save size in fixed chunks. So it will blindly try and create a new save file, but there actually no more space left, so the game crashes.

See the issue posted here https://github.com/J-D-K/JKSV/issues/264

I don't believe the rewrite branch is quite ready yet? I may be wrong. If it isn't, I can send you an app that will print the size of the save from S2, then use the same app on S1 to resize the save size. I had to do this fix my Skyrim save

Post automatically merged: Feb 15, 2025

here it is. launch it on S2, it'll display the data_size and journal_size. Launch the same app on S1 and press X to enter the data_size and journal_size for skyrim.

 

[duckbill007]

When dumping a save, it doesn't dump enough information to correctly restore the save. Each game sets how much space is needed for it's save. They can increase the space over time if needed, Skyrim is such as example of this.

Dbi do dump this and do restore saves as it should without any additional user actions.

 

[Deleted member 413168]

Dbi do dump this and do restore saves as it should without any additional user actions.

Oh nice, where does it save the data size? Did you see the issue linked? Maybe jksv can use the same file format you use

 

[duckbill007]

where does it save the data size?

In the backup archive as additional files

 

[Krafter]

Yes, this is a bug in save tools. When dumping a save, it doesn't dump enough information to correctly restore the save. Each game sets how much space is needed for it's save. They can increase the space over time if needed, Skyrim is such as example of this.

The issue here is that Skyrim increases the save size in fixed chunks. So it will blindly try and create a new save file, but there actually no more space left, so the game crashes.

See the issue posted here https://github.com/J-D-K/JKSV/issues/264

I don't believe the rewrite branch is quite ready yet? I may be wrong. If it isn't, I can send you an app that will print the size of the save from S2, then use the same app on S1 to resize the save size. I had to do this fix my Skyrim save

Post automatically merged: Feb 15, 2025

here it is. launch it on S2, it'll display the data_size and journal_size. Launch the same app on S1 and press X to enter the data_size and journal_size for skyrim.

I greatly appreciate this. I have not tried this solution yet or using Dbi as TotalJustice suggested. I did explore them both a little but I got sidetracked with life lol.

I'll try them both later. I'm the kind of guy that likes to have an explanation for the problem with a solution and not just the solution. The problem makes since. Thanks for explaining that.

Post automatically merged: Feb 15, 2025

Dbi do dump this and do restore saves as it should without any additional user actions.

Thank you. I will Try Dbi a little later. I didn't realize it had a save file manager.

 

[Krafter]

here it is. launch it on S2, it'll display the data_size and journal_size. Launch the same app on S1 and press X to enter the data_size and journal_size for skyrim.

Okay. I've had time to try out both methods. I can get both to work. Meaning that I can restore a save and I'm able to write over the save on S2. The problem that I'm facing now is, no matter what method I use, it's an early save file that's being restored. I've leveled up to almost 27 but each time I restore, it restores a level 25.

I've tried multiple times from scratch. I'm deleting saves from SDs each time and then backing up the save from my "Krafter" account on S1 and restoring that account on a "Krafter" account on S2 and I've even tried a new profile. Both methods are just grabbing an older save. I doesn't make sense......

 

[Deleted member 413168]

Okay. I've had time to try out both methods. I can get both to work. Meaning that I can restore a save and I'm able to write over the save on S2. The problem that I'm facing now is, no matter what method I use, it's an early save file that's being restored. I've leveled up to almost 27 but each time I restore, it restores a level 25.

I've tried multiple times from scratch. I'm deleting saves from SDs each time and then backing up the save from my "Krafter" account on S1 and restoring that account on a "Krafter" account on S2 and I've even tried a new profile. Both methods are just grabbing an older save. I doesn't make sense......

Is it in cache?

 

[Krafter]

Is it in cache?

Now that's a good question. Where are the cache files located?

 

[Deleted member 413168]

Now that's a good question. Where are the cache files located?

Iirc jksv should have a cache tab on the left side

 

[Krafter]

Iirc jksv should have a cache tab on the left side

Well, I figured out why I'm only able to get level 25 save. I'm a dumb @$$. I was making a backup for the emuNAND which was created when I was at level 25....

Now I can at least get a current save by launching into sysNAND CFW. No my issue is resizing using your app. I launch it on S1 and it says the data size is 4193040 and the journal size is 25165824. I then launch it on S2 and enter those sizes but it errors saying that it was unable to change the size. Any thoughts on that? I've used DBi to restore and now its crashing too on save.

 

[Deleted member 413168]

Well, I figured out why I'm only able to get level 25 save. I'm a dumb @$$. I was making a backup for the emuNAND which was created when I was at level 25....

Now I can at least get a current save by launching into sysNAND CFW. No my issue is resizing using your app. I launch it on S1 and it says the data size is 4193040 and the journal size is 25165824. I then launch it on S2 and enter those sizes but it errors saying that it was unable to change the size. Any thoughts on that? I've used DBi to restore and now its crashing too on save.

Do you have the game open when trying to re size the save (including title override)? If not, try deleting the save, restore and resize again.

 

[Krafter]

Do you have the game open when trying to re size the save (including title override)? If not, try deleting the save, restore and resize again.

Maybe I did. Maybe I didn't. I don't think so but it doesn't matter now. I finally got it to work. I deleted all save files from my backups on my PC and from both SD cards. I went though the process again but this time it allowed me the changed the file size. I'm now running my most recent save and I am able to save on top of it. Thank you so much for your help and for the app.

 

[duckbill007]

Any thoughts on that?

Journal can not be bigger than data.

I've used DBi to restore

What version? Latest is 761. Save size restoring was introduced in 676.

 

[Krafter]

What version? Latest is 761. Save size restoring was introduced in 676.

6.58. It's the last version in English that I know of.

 

[duckbill007]

It is a very old and buggy version without full suport of FW 19+