Menu
What's new
By:
Filters
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!

Question CTD on approach to settlement sites at start of new game

frazzlesnap

frazzlesnap

New Member
Messages
12
I'm not used to having problems with WSFW, and have been using it for a few years without incident. I recently purged my old Fallout 4 installation to start a completely fresh playthrough. On exiting Vault 111, I get a constant CTD on approach to Sanctuary or Abernathy Farm (the only two I've approached). Buffout and careful reading of the crash log files shows from 2 to 6 potential culprits, and WSFW is the only one that is always consistent. I tried uninstalling all the other listed mods, but it didn't help. Uninstalling WSFW fixed the CTDs. Going through the crash log line by line, it keeps referencing buildable areas, build limits, and other attributes directly tied to the workshop. I really need WSFW, because I am addicted to Sim Settlements 2, and I know that I must be having a problem that is not WSFW itself, since it has always been so stable. I've got a small, but highly interconnected mod list of 472 plugins, and many of the associated mods have cross-dependencies. I've tried testing with as few enabled as possible and just WSFW enabled, then re-enabling as few as possible to get functionality in each load instance, but it's taking ages. I think it's down to the previsbines, but uninstalling PRP and all associated patches still leaves the CTDs with WSFW. I would really appreciate any help, but understand that I haven't exactly approached this from the best angle. Thank you in advance.
 

Attachments

  • crash-2023-06-08-01-06-40-AUTOSCAN.txt
    7.5 KB · Views: 1
  • crash-2023-06-08-01-15-17.txt
    58.3 KB · Views: 3
Sort by date Sort by votes
LeapinL said:
If you are going to start a new game, and your game is through steam, you may want to verify your game files. Or reinstall the game. I have had several times that I broke my game with mods. :grin:scratchheadAnd that really helped to get it off to a good start. That and I use a start method now that someone shared with me. I will see if I can find it. It rolls the mods into your game gradually, and not all at once. Makes it easier to see if there is a conflict with some.
Click to expand...
I have verified my game files. When I try to start a new game with just the basics, including the Unofficial Fallout 4 patch, the game never loads. It goes from a black screen to CTD. No error log. I had it loading earlier today with all my desired mods, including WSFW and SS2, and being able to get to the workshop, but it would still CTD upon activation. I noticed the activation script for the workshop in the crash log (I started getting those again! Yay!) and thought that maybe something had overwritten it in the loose files. Nope. I pared my load order down and checked each crash log for a pattern, to the point where the game would no longer load at all and no longer generated crash logs, then I created a new profile in Vortex, disabled all mods, and just enabled the basics. I was never able to use the workshop in that whole time. Now it still won't load. I obviously have something left over somewhere that is borking things. I guess it's time to wipe the install and start over from scratch. Bloody hell. I've never had this level of trouble with any other game. Not even Skyrim SE, where I currently have 1356 plugins, plus about 110 dlls and a host of other plugin-less mods installed. That thing is comparatively stable. (I probably just borked it, too...) All hail the mighty Todd!
 
Upvote 0 Downvote
Mystical Panda said:
The normally happens if there' s a problem with the audio, or avi playback or a missing master file for a plugin.
Click to expand...
Yeah, I'm familiar with the missing master problem from way back in Morrowind days. I've nuked the install and redone it all from scratch. I made another major mistake, and jumped in whole-hog, instead of just enabling the bare minimums and working up from there. I can't create a new game - it just sits there forever - but I can load an old one I imported from the previous installation without trouble. I'm sorry for this unending tale of woe that I've brought upon myself by not following best practices. Same problems as before. I really am going to just disable all the third party mods and start again from there. Thanks for not abandoning me!
 
Upvote 0 Downvote
Unfortunately, I had to extract a bunch of ba2s to run my mod list, as I had way over the maximum allowed. I've got both the loose files and ba2s backed up, so I just need to empty those folders and test, I suppose. It just seems so crazy that modding Skyrim SE is so much easier and more stable than FO4...
 
Upvote 0 Downvote
frazzlesnap said:
It just seems so crazy that modding Skyrim SE is so much easier
Click to expand...
It is even easier if you buy a console. That is why a bought a console 15 years ago. I spent as much time playing with the computer to get things working as I did playing the games. FO4 is a much more complex game in it's architecture, there are a ton of simple things that mods can break. From reading this forum loose files want to be avoided. Do you really need your mod list to be so long? If you do, why don't you combine mods that are in the same area of your load order to make less mods and not break your limit and keep your BA2s.
 
Upvote 0 Downvote
You must log in or register to reply here.
Top