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!

Solved Crash When Approaching Settlements

KennedyMadeIt

Member
Patreon Supporter
Messages
46
Game configurations:
  • New game
  • Sim Settlements Three-in-One v4.0.10
  • Sim Settlements - Conqueror v4.0.10
  • Workshop Framework v 1.1.6
  • No additional city plans. Only using optimized RotC plans.
  • Only have settlements pre-built by Conqueror.
  • Running on hardware that is more than capable of running Fallout 4.
  • Papyrus memory settings are set in Fallout4Custom.ini.
Issue:

Some settlements consistently cause a crash when they are approached. The effected settlements in my current game are Graygarden and Oberland Station. Both are not yet conquered. Other large settlements (containing many objects) such as Starlight Drive-In and Outpost Zimonja load perfectly fine when approached.

I've also tested while doing following:
  • Disabling all add-on packs.
  • Disabling all Sim Settlements performance options.
  • Disabling multi-threading.
All settlements in my game are pre-built by Conquer and use the optimized city plans included with RotC. I don't have any additional city plans installed. I haven't manually placed any additional objects in any city. I haven't increased the build limit for any city. I'm not using any other mod outside of the realm of Sim Settlements that effects settlements. I always thoroughly check for conflicts before committing to using a mod. No mod is conflicting with Sim Settlements or it's peer mods. The papyrus logs, as expected, don't provide any context for the crash.
 
Game configurations:
  • New game
  • Sim Settlements Three-in-One v4.0.10
  • Sim Settlements - Conqueror v4.0.10
  • Workshop Framework v 1.1.6
  • No additional city plans. Only using optimized RotC plans.
  • Only have settlements pre-built by Conqueror.
  • Running on hardware that is more than capable of running Fallout 4.
  • Papyrus memory settings are set in Fallout4Custom.ini.
Issue:

Some settlements consistently cause a crash when they are approached. The effected settlements in my current game are Graygarden and Oberland Station. Both are not yet conquered. Other large settlements (containing many objects) such as Starlight Drive-In and Outpost Zimonja load perfectly fine when approached.

I've also tested while doing following:
  • Disabling all add-on packs.
  • Disabling all Sim Settlements performance options.
  • Disabling multi-threading.
All settlements in my game are pre-built by Conquer and use the optimized city plans included with RotC. I don't have any additional city plans installed. I haven't manually placed any additional objects in any city. I haven't increased the build limit for any city. I'm not using any other mod outside of the realm of Sim Settlements that effects settlements. I always thoroughly check for conflicts before committing to using a mod. No mod is conflicting with Sim Settlements or it's peer mods. The papyrus logs, as expected, don't provide any context for the crash.

:bye great explanation!

I would start with:

https://www.simsettlements.com/site/index.php?forums/educational-guides-vault-13.145/

There are settlement recovery procedures there that explain the procedures for remote destruction of a location.

I would also try:

ASAM Maintenance Software

https://www.nexusmods.com/fallout4/mods/30500


You may want to post a screenshot of your fallrim results to see if scripts are backed up.

To view this content we will need your consent to set third party cookies.
For more detailed information, see our cookies page.

Also, check the wiki page: "see the ini settings"

https://simsettlements.com/web/wiki/index.php?title=Performance

[Papyrus]
fUpdateBudgetMS=2.4
fExtraTaskletBudgetMS=2.4
iMinMemoryPageSize=256
iMaxMemoryPageSize=1024
iMaxAllocatedMemoryBytes=307200

Lastly, I have tried the opposite of disabling multi-threading and pushed it up to 30 and tried to get close as I can, then just wait. This is my last idea.

I hope something helps in the above... :pardon

 
My save doesn't have any active scripts. It's a new game. I already have the Papyrus memory settings set in my Fallout4Custom.ini file. I can't get close enough to the effected settlements to perform any remote operations on them. It's odd that a pre-built settlement that I've never been to would need to be completely destroyed just to visit it.

I've never used the ASAM Maintenance Software mod before. I'm definitely going to try that out with settlements that I can approach.
 
Try leaving the game running for 20 minutes without doing anything when you load up your fresh save, that's the way I did this last time, I first prebuilt the settlements without any additional mods but sim settlements and the addons, then I saved and I quit, then loaded all my mods at once, which are a lot btw, loaded up my save and I got hungry so I went to eat and had I got entertained and when I came back the game was stable af. Go figure. I haven't crashed but once since then.. and I was getting crazy CTD every corner on a fresh save like you before.

Honestly, I think its a bad script, lurking around... this has become too common and its very weird..

Also if you can't approach settlements you can go nuclear on them instead:

https://www.simsettlements.com/site...-recovering-a-problem-settlement-part-1.7125/

scroll to the bottom
 
I'm working on narrowing down a CTD possibly in auto assignment or in the settler list, which would probably be applicable in these two settlement cases, so just for grins please try this possible fix:

Try approaching on foot then switch to flying(tcl) and at max sighting distance select four settlers and use the console to kill them. Switch out of flying and then approach.

IF that worked then please let us know.
 
I'm working on narrowing down a CTD possibly in auto assignment or in the settler list, which would probably be applicable in these two settlement cases, so just for grins please try this possible fix:

Try approaching on foot then switch to flying(tcl) and at max sighting distance select four settlers and use the console to kill them. Switch out of flying and then approach.

IF that worked then please let us know.

As a mater of fact I am almost finished writing a guide and this was a tip included in it, according to a thread in afkmods, the more settlers you have assigned to scripted resources or even animated furniture (since they are techically the same, scripted furniture) , the more you choke the scripts that handle the workshop, also if you surpass the limit of 20 settlers it becomes more of a problem, I've seen that if you chose too high population at startup the settlements can end up having like 29 settlers once you raid if you choose to keep captives, and THAT could lead to crashes, it was confirmed by the UFO4P team.

I am going to have the guide up in this forum as soon as im finished with it , I have already included 10+ tips that will increase stability.

In addition to that for the meantime, OP, try setting everything to "Manual" in the Upgrades tab.
 
I have found a reproducible solution to my Graygarden approach crash. I used the ASAM Maintenance Software to change a Style Wagon interior commercial plot to a Caps General. I did this on a terminal not far from Graygarden. The one on a train car that controls the door of a power armor transport cage. I tried changing one plot at a time until I was finally able to enter Graygarden without crashing.

I chose to change the Style Wagon to a Caps General because I know that a fix was made specially for the Caps General that causes an approach crash in version 4.0.9. I performed this more than twice with 100% reproducibility.

To reestablish the context of this test: the Graygarden build I used was in a new game. It was 100% pre-built by Conquer. I had never been to Graygarden in the game save before performing the test.

Could there be an issue with Style Wagon similar to the one @kinggath fixed for Caps General?

Fallout4 7_13_2019 8_46_18 PM.png Fallout4 7_13_2019 9_15_35 PM.png Fallout4 7_13_2019 9_15_55 PM.png
 
There was a Style Wagon at Oberland Station as well. I changed it to a Caps General, using the same method and terminal mentioned in my previous post, and was able to enter the settlement without crashing.
 
Someone suggested an issue with Style Wagon recently, and I couldn't replicate any crashing - tried all 3 levels of the building plan...

What are your system specs? We recently discovered that Radeon cards can render certain shaders correctly, so I'm starting to suspect that I may have to rebuild our texture files. I haven't found it as a source of crashing, but it's making me think that different hardware could be failing to handle different assets in the way we've built them - which would explain why so many people can have wildly different results with the mod....
 
Someone suggested an issue with Style Wagon recently, and I couldn't replicate any crashing - tried all 3 levels of the building plan...

What are your system specs? We recently discovered that Radeon cards can render certain shaders correctly, so I'm starting to suspect that I may have to rebuild our texture files. I haven't found it as a source of crashing, but it's making me think that different hardware could be failing to handle different assets in the way we've built them - which would explain why so many people can have wildly different results with the mod....

If it's any useful info to you, I was having similar crashes, but I doubt its the textures, I couldn't manage to get around the corner on a new game with just SS + Addons on a fresh save, CTD every 3 minutes or so, then I decided to refuse playing with SS and I started a new game without SS and everything was smooth, but I missed SS and it was not the same without it, so I tried again after a couple of days of playing modded FO4 without SS, launched up the SAME SAVE I tried when I was getting CTD, the only thing I did was lower some of the settings in the MCM like Auto Assign, Auto upgrade, etc , toggled to OFF, and I left my char idling in a settlement for like half an hour when I enabled my mods, I've been playing on that save for 2d 4h and 30ish minutes now, I've had about 7 crashes in 2 days game time, where as before I was getting CTD every corner , every 3 minutes, without any additional mods.

I think its scripts overwhelming the game engine, oherwise I have no explanation on why it decided to "randomly" work again out of a sudden, at least on my case, because if it was textures, I would still be crashing, and more often, since I just added mods which *should* have made the matters worse
 
i think this is a good post. i have ss enabled, but i have disabled a LOT of things in it. not out of malice or anything like that - just simply to minimize the risk of a script or series of scripts overloading the engine and forcing a ctd.

what i also did was follow the advice of sclerocephalus from the afkmods team, who posted some good information in the ufo4p discussion forum about minimizing things such as turrets and settlers. the busier the settlement the harder it is to get things to go.

with that recommendation in my head, i disable a lot of things. probably to the detriment of my own game - but doing that - i get very stable gameplay. probably very basic compared to some games, but stable. i like stable! :)
 
Oh yeah! ^ same here, reducing the amount of scripted resources at settlements seem to have made them really more stable, like, non placebo speaking here and I'm pretty sure about it, also not going above the limit of 20 settlers! Thats another thing I did , sent the extra people to other settlements when conquering them, because after conquering there were times I ended up having around 29 settlers in one settlement!

But as for the CTD, it could be a really bad script in one of the addon packs as well, that no one has traced yet.
 
I will say, that the script footprint of SS is very compact now. It does a lot, but I have everything spaced out on timers, and threads to avoid getting anywhere close to the limit. If you find that your save files in Resaver show ActiveScripts piling up from SS, definitely send me those saves as they'll point me to things I can further optimize.

My own recent LP has been a great testament to how resilient this game engine can be. I have what would now be considered a moderate gaming computer and I have Sanctuary running with 50 settlers and 100 plots without crashes... just the expected FPS drop.
 
I will say, that the script footprint of SS is very compact now. It does a lot, but I have everything spaced out on timers, and threads to avoid getting anywhere close to the limit. If you find that your save files in Resaver show ActiveScripts piling up from SS, definitely send me those saves as they'll point me to things I can further optimize.

My own recent LP has been a great testament to how resilient this game engine can be. I have what would now be considered a moderate gaming computer and I have Sanctuary running with 50 settlers and 100 plots without crashes... just the expected FPS drop.

May I know which addons are you using? Maybe its something on the addons that are not RotC..?
 
I have the majority of them installed now, so I'll go with the ones I'm not using:

JTBryant's Addons
IDEK's Logistics
Legalize the Commonwealth
Horizon Job Plots
Bad Neighbors

Pretty sure I have all of the rest, either directly, or via the MegaPacks.
 
Hmmmm, yeah, the only one of those im using is Legalize, but I doubt it, I've seen a couple of users report ctd with just base SS and RotC these past weeks, and I personally was having them as well, I still have them, but they're not every 5 minutes at least, I can play for 3 hours most of the time, on rare occasions I crash early on my gameplay session but its not constant anymore.

Either way, my game is pretty stable-ish right now, just as I said im not sure what I did, it was not the mods, cause Im running 298 mods right now, 223 ESM+ESP and 11 ESL's, I did disable all the CC crap and that sort of stuff , I think that helped a bit.
 
------------------
System Information
------------------
Time of this report: 7/17/2019, 22:27:43
Operating System: Windows 10 Home 64-bit (10.0, Build 17134) (17134.rs4_release.180410-1804)
Language: English (Regional Setting: English)
System Manufacturer: Gigabyte Technology Co., Ltd.
System Model: AX370-Gaming K3
BIOS: F3 (type: UEFI)
Processor: AMD Ryzen 7 1800X Eight-Core Processor (16 CPUs), ~3.6GHz
Memory: 16384MB RAM
Available OS Memory: 16332MB RAM
Page File: 7573MB used, 12854MB available
Windows Dir: C:\WINDOWS
DirectX Version: DirectX 12
DX Setup Parameters: Not found
User DPI Setting: 240 DPI (250 percent)
System DPI Setting: 288 DPI (300 percent)
DWM DPI Scaling: Enabled
Miracast: Available, with HDCP
Microsoft Graphics Hybrid: Not Supported
DxDiag Version: 10.00.17134.0001 64bit Unicode

---------------
Display Devices
---------------
Card name: NVIDIA GeForce GTX 1080 Ti
Manufacturer: NVIDIA
Chip type: GeForce GTX 1080 Ti
DAC type: Integrated RAMDAC
Device Type: Full Device (POST)
Device Status: 0180200A [DN_DRIVER_LOADED|DN_STARTED|DN_DISABLEABLE|DN_NT_ENUMERATOR|DN_NT_DRIVER]
Device Problem Code: No Problem
Driver Problem Code: Unknown
Display Memory: 19293 MB
Dedicated Memory: 11127 MB
Shared Memory: 8166 MB
Current Mode: 3840 x 2160 (32 bit) (60Hz)
HDR Support: Supported
Display Topology: Internal
Display Color Space: DXGI_COLOR_SPACE_RGB_FULL_G22_NONE_P709
Color Primaries: Red(0.659680,0.340344), Green(0.244641,0.670422), Blue(0.130383,0.040539), White Point(0.313000,0.329602)
Display Luminance: Min Luminance = 0.010000, Max Luminance = 1499.000000, MaxFullFrameLuminance = 799.000000
Monitor Name: Generic PnP Monitor
Monitor Model: LG TV
Native Mode: 3840 x 2160(p) (60.000Hz)
Output Type: HDMI
Monitor Capabilities: HDR Supported (BT2020RGB BT2020YCC Eotf2084Supported )
Display Pixel Format: DISPLAYCONFIG_PIXELFORMAT_32BPP
Advanced Color: AdvancedColorSupported
Driver Name: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_5db32447b43ce666\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_5db32447b43ce666\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_5db32447b43ce666\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_5db32447b43ce666\nvldumdx.dll
Driver File Version: 25.21.0014.1771 (English)
Driver Version: 25.21.14.1771
DDI Version: 12
Feature Levels: 12_1,12_0,11_1,11_0,10_1,10_0,9_3,9_2,9_1
Driver Model: WDDM 2.4
Graphics Preemption: Pixel
Compute Preemption: Dispatch
Miracast: Not Supported by Graphics driver
Hybrid Graphics GPU: Not Supported
Power P-states: Not Supported
Virtualization: Paravirtualization
Block List: No Blocks
Catalog Attributes: Universal:False Declarative:False
Driver Attributes: Final Retail
Driver Date/Size: 1/10/2019 8:00:00 PM, 957616 bytes
WHQL Logo'd: Yes
WHQL Date Stamp: Unknown
Driver Strong Name: oem2.inf:0f066de35d9aeff6:Section108:25.21.14.1771:pci\ven_10de&dev_1b06
Rank Of Driver: 00D12001
Video Accel:
DXVA2 Modes: DXVA2_ModeMPEG2_VLD DXVA2_ModeVC1_D2010 DXVA2_ModeVC1_VLD DXVA2_ModeH264_VLD_Stereo_Progressive_NoFGT DXVA2_ModeH264_VLD_Stereo_NoFGT DXVA2_ModeH264_VLD_NoFGT DXVA2_ModeHEVC_VLD_Main DXVA2_ModeHEVC_VLD_Main10 DXVA2_ModeMPEG4pt2_VLD_Simple DXVA2_ModeMPEG4pt2_VLD_AdvSimple_NoGMC DXVA2_ModeVP9_VLD_Profile0 DXVA2_ModeVP9_VLD_10bit_Profile2
D3D9 Overlay: Supported
DXVA-HD: Supported
DDraw Status: Enabled
D3D Status: Enabled
AGP Status: Enabled
MPO MaxPlanes: 1
MPO Caps: Not Supported
MPO Stretch: Not Supported
MPO Media Hints: Not Supported
MPO Formats: Not Supported
PanelFitter Caps: Not Supported
PanelFitter Stretch: Not Supported
 
I just now encountered another settlement in my game that caused a crash when approached, County Crossing. I loaded the game again after the crash and checked out which plots were in the settlement using the ASAM Maintenance Software on Kessler's terminal in Bunker Hill. Sure enough it had a Style Wagon.

First I tried changing a Red Yao Guai Armoury to a Caps General and the crash still happened. I loaded the save again and changed the Style Wagon to a Caps General and was able to approach the settlement without a crash.
 
I just now encountered another settlement in my game that caused a crash when approached, County Crossing. I loaded the game again after the crash and checked out which plots were in the settlement using the ASAM Maintenance Software on Kessler's terminal in Bunker Hill. Sure enough it had a Style Wagon.

First I tried changing a Red Yao Guai Armoury to a Caps General and the crash still happened. I loaded the save again and changed the Style Wagon to a Caps General and was able to approach the settlement without a crash.

@KennedyMadeIt

help me out, which add-on is associated with the style wagon?

I might as build one in my game and see what happens?
 
@KennedyMadeIt

help me out, which add-on is associated with the style wagon?

I might as build one in my game and see what happens?

Style Wagon is an interior commercial plot that comes with Sim Settlements.

Also keep in mind that the settlements that are crashing are pre-built by Conquer. I haven't tested manually building a Style Wagon in a settlement that I own.
 
Top