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!

Not a bug CTD on loading mod in new save

Henry Worden

New Member
Messages
0
Hey, I just recently reinstalled Fallout 4 to try the mod out. After changing the new game settings for Sim settlements Conqueror, and the mod starts loading city plans and spawning settlers the game CTDs. I have yet to get past the four loading bars of the mod. I run the newest version of F4SE, I have an enb, and I have all my other mods temporarily disabled in order to get it to load properly. If anyone else has had this problem/has a solution I would love some help, as this mod sounds really awesome. Thanks in advance.
 
are you still having this issue?
try reducing the amount of pre built cities
Have them only start at level 1
 
Yes, I still have this issue. I will try that. Before I had them start at random levels from foundation to 3. Ill post back if the problem persist.
 
Alright, I have tried multiple times over the last couple of days to get it to work. I kept random starting level on, but only from foundation to level 1. Now I am able to consistently get to the 4th stage of loading before it hard crashes. I have pretty good system specs, and have extensively modded the game before. What might I try to get it to work?
 
maybe load order issue or mod conflict of some kind.
do you use alternate start or start me up mods?
When you get the option to choose your game settings choose medium or low.
put Workshop Framework above simsettlements
 
As I said in my first post, I have all other mods disabled at the moment. I'll try putting the framework above simsettlements.
 
I'm having similar issues, it appears to be a real shot at the dark wether you're going to have a stable playthrough or not.

I had a save of 2 days with Conqueror, I conquered half the map up until joining up the institute and taking over Warwick Homestead, then issues starting to arise, CTDs every now and then, random really, I couldn't reproduce any of them, it wasn't a specific area CTD. so I gave up on the save just today.

I said well, it is my load order, or it is my save that is screwed up, so I went to the nexus and downloaded a vanilla save that had all settlements unlocked, loaded up that save and Conqueror's message to start the process appeared, I chose no to play without Conqueror but keeping the rest of my load order enabled, I played for about an hour free roaming the commonwealth in that save shooting stuff, trying to get the game to crash, spamming minigun and missiles/fat man mini nukes, spawning a bunch of raiders via console, and yes I did try going to the demanding places like the heart of the city as well, I played for about more than half an hour, no crash, I know its not too much, but with the other save I couldn't play more than 20 minutes before it Crashed to desktop.

So ofcourse, it was my save, again.. I said no biggie, I did remove mods mid playthrough so that might have been on me, well..

Started a new game with Conqueror on again, same mods even less than the other playthrough because I disabled some, the build up process went up normal, took about an hour as usual, I was waiting it out in the sanctuary basement jahani cell, as usual, I use StartMeUp and I used the same method for previous save, escaped synth and load me into the basement, all went fine until the process finished and I exit the basement, I get insta CTD, on a FRESH save with less mods enabled than the previous one (I use Mod Organizer so left over scripts of mods was not theissue)
Okay, I loaded up the save again and I could come out of the basement this time, 10 minutes in.. CTD.. Load up again, 10 minutes again, CTD, all this while roaming the "triangle of death" area, because, well, its the starting area, the save is not even 2 hours old and its already crashing non stop:/

Now, that being said, I did went with level 3 cities at start with max population, but, thing is, these are the same settings I used on the previous 2 day save, and that save was more stable , at least when I started that save it was xD, I had almost no CTDs i could play for long sessions before I would eventually CTD, but this time around well, something didn't go well apparently...

I know its going to be my machine struggling, but maybe some one can tip me on which settings to tamper with so I can at least get the game running properly, what comes weird to me is that it wasn't crashing this much on the previous save, looks like something got stuck pretty bad this time around, Active Scripts on the save are normal , only 4.

My Potato specs:

Intel Core i5 4440 3.1GHz
8GB RAM
Seagate 7200RPM 1TBHDD(D: )
WD Blue 5200RPM 200GB HDD(C: ) for OS (Its crap I know but it was an emergency, Pagefile is still allocated on the D:/ Drive)
Nvidia GeForce GTX 970
Windows 10 build 1809 with October's Update installed.

It's an almost 5 year old PC , not sure if its enough for the task of the heavy scripting this mod involves or not, but Im playing the game at Ultra-ish settings at exception of some settings.
I tried turning the sliders for Objects/NPCs/Grass down in game but that didn't help, still crashing a ton on the new save :/
 
Last edited:
Having all the cities at level 3 and max pop is prolyl whats doing it. I had the same problem on my system. I would recommend starting some cities at level 1 and not have all cities starting at the beginning. Also avoid sanctuary/red rocket.
You can try some of these https://simsettlements.com/web/wiki/index.php?title=Performance

Reducing your game settings would be a good idea as well,go for medium.
 
As uit mentioned, this is likely due to too much being done with Conqueror. I'd recommend trying it out next time with the default settings from Conq to see if your system is stable. If so, then you can try bumping it up a bit in future runs, but if not, then you should probably open up another help request so we can see if there's some sort of mod conflict or specific issue you're running into.
 
Top