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!

Closed Plot Post/ASAM Issue

pyratelv

Active Member
Messages
172
I just jumped into the game again after a few weeks of not playing, D/Led all the recent updates for SS and it seems Im having an issue activating Plots
ASAM (E) Activate: only switches the green/red light. Doesn't bring up the menu.
(E)&(R) on the Plaque do nothing.
IBB does nothing.
I can go into Workshop and destroy/re-drop plots, but cant use the post to choose the new plot.
I can interact with doors, radios and other things on plots. Just not the Post/ASAM.
Also, some of the indicators on the Menu Manager (power/home/job) arent working. I have 3 Settlements that say I have citizens without jobs and/or homes when they do. All Settlements Power shows Zero, when power is fine.
Nothing new has been installed
I removed "Sim Settlements Building Plans Tags and more" awhile back because it was causing issues and everything has been working really great.
Up till now that is.

Anyone else having these problem?
 
You may need to do a manual install of Sim Settlements and Industrial Revolution, sounds like some of the scripts are missing.
 
If you need it, there is a link to a help video on the Wiki for Installation Problems and doing a manual install.
Video Mod Help - Installation Problems

Wiki Link: https://simsettlements.com/web/wiki/index.php?title=Install#Video_Guide

Direct to Video Link:
To view this content we will need your consent to set third party cookies.
For more detailed information, see our cookies page.
 
Did a Manual Re-Install twice. Still having the same issues
Ive gone through every SS Mod and cant find any files that are missing

Dont understand what went wrong. Everything was working perfect just a few weeks ago
 
Last edited:
Does the issue happen if you test on a different character?
 
Ill try and see if the same issues happen on another build.
Checking now

*Yes its a game wide problem. Checked all my 5 SS builds all the way back to when I first installed SS.
Cant interact with any Post/ASAM in any of them
 
Last edited:
I seem to remember having the same thing a few weeks back and all i did was to fast travel back to the settlement and it was ok then, I've only had it happen the once.
Maybe something loading slowly or just a glitch?
 
I seem to remember having the same thing a few weeks back and all i did was to fast travel back to the settlement and it was ok then, I've only had it happen the once.
Maybe something loading slowly or just a glitch?

FT to all my Settlements with SS. Same issue in all of them.
 
Tried it on my Clean Save (before installing/using the SS Holotape for the first time).
Still doesnt work.
ASAM doesnt even show up now(set to Visible). Just the Plaque that says "unoccupied lot"
 
Its frustrating. Everything was working excellent.
Plots werent randomly resetting or rebuilding. Crashes werent happening as often. Settlers werent showing up naked
Ill just chalk this up to my FO4 being the weirdest every.
I experience so many strange bugs.

Eventually it will start working again. Just cant build anything new for awhile
 
Can you load your save in Fallrim Tools and check what your Active Script count is?
 
Are you by chance using Place Anywhere with the Options Menu feature on? There have been some previous bug reports describing some of the same problems. The cause was Place Anywhere Options Menu interfering with various Plot Activation. Fix was turning off Options Menu.

Previous Post: https://www.simsettlements.com/site/index.php?threads/xbox-unable-to-read-plaques.363/

If you mean Place Everywhere, yes. Though I dont know how to turn Options Menu Off or On.
Dont know how it got that way in the first place (bad keypress?)
What key is it?
 
Did some more digging. looks like it is only on Xbox. So most likely not your issue, since you have PC selected for playing on.
 
Did some more digging. looks like it is only on Xbox. So most likely not your issue, since you have PC selected for playing on.
Well thats good to know.
Though I wish that was the problem so I knew the fix.
 
Last edited:
9 active is a good safe number, so I don't think it's a script backup issue.

Since it's happening for all of your saves, and you've done a manual install, the last two problems to check are:

1. Is it another mod? You can quickly test by disabling everything but Sim Settlements and loading in. Don't re-save during this test or all of your various mod progress will be lost, but since you have some easy things to test, like the ASAM Sensor menu, it should be a quick check.

2. Are your FO files corrupt? Steam can do a verification to fix up any missing files. I've heard of Steam messing with saves when you do this, so I'd recommend backing up your Documents/My Games/Fallout 4/Saves folder first.
 
1. Is it another mod? You can quickly test by disabling everything but Sim Settlements and loading in. Don't re-save during this test or all of your various mod progress will be lost, but since you have some easy things to test, like the ASAM Sensor menu, it should be a quick check.

Possibly. I only updated 3 other mods besides SS and SS:IR recently so I will try and see if those are the problem.
Otherwise I will start with my Clean Save and make a new build and re-enable mods 1 by 1 (148) till I find whats causing the issues.

2. Are your FO files corrupt? Steam can do a verification to fix up any missing files. I've heard of Steam messing with saves when you do this, so I'd recommend backing up your Documents/My Games/Fallout 4/Saves folder first.
This is what I will do first and actually could be the problem. It has happened twice before. Its also the easiest to recover from as it only messes up my Fallout4Prefs.ini files
 
Pyratelv: reenabling one by one is going to take forever.

Your best bet is to enable exactly half your mods along with Sim Settlements. If the problem goes away then the issue is in the half you still have disabled, so enable those and disable the first half and check again. This will tell you which half of your mods the issue is in. Once you've narrowed that far, disable half the ones in the failing half and test, then do the other half. If the problem appears in one of those halves, you're down to 35 that need to be checked. Keep making the problem appear and disappearuntil you've narrowed it down.

Worst case, 9 passes will be needed to narrow in on the problem mod. Beats doing 148 one by one by a long margin.
 
Top