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!

Hotfix 3.0.3b

kinggath

kinggath

Well-Known Member
Staff member
Administrator
Moderator
Verified Builder
Messages
5,184
If you downloaded 3.0.3 or 3.0.3a yesterday, please update to 3.0.3b and roll back your save to before you patched. Or, if you don't want to roll-back, or don't have a save to do so, you can clean save Sim Settlements out of your save (which will reset your SS progress - but not the rest of your character). Clean save instructions at the bottom of this message.

If you're on PC, you don't have to roll back or clean save, you can use Fallrim Tools to kill the runaway script.

1. Download and install Fallrim Tools
2. Open Resaver.exe, load your latest save file.
3. Expand ActiveScripts, search for any entries of "SimSettlements:SimParentScript"
4. Expand each of those and look for "SetupCurrentMaintenanceCosts", if you find it, right click on the folder icon above it and choose terminate.
5. Click File->Save
6. Install 3.0.3b of Sim Settlements if you haven't already and load your save.

NOTE: If Fallrim Tools gives you a message about Invalid plugin index, snag the 3.0.1 version of Fallrim Tools.


Apologies for this issue guys, and thank you @EyeDeck for discovering and reporting it to me right away!


Clean Saving

1. Disable Sim Settlements and all related mods, such as the expansions, add-on packs, or any other mod that specifically alters Sim Settlements. You can do this quickly by going to the Mods screen, then the Load Order screen and unchecking them.
2. Load your save.
3. Create a new save file from the pause menu (if you're on Survival, you'll want to pick up a mod that allows survival mode saving).
4. Re-enable your Sim Settlements mods.
5. Load that new save file you created.
 
Last edited:
So, uh, unfortunately, if you have Creation Club mods, ReSaver doesn't recognize the mod slot they're in and won't load.
 
Fallrim Tools 3.0.1 will work with Creation Club saves, not sure why the Fallrim Tools creator broke his original fix.
 
kinggath said:
If you downloaded 3.0.3 or 3.0.3a yesterday, please update to 3.0.3b and roll back your save to before you patched.

If you're on PC, you don't have to roll back, you can use Fallrim Tools to kill the runaway script.

1. Download and install Fallrim Tools
2. Open Resaver.exe, load your latest save file.
3. Expand ActiveScripts, search for any entries of "SimSettlements:SimSettlementParent"
4. Expand each of those and look for "SetupCurrentMaintenanceCosts", if you find it, right click on the folder icon above it and choose terminate.
5. Click File->Save
6. Install 3.0.3b of Sim Settlements if you haven't already and load your save.


Apologies for this issue guys, and thank you @EyeDeck for discovering and reporting it to me right away!
Click to expand...

Should this be SimSettlements:SimSettlementParentscript"? I don't see SimSettlements:SimSettlementParent".

Thanks
 
adb1x1 said:
Should this be SimSettlements:SimSettlementParentscript"? I don't see SimSettlements:SimSettlementParent".

Thanks
Click to expand...

Yeah, bethesda arbitrarily appends "script" to the ends of script names for some reason, even though we know they are scripts because they're of a script type. (sorry, just a minor rant there :P)
 
I get an error trying to load saves with Fallrim about "Invalid plugin index: 254" and my only saves that predate 3.0.3 are from 3 days ago. There's no other way to fix this?
 
Vortec said:
I get an error trying to load saves with Fallrim about "Invalid plugin index: 254" and my only saves that predate 3.0.3 are from 3 days ago. There's no other way to fix this?
Click to expand...
If you get that error, download the 3.0.1 version of Fallrim Tools, it's available in the files section on that page.
 
Right! Maintenance actually seems to be getting calculated properly now. Loading in the middle of a settlement with a bunch of City Supplies scripts running (probably brought on by the infinite loop bug, I only edited out the parent) threw an error and crashed, but loading a save outside the city and letting Sim Settlements update seems to have done the trick.
 
kinggath said:
If you get that error, download the 3.0.1 version of Fallrim Tools, it's available in the files section on that page.
Click to expand...

That worked. I ended up terminating every instance of SimSettlements:SimSettlementParentScript since they all contained SetupCurrentMaintenanceCosts and it also fixed the issue with plots from add-ons not loading, which is what led me here looking for help in the first place.

Thank you!!
 
kinggath said:
If you downloaded 3.0.3 or 3.0.3a yesterday, please update to 3.0.3b and roll back your save to before you patched.
Click to expand...

Is there ANY way you can put the Update # in the Mod info area? I can't tell which mod is which because the numbers for XB1 mods are different. Thank you!!
 
Does the number I set up on Bethesda.net never show up in the game?

upload_2018-1-12_20-24-15.png

If not, shame - Bethesda, shame!
 
mytigio said:
Yeah, bethesda arbitrarily appends "script" to the ends of script names for some reason, even though we know they are scripts because they're of a script type. (sorry, just a minor rant there :P)
Click to expand...
Hello, I found 2 entries using FallRim in my save but the title is a little different.
simsettlements:simparentscript
Is this the same thing? Thanks.
 
Woah what I'm confused I'm on xbox and have a older save I'm sure that one will work but why is this necessary what happend?
 
What does terminating these active scripts mean? They contained more than only "SetupCurrentMaintenanceCosts" in them for me atleast.
What I really mean is, what info are we deleting along with this script that has the error? Or is everything related to the error and these scripts shouldn't exist in the savefile at all?
 
what you're killing is a bugged script that is stuck in an infinite loop. If you kill only the one listed, it'll just regenerate a new version that isn't bugged when it needs to.
 
You must log in or register to reply here.
Top