Why is the size of the saves "A Problem", as far as I can tell everybodies saves are around
6 to 7 MB in Fort Joy
10 to 12 MB in Reapers Coast
I fail to see why you'd ever consider save size increase as you progress, and inventory increases as any sort of problem.
The savesizes increase not because of inventory, but, as I stated before, it keeps a copy of every map in your savegame.
I'm at Arx now and I can clearly as day see it has full Reaper Coast, Nameless Isle and Fort Joy in my savegame, which is SAVES and LOADS each and every time. Can you start seeing where the extreme rise in loading and saving times when the game continues comes from?
I don't understand why this is done. You cannot return. All "choices" should be in a seperate few kb file with booleans and strings, not a whole copy of the map needs to be included. They DEFINITELY need to purge non-returnable areas from saves.
It's 15-16MB on Nameless Isle, 20MB on Axe by now. Per savegame. Some compression is done, but here's how a savegame is made up for me, courtesy of the "Levelcache" folder;
Arx; 11,7MB
cos_aoto_itemtransfertemplate; Dunno what that is, 120kb though.
Nameless Isle: 3,8MB
Nameless Isle finale; 200kb
Fort Joy; 6,3MB
4 Decks of Vengeance (these are the only ones who definitely need no purging); 500kb
Reaper Cost; 13.4MB
Tutorial: 500kb
Stuff that needs to be purged to seriously speed up saving and loading times; Nameless Isle, Fort Joy, Reaper Cost, Tutorial. 24,2MB of stuff gone, 12,3MB of stuff left. Improving saving performance by about 200%
Larian are aware of Long Loading time issues, but for most of us that's mod related.
As you can see, it's not mod-related. They just bloat savegames. No good reason really seeing you can't return there, so no need to store it.
As far as I can tell, this threads ignored, because it's mainly about the savefile sixe.
Except that's the whole cause it's taking so long to save and load. Reduce the size, by purging non-entities at that point in the game, and saving and loading goes faster, taking less memory while doing so. It's like saying "this car fix topic is being ignored, since you just talk about having no tires."
That's not a problem, or a bug, it's normal for this game, we all have the same sizes of saves.
And now you know why. And why that's an issue. And why it is so memory-intensive on save and load. And why this process slows down considerably over the course of the game (hint; it's not your inventory size).
If you do have other issues, post about those issues outside this thread, ignore the savefile size.
"If you have issues with memory usage, complain about something ELSE than the cause please."
Me: No.
If you find a thread that's about your actual problem, post there, or start a new topic.
I found it, and I'm posting in it. And so far it seems there's only one person here who doesn't understand the problem. That person being you.
Make it about what your problem actually is, and you may get somewhere.
The problem is savegames are bloated with inexeccesable content that still gets saved and loaded regardless, making memory-usage far higher than needed if it stuck to the essentials; current game area, choices, and character data (inventory, stats etc.).
