Makes me wonder if there is a console command that can make me clear Slog for all build assets, to test if that fixes the issue.Įdited by HoratioCaius, 25 January 2021 - 06:48 AM. I have saves from 20 hours back, before Slog where made a settlement, and used city plan on. So maybe not a backlog of scripts that is the issue. Any suggestions?Ĭhecked save with Fallrim. I do have crimes and punishments in my load order, and a couple of quest mods. Took it to low performance, and still ctd. Then I started to check if it was performance. I realised that recently both workshop framework and SS2 has been updated.
Then suddenly (today) I got ctd when fast traveling or walking to Slog. Helped the settlement, made wiseman a leader, activated ur city plan, and has been around there a couple of times after. Everytime I am getting close to Slog, I get ctd. Thank in advance to anyone who can offer some insight.But I am now having a issue with one of the settlements. I'd really like to avoid having to start 100% over again and loose yet another 16 hours of play time. I'm honestly at my wits end with trying to figure this out, I will take any and all advice on fixing this.
Unofficial Fallout 4 Patch Workshop Framework Sim Settlements 2 HUDFramework Rise of the Commonwealrh for SS2 (Official) Caliente's beautiful bodies enhancer Settlement Menu Manager Craftable Display Shelves Face Texture Glitch Fix A Girly Animations X1 Jacq's NOT Default Eyes Ponytail Hairstyles by Azar Zella's Hair Dye Collection Sanctuary Bridge Fix SA80 (L85 & L86) British Rifle Here are what mods I still have running and in their respected load order. I have removed practically all my mods trying to trouble shoot this and still have not been able to get this to work. I have now trashed my game and started over 3 times to fix this with no fix. I have tried to talk to the guy (forget his name atm) and all he ever says is "Hello" and "Hi there" "Can I help you?" I have a quest marker for 81, but soon as I go inside I no longer have a marker.
I have been having issues with getting this quest to move forward.
0 kommentar(er)
