Hello
Raze, thank you very much for your reply!
UBBCode is disabled on new accounts as an anti-spam measure (no clickable links, etc); editing the post now will let you use it.
Oh okay, I understand, thanks for letting me know. Well, since I had already deleted all the UBBCode, I'll just keep it as is.
Both the location and playtime should change if you make new saves, rather than overwriting an existing one. That should also be a little more reliable, as it is one less step in the save process, and safer since crashes during the save process would be less likely to affect previous saves.
So far, none of the crashes that occurred while saving have corrupted or completely wiped the save file, but it's better to be safe than sorry.
Reaper's Coast is 3 or 4 times the size of Fort Joy. Arx is also quite large, with lots of NPCs and various behaviour scripts running in the background, etc. There were some fixes and memory optomizations in the first update, that should have helped with stability issues in Arx.
I understand that Reaper's Coast and especially Arx is pushing the Nintendo Switch to the limits even with the memory optimizations, and I totally understand and accept that, but the crashing while loading/saving (especially saving) problem is unacceptable.
Can you check if new named save have the same chance of crashing?
Sure thing, I will try to save my data in a new save slot and check to see if the crashing instances have changed or whatnot.
Does the chance of crashing change with either fairly short playtimes, or fairly long?
This late game Arx crashing while saving occurrence is currently around a variable rate that ranges from as low as 20min~30min of gameplay and higher. I try to save after each battle now given the high chance of crashing, but it seems that even after smaller battles or even no battles (there was one time I was just doing some inventory management, then tried saving afterwards, then it crashed), it could still crash. I'm starting to believe that having 730+ items in the inventory might having something to do with it, but that's just a guess.
Are saves during combat (with lots of surfaces, etc, around) more likely to crash?
I have never saved during combat, save (no pun intended) for the times when the game auto-saves itself right at the start of certain battles that you walk into. At this point, these auto-saves are making me nervous due to the current crashing probability. When I save now, I try to go into a small secluded room with very few items (no NPCs inside)....but even STILL, the game could crash while saving even in such isolated places; it already happened to me 3 times, so suffice to say, there's no hiding from it.
Since you didn't mention Steam, I'm assuming you don't have that version, as well, with your account linked?
The only other way to get saves off the Switch, for the programmers to check out, would be if you have Nintendo's extra Online service, and would be willing to PM me or email supportdos2@larian.com with your account email/password to retrieve them from cloud storage (you could change the password temporarily, and switch it back once the saves have been transferred).
Otherwise I will create a bug report for this, and hopefully the description will be enough to help track down the issue or reproduce the problem.
That's right, I only own and play the Nintendo Switch version of Divinity: Original Sin 2; I have no such linked accounts. As for transferring my game save cloud data for this game to Larian Studios via the Nintendo Switch Online service, I'll send you a PM.
Thank you very much again for your reply, Raze.
