Closed Settlement HuD unchanged

[marauder13]

G'Day all,

I have a problem with the HuD displaying the various meters for the SimSettlement remained fixed, regardless of what other active settlements my character travels to. It even remains on screen in open territory. This has only happened since I loaded the latest version of the SimSettlement files.

Relevant information
Windows 10 PC
Fallout 4 ver 1.10.75.0
F4SE ver 0.6.6 rel 13
SimSettlement, Industrial Revolution & Rise of the Commonwealth 3.1.5
Difficulty mode : Survival
Screenshot0.png shows the status just after loading the saved game, while in Sanctuary. It has been activated as a city.
Screenshot2.png is when the character is in the Red Rocket settlement, which is activated, but not setup as a city. As you can see, the HuD meters are exactly the same.

If there is anything else that you would need, or want, to assist in finding out what is happening, please let me know and I will supply it, as I am not sure what other material is needed.


Thanking you in advance for your time and assistance,

marauder13

 

[Karyusan]

what's your spec for you pc ? and what happen if you stay some mins in anothers settlement the HUD change after 10-15 min ?

 

[Muddball]

I've had the Hud meter stick sometimes myself. Here are a couple of fixes I've found.

1) Sit in a chair and Wait 1 hour. Also literally wait a couple of min. this helps if the settlement is firing off scripts in the background has hasn't updated the hud yet.
2) Go to another settlement and back, EXCEPT for sanctuary and red rocket. They are just too close together i've found. Head over to Abernathy's farm and back if the problem is only with the above two.
3) Rest in a random sleeping bag outside any settlement for 4 hours. Concord has you covered there.

 

[marauder13]

Hello all.

Please disregard this bug report, as it is no longer relevant. Another issue has occurred that supersedes this error. Thank you for your time and assistance.

 

[thefirebirdman]

Closing this thread and moving it to Archive since the OP reported this was not an actual bug.