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!

Researching Still CTD with 3.2.1

Cranky Cat

Active Member
Patreon Supporter
Community Rockstar
Messages
291
I figure the drawcalls go way up when mods break the precombineds to make it possible to scrap or build or just generally in settlements.

3.2.0a is stable and with good framerates for me even in Sanctuary but my old save was from before I went through my settlements and deleted plots which would stop the rebuilds. I use the ASAM Maintenance Tool to figure out which plot it is if a plot doesn't finish refreshing during the refresh-all step and then delete the plot. I'll try 3.2.1 (or 3.2.2) again after I clean up the refresh fails again and make sure I'm not in the middle of a global refresh to apply new settings this time. Maybe something happened the first time which can be avoided.

I think the Papyrus engine doesn't do a good job of determining if a script should run or wait and if your system has fewer resources the engine is less likely to overreach. It could be tricky to lower the papyrus settings enough to avoid this while not causing scripts to terminate instead because they time out if there are lots of them triggering. I suspect the new cell load/unload changes may put me over the "tipping point" in some locations.
 

Rabscuttle

New Member
Messages
6
One more user's experience, just FYI

Love, love, love the mod, but...game is basically unplayable now. I'm sure it's the memory overload, I have a GTX 1070 (although only 8 GB RAM) so not a low-end machine, but I CTD about 50% of the time approaching Starlight or Sanctuary and they're only Level 1's. I cannot imagine how bad it will get if they reach Level 3 and other settlements level up also.

I followed the helpful advice on these forums and on Youtube. Turned down my overall graphics settings for the whole game and then dropped the configurations for SS itself from Ultra to High to Medium. Crashed both before and after upping the build limit, in case that was the problem.

I don't blame kinggath, he and the team have built an amazing mod. But we all know Bethesda did a terrible job optimizing their game and I think ROTC is probably too much for the game engine.
 
Last edited:

Cranky Cat

Active Member
Patreon Supporter
Community Rockstar
Messages
291
I don't think this has anything to do with the graphics settings. I turned mine down to a windowed lower resolution with low end settings and it didn't matter at all. Frame rates would be impacted but that's it.

I did see comments on the forums about CTDs when crossing cells being related to the last Bethesda patch but it's hard to say. I still haven't finished refreshing the plots in all of my settlements but will try 3.2.1 again after that to see if I still have issues after being still stable on 3.2.0 for a long time.

Also, I reset my build limit and recalculated it for Sanctuary and it was still below the default. I'm not sure that all plots support it though. Grey Gardens was built up using vanilla objects and mostly internal plots and was wayyyy over the limit and never had the issues there so I'm not sure that matters.
 

Drask

Member
Messages
73
So, Conqueror is live and I've got myself a new 2080ti that I'm running it on. I've got to say that it's running perfectly now. I wanted to test it so I put all cities at level 3 from the start and ran the game for over 6 hours with no crashes or hitches.

For Cranky and others running 2 gpu's:

During testing with my 2 980's, I did pull one and it didn't seem to make a big difference. However, I believe that I forgot to reinstall the graphics driver after doing so. This may have left some of the SLi stuff active. So, moving from 2 gpu's to 1 may be the fix that the high end pc users are looking for, as it worked for me (for the moment at least).

I wouldn't be surprised if it had to do with bethesda's VRAM allocation or something. With 2 4 GB cards, it might think that you have 8 GB of VRAM on a single card and not allocate it properly. My old cards only ran at about 70% and were crashing, but I never took a good look at VRAM usage, and if it's mis-allocation, then it would be really hard to see anyways. I always ended up getting a Visual C related crash where it was searching for various .dlls.

I'm just glad it's working right, after a year of pissing around with it. Hope this helps someone.
 
Top