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!

Solved ? Vassal Bug

Ozirambler

Ozirambler

Member
Patreon Supporter
Messages
31
Did all jammers initial quest and have RR as base and sanctuary as vassal. But with not enough money coming in I decided to take Abernathy as a Vassal. Joined the warriors and went through and took it with all settlers sitting down and defenders dead. Then once I got the notification that I had taken it, all settlers slowly get up and start fighting again but this time to the death. Have I missed something ?

As a side note I just updated mod files to latest version 4.1.2 before attacking/
 
Sort by date Sort by votes
Ozirambler said:
Did all jammers initial quest and have RR as base and sanctuary as vassal. But with not enough money coming in I decided to take Abernathy as a Vassal. Joined the warriors and went through and took it with all settlers sitting down and defenders dead. Then once I got the notification that I had taken it, all settlers slowly get up and start fighting again but this time to the death. Have I missed something ?

As a side note I just updated mod files to latest version 4.1.2 before attacking/
Click to expand...
Yeah this happens to me too i think what is a 4.1.2 bug.
 
Upvote 0 Downvote
I saw this on a new game last night but I moved a couple saves back, cleaned with resaver, uninstalled and reinstalled sim settlements, conqueror and workshop framework. That seemed to clear it up but it might just be one of those things.
 
Upvote 0 Downvote
So I've seen this issue too, both before and after the 4.1.2 patch. This is just a guess, and not even a super educated guess, but it might be script lag that's the issue. Seems like it might be for me at least.

Here's an example, I just ran an assault on Oberland Station and, after the proverbial smoke cleared the first time through, I had 2 settlers left before they became pacified. However, while it happened I noticed that if anyone else knocked down settlers (raiders or even my own companions) that's all it was, they were knocked down again, not dead. If I shot them they died. So I reloaded and ran the raid again. This time, when the quest completed, I ran away. Everyone still went hostile and my raiders shot at some but I was out of range and didn't fire back so eventually it seemed scripts caught up and all was well. This time there were 14 settler/civilian survivors.

So I suggest if you see this happen try running away after the quest completes and see if that helps.
 
Upvote 0 Downvote
I realized I had script logging and debugging on and toggled that back off. It really seems like script lag in that the knocked down civvies were standing up and turning red again before the cap could complete. Loading a save prior to arranging the attack and redoing it until it completed worked eventually even with script logging on, so hopefully it will go flawlessly with logging off.
 
Upvote 0 Downvote
This issue comes up regular and 9/10 it's script lag, or a stray molly.

The best way to clear scripts is firstly add this under General in your Fallout4Custom.ini bAlwaysActive=1
It will prevent the game pausing while alt+tabbed.
Dismiss any companions then head to an internal cell, I usually go here coc debugjpsa
Then just let the game idle for a few hours.
 
Upvote 0 Downvote
You must log in or register to reply here.
Top