- Messages
- 147
Since updating, super slow saves. I mean quick saves, real saves, etc. 20+ mins!!
the Sim Settlements forums!
Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!
Super slow saves 2.0.0
- Thread starter Amardon1961
- Start date
- Messages
- 5,184
Appreciate all the reports on this.
Unfortunately, I can't replicate this, and we don't actually have control over save files. It's not as if we can change the data that gets saved at any particular point - so I don't really have any meaningful action I can take.
It's especially confusing when I'm seeing some reports saying it happens without Chapter 2, and others saying it only happens with Chapter 2. If we can get this confirmed one way or the other, it would at least narrow down where the issue might be.
Has anyone managed to replicate this problem without SS2 at all? For example, just using the latest WSFW.
Unfortunately, I can't replicate this, and we don't actually have control over save files. It's not as if we can change the data that gets saved at any particular point - so I don't really have any meaningful action I can take.
It's especially confusing when I'm seeing some reports saying it happens without Chapter 2, and others saying it only happens with Chapter 2. If we can get this confirmed one way or the other, it would at least narrow down where the issue might be.
Has anyone managed to replicate this problem without SS2 at all? For example, just using the latest WSFW.
Cuatela
New Member
- Messages
- 12
I uninstalled SS2 and Chapter 2 to test that (just now). Made a new game, went directly to Starlight, cleared it and built a settlement with 14 beds, water purifier, all 6 of the level 3 stores, and enough plants to get around 20+ food. Spawned and assigned 12 settlers (about how many I normally have in a settlement). No issues saving at all in that state, but I also don't see the normal status pop-ups that I would with SS2.
Although in my case, I never had issues anyway until I started having full SS2-built settlements, and only after 2.0, so I'm thinking it's something with the building scripts? That's the only thing in my game that changed when I started having saving issues.
Although in my case, I never had issues anyway until I started having full SS2-built settlements, and only after 2.0, so I'm thinking it's something with the building scripts? That's the only thing in my game that changed when I started having saving issues.
phpones
Member
- Messages
- 33
In my case it only happened with SS2 2.0 + Chapter 2. It happened during If I Had a Hammer quest on a new fresh game, about 5hrs in. Then I started a new game with exactly the same load order except that I went back to SS2 1.1 (kept WSFW 2.0.17). Not a single hickup so far, also about 5hrs in and with much more things at Sanctuary than I did on the first game.
On this bug report here: https://simsettlements.com/site/ind...e-and-fast-travel-significantly-longer.20177/
Posts #4 and #5 confirm they did not have Chapter 2 installed, only SS2 2.0 + WSFW.
By elimination, makes me think it's isolated to SS2. Putting together with that other post about hanging scripts, couldn't it be that SS2 2.0 is flooding the VM causing it to hang when we save? After all, the VM freezes before we save...
- Messages
- 5,184
Uncertain. Of the new systems that were added with 2.0.0, the only one with significant code is HQ, which most folks haven't gotten close to when these issues start cropping up. It also appears to be inconsistent, as this issue hadn't come up for any of our testers during 6 months of alpha/beta. So this is going to be a tough nut to crack.
phpones
Member
- Messages
- 33
Could also be some incompatibility... Might be worth to start asking people for their load order so we compare and see if there's something fishy there.
TornadoADV
Member
- Messages
- 40
Throwing my hat in the ring with catastrophic save times and hanging after updating to 2.0 and adding the Chapter 2 XPAC. At least with 2.0.0a, with what saves DO get through, they no longer cause CTDs and missions trigger properly.
Cuatela
New Member
- Messages
- 12
As an update to my previous post (#20 in this thread), I reinstalled both SS2 and Ch2 and kept playing from the earlier save. Aside from one random CTD in HQ while doing the first of the setup tutorial (didn't happen again or with any other builds I did), I played for a solid 6 hours without any issues. At least until I needed to go to a settlement to get supplies. Oddly enough, I could fast travel and save near the settlement, even built a caravan plot and let it build before saving and fast traveling again. The next crash happened after I built some turrets around the settlement. Trying to save caused another freeze/crash, but again that's after several hours. Also reiterating that I had no technical issues at all with the HQ's new systems, aside from one CTD (which I think was caused by my character sitting on a sofa that was being scrapped).
All of my freezing issues have happened in an SS2 settlement either while the settlers were building plots, or while one of the scripts were running, or immediately after a new object has been built. Aside from low FPS / stuttering during the larger events, I haven't had any serious issues other than working with settlements post-2.0.
kinggath, out of curiosity, how is the range on your testers specs? Do they all have good systems, moderate, low-end, or some mix of all of those? I'm curious if it's simply a matter of all the scripts overloading low-end systems, even with things like F4SE and baka's scrapyard.
All of my freezing issues have happened in an SS2 settlement either while the settlers were building plots, or while one of the scripts were running, or immediately after a new object has been built. Aside from low FPS / stuttering during the larger events, I haven't had any serious issues other than working with settlements post-2.0.
kinggath, out of curiosity, how is the range on your testers specs? Do they all have good systems, moderate, low-end, or some mix of all of those? I'm curious if it's simply a matter of all the scripts overloading low-end systems, even with things like F4SE and baka's scrapyard.
- Messages
- 262
- Messages
- 5,184
Our testers' systems definitely run the gambit of potato to superbeast!
If we can get confirmation from any of you digging in with this testing that the issue happens WITHOUT Chapter 2 having ever been installed - but just the 2.0.0 update to SS2 and 2.0.17 update to WSFW, that would narrow down the issue quite a bit.
The fact that the issue seems to happen more frequently when near a settlement definitely helps with some ideas - and also may act as a potential workaround for folks having the issue (ie. they can save far from settlements, such as in an interior or an alternate worldspace like Diamond City).
If we can get confirmation from any of you digging in with this testing that the issue happens WITHOUT Chapter 2 having ever been installed - but just the 2.0.0 update to SS2 and 2.0.17 update to WSFW, that would narrow down the issue quite a bit.
The fact that the issue seems to happen more frequently when near a settlement definitely helps with some ideas - and also may act as a potential workaround for folks having the issue (ie. they can save far from settlements, such as in an interior or an alternate worldspace like Diamond City).
- Messages
- 74
my experience with ss2 saves. played from the initial release of ss2 + depravity , valkyrie(not started) and bleachers. saves were ok when i built up a settlement in sanctuary and abernathy 43/ 20 respectively my saves got slower and slower and strangely workshop fly mode became unreliable(upto 6 attempts to activate) now wherever i save, i cant save and quit to desktop just freezes (skyrim did this as well) if i save and continue its very slow but its ok. this happens all over the commonwealth. ,but i may have deleted some precombines in sanctuary with scrap everything. my save is at least 59 mb.
Hey there, I can confirm that the slow save/CTD issue started almost immediately after upgrading SIM Settlements 2 but WITHOUT having part 2 installed (I CT'D twice in an hour, both when attempting to save; all saves ranged from 3 second to 1 minute, average of maybe 10 seconds). I was on maybe a 3 hour playthrough and the issue became noticeable right around "If I Had a Hammer". Saves were still slow as far away as Conchord, but I didn't test farther out from Sanctuary than that. Also, I had no city plans, or large-scale settlements, no triangle of death: just a couple of residential ASAMs in Sanctuary.
It MAY not be a Workshop Framework update related issue, as I did that update a couple days before updating SS2, and didn't have the issue until updating SS2. If it helps, I'm on a Xbox Series X, and if others want to compare my load order is:
Workshop framework
SIMS Settlements 2
True storms
NPCs Travel (no DLC)
Search and Destroy
SKK Stalkers
Random Encounter Manager
Faded Glory
Realistic Sound XB1
Ambient Wasteland
Darker Nights 0 for True storms
ISO
Interior visual overhaul
HQ Gothic towns
Simply Green Grass
HUD framework
Immersive HUD
Smokeable Cigs
Cigarettes Retexture
Detective Special pistol
Knight Sword
Pre-war Binoculars
Colonial duster
The Wild Wasteland
Atomic world
Atomic World visual fix
Crowded Commonwealth
Expanding Boston
Rsiyo’s locations pack
Commonwealth wilderness overhaul
Prime Location
Notes of the commonwealth
Pip-boy Flashlight- Small
BlurkillerComplete
I had played multiple playthroughs with SS2 and this exact load order, pre-update and nary an issue or CTD. I thought the issue maybe was Atomic World's new locations conflicting with SS2 somehow, but looked it up and sure enough finding a lot of comments on how it seems to be definitely SS2 or WSFW
edit: a reddit page from 3 days ago confirming the same issue (a couple commenters said they only had SS2 part 1, not part 2)
Last edited:
tempestbob
Active Member
- Messages
- 174
I've noticed that using the console's 'savegame' command works just fine despite all other saves freezing for between 20secs and 3 minutes. So I just turned autosaves off for now and am trying to remember to do manual saves like that more often. Only lost an hour this morning. haha
I've always noticed longer save times if a specific script is in the middle of running, but this occurs in vanilla as well, and I could never nail down which script/s did it. Perhaps there is something exacerbating the vanilla issue in Chapter 2? I've never seen anything on the order of minutes to save though. At most 40 seconds if something is trying to finish running before the save occurs. On a moderate potato computer with midrange gfx and hundreds of mods. The save system in bethesda games has always been a bit bonkers and bug riddled. Especially autosaves.
MisterKen
Active Member
- Messages
- 455
Unless its an incompatibility with SS2 plot add-ons, I'm wholly just SS2.
- Messages
- 293
For me it's anytime I'm near or interacting with SS2 content. Usually at or near settlements. I started a new game for the chapter 2 release. On my previous save already using SS2, the issues were 10 times worse after updating ch1 and loading chapter 2. During the new game, it is not nearly as bad.
Had one happen last night in Concord. I'd just finished Well, Well, Well and went to check out the new Preacher character. Talked to him, read the bulletin board. Went and got the quest from the Caravan guy. Then went to Sanctuary to throw down a beacon and another residential to kill time until Preacher's sermon at 9pm. Walked back to Concord after everything seemed to finish running in Sanctuary. Went into the church, about 8:55pm in game, Preacher and the caravan guys are all sitting in there, nobody saying anything. Wait like 30min-1hour in game. Open Pip-boy, triggers autosave. Autosave locks up and takes 5-10minutes. When the autosave finished and unfroze the game, the caravan hand started talking to the preacher about donating. No one else said anything after that and i eventually left, hard saved(which works fine), and called it a night.
phpones
Member
- Messages
- 33
Alright, let's summarize what we know for sure at this time:
This all points to be SS2 update. @kinggath & Team: I don't know how the VM or Papyrus scripts work behind the scenes but I have good experience with debugging. Since you have direct access to your users reporting the problems, what I'd suggest is that you create a test version with debug calls in everything that you changed from 1.1 to 2.0. We have a bunch of users here with busted saves so having them test with debug On and comparing the logs might reveal the offending script(s).
- It's not Chapter 2: several reports of not having it installed.
- It's not WSFW (at least not by itself): Some reports of having it up to date but not SS2 (I'm one of them and monitoring closely)
- It's not mod conflicts: 1 report of running only SS2 related stuff.
- 3 reports of having it happen during If I Had A Hammer, but some happening out of that quest.
- Autosaves are mentioned a lot. We have to remember that autosaves trigger immediately after X happens. The "immediately" here might be relevant. But a lot of reports saying it happens on manual saves too (I was one of them)... but maybe starts happening AFTER autosave already messed things up? It would be nice to have a report from someone not using autosaves at all.
This all points to be SS2 update. @kinggath & Team: I don't know how the VM or Papyrus scripts work behind the scenes but I have good experience with debugging. Since you have direct access to your users reporting the problems, what I'd suggest is that you create a test version with debug calls in everything that you changed from 1.1 to 2.0. We have a bunch of users here with busted saves so having them test with debug On and comparing the logs might reveal the offending script(s).
Last edited:
I can confirm, it's anywhere near SS2 content. In my settlements, Concord, The Ron's office, vault 57 (is that, where rescuing Jake takes place?). Even at the entrance to it. Saves take up several minutes, but not continuously so. Sometimes they finish quickly. Maybe an unfinished script in the background?
Gingernick
New Member
- Messages
- 16
in a settlement its slow ( not as long as some people are getting...20/25 seconds maybe, but I have a good rig and all games or on m2 cards and my saves go to a ssd)
outside of a settlement its pretty much a couple of seconds only
thats on SS2 and chapter 2
as eldiablo said though, you used to get variable save times before SS2 was updated and chapter 2 came along, especially on exiting the game
I am running about 230 mods..mostly wepaons and graphical, not much at all altering world spaces , I also removed anything that extended settlement foot prints just in case
so all in all..I havent been much help!!
outside of a settlement its pretty much a couple of seconds only
thats on SS2 and chapter 2
as eldiablo said though, you used to get variable save times before SS2 was updated and chapter 2 came along, especially on exiting the game
I am running about 230 mods..mostly wepaons and graphical, not much at all altering world spaces , I also removed anything that extended settlement foot prints just in case
so all in all..I havent been much help!!
smitty420
Well-Known Member
- Messages
- 535
I can’t believe I get to correct the brilliant kinggath!
It’s “run the gamut.” A gambit is either a ruse of some kind or the most underrated X-man.