Question Crash When Approaching Settlements

Discussion in 'SS Help (Mod Questions Here)' started by KennedyMadeIt, Jul 11, 2019 at 10:58 PM.

  1. KennedyMadeIt

    KennedyMadeIt New Member

    Joined:
    Oct 28, 2018
    Messages:
    9
    Likes Received:
    5

    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.
     
    nzane likes this.
  2. RayBo

    RayBo Well-Known Member Patreon Supporter Community Rockstar Support Team Vault Librarian

    Joined:
    Jun 6, 2017
    Messages:
    1,180
    Likes Received:
    1,866

    :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.



    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

     
  3. KennedyMadeIt

    KennedyMadeIt New Member

    Joined:
    Oct 28, 2018
    Messages:
    9
    Likes Received:
    5

    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.
     
    nzane likes this.
  4. nzane

    nzane Member

    Joined:
    Jan 25, 2019
    Messages:
    98
    Likes Received:
    40

    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
     
    WetRats and RayBo like this.
  5. Xeteco

    Xeteco Member

    Joined:
    Jun 8, 2018
    Messages:
    46
    Likes Received:
    27

    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.
     
    nzane likes this.
  6. nzane

    nzane Member

    Joined:
    Jan 25, 2019
    Messages:
    98
    Likes Received:
    40

    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.
     
    NikolajtheNord, RayBo and Xeteco like this.
  7. KennedyMadeIt

    KennedyMadeIt New Member

    Joined:
    Oct 28, 2018
    Messages:
    9
    Likes Received:
    5

    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
     
    nzane likes this.
  8. KennedyMadeIt

    KennedyMadeIt New Member

    Joined:
    Oct 28, 2018
    Messages:
    9
    Likes Received:
    5

    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.
     

Share This Page