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!

Public Beta 1.0.1b

kinggath

Well-Known Member
Staff member
Administrator
Moderator
Verified Builder
Messages
5,172
Have another beta ready for you guys! I've started tackling some of the side character reports. Most of my week has been committed to wrapping up the initial release of the Add-on Maker's Toolkit, which I hope to drop this weekend. Still have some more stuff in mind to sneak in to 1.0.2 though!

  • Fixed a bug where Jake would not travel with the player during Where There’s Smoke if the player agreed to help, and instead would only show up when the player reached the final location.
  • The quest objective in Piper’s office triggered by one of The Ron’s settler recruitments will now correctly point to a note instead of nothing.
  • Fixed a bug that would cause the item for the quest Buckle Up, Buttercup to not appear correctly.
  • Fixed a bug that would prevent turning in Lacey Buckles’ quest.
  • Fixed a bug in the quest Not All Artists Starve which could cause the player to attempt to start the turn-in scene to every NPC due to a condition problem.
  • Fixed a bug in the quest Hub of the Problem where if you activated the inaccessible hatch without unlocking it, Jake could start his sub-basement scene before teleporting and he would fail to correctly go into the cell.
  • Fixed a bug in Hesper’s dialogue that would make some of the dialogue options not make any sense.
  • Fixed one of the production report messages to display the correct name.
  • Fixed another bug that was causing the “Ain’t Nothing But a Hounddog” quest to start for players automatically. This quest was not supposed to be released yet and will be re-enabled in a future update.
  • Added several additional templates to make it easier for add-on makers to generate content for SS2.
Download public beta 1.0.1b here

-kinggath
 
Getting a detected failed startup warning on the more recent versions of the mod when starting a new game. Older version, beta 1.0.0g for example, work just fine. One thing I noticed is when disabling the SS2 addon packs, the newer versions also seem to work. As always, thanks for the hard work.
 
The detected failure means that something in your load order is preventing everything from starting up as expected. This could mean too many things trying to launch at once gumming up the works, or an actual problem with the installation, such as a mismatch between the esm and ba2 (which can happen with mod managers on occasion).

It could also be a false positive. Due to the number of scripts that run during a new game from the base game and various mods, it could simply be that some things occurred in an unexpected order that triggered the warning from SS2 even though SS2 will ultimately complete its start-up for you.

If you receive this warning, my recommendation is to do a staged loading of your mods, saving your script heavy mods like SS2 for last. Ie. Disable it and all addons, and any other script heavy system mods (never include Workshop Framework or Unofficial Patch in this, those should always be there from the moment you start a new game if you're going to use them). Start your new game, and wait until a few minutes past character creation, make a save, then enable one of those mods, load back in to your save, wait 30 seconds, save, repeat. It's a pain, but you'll end up with a more stable save for it.
 
I'm still stuck on "Buckle up, Buttercup". I already had the bug and it still hasn't appeared at the quest marker. Is there a command I can use to advance it or anything?
 
Thanks for your detailed explanation, kinggath! Staged loading sounds like a good idea, I will give it a try and see how it works out for me.
 
I'm still stuck on "Buckle up, Buttercup". I already had the bug and it still hasn't appeared at the quest marker. Is there a command I can use to advance it or anything?
This is what Deepfreeze said in another thread:
"The quick way to get around this, until this is fixed, is to accept the quest from Lacey then open the console and type in:

setstage ss2_characterquest_laceybuckles 40

This immediately kicks you to the settlement select menu for Lacey, and ends the quest."
 
im having issues, do i have to enable the previous version of this mod in vortex and have this new one enabled at the same time???

plz help.
 
im having issues, do i have to enable the previous version of this mod in vortex and have this new one enabled at the same time???

plz help.
nevermind, fixed it and got the mission working thanks to the new update, danke KingGath.
 
awesome progress! will download and check! Thank you kingath and kingTeam!

EDIT01

"Where theres Smoke" was tough (I died 2 times) but very fun.
All quest stages worked fine! I installed Buffout4 just in case...

EDIT02
All fine, no CTD,
1 little hickup, when failing speech charisma, nobody steps forward, nobody talk to me, snief (I reload and passed the test and all went fine)
This were awesome quests! so much more to do. nearly missed getting last blueprint for the youknowwhatitem.
chapter1complete :grin :agree:
 
Last edited:
Getting a CTD when customizing plot power poles. Checked my Buffout 4 crashlog and there's many references to "PowerPole_StreetLamp.nif".
 
Even on this latest version, I still can't get the mod to work. When the stranger appears and gives you the ASAM sensor, the residential plot option never appears in the workshop menu, ive tried everything under the sun for it to work, but still no die. Is this a common issue?
 
i am having some difficulty being able to give jake some armor. i don't know if this is because he isn't always considered a companion, or a settler or an npc. i was able to give him a few pieces at the start of the game when your doing the concord mission. but after that, nothing.
 
Loaded this into my current save and got the resurrection message. I'm hoping this will at least cause the quest after "Where theres Smoke" to fire up.
 
The detected failure means that something in your load order is preventing everything from starting up as expected. This could mean too many things trying to launch at once gumming up the works, or an actual problem with the installation, such as a mismatch between the esm and ba2 (which can happen with mod managers on occasion).

It could also be a false positive. Due to the number of scripts that run during a new game from the base game and various mods, it could simply be that some things occurred in an unexpected order that triggered the warning from SS2 even though SS2 will ultimately complete its start-up for you.

If you receive this warning, my recommendation is to do a staged loading of your mods, saving your script heavy mods like SS2 for last. Ie. Disable it and all addons, and any other script heavy system mods (never include Workshop Framework or Unofficial Patch in this, those should always be there from the moment you start a new game if you're going to use them). Start your new game, and wait until a few minutes past character creation, make a save, then enable one of those mods, load back in to your save, wait 30 seconds, save, repeat. It's a pain, but you'll end up with a more stable save for it.
I have found that tales from the commonwealth causes The ss2 script to try and revalidate it self when I start a game. i am also using a few modern weapons replacers so guessing between that and tftcw installed it’s making ss2’s scripting slow down to much. Maybe a good idea to start the game with everything except ss2 activated then save after you leave the bathroom and before vault tec comes and then activate ss2 and start the game again should allow ss2 run without all the other scrips running at the same time. You could also do the opposite let ss2 load first then save and load the rest.

this isn’t a tales from the commonwealth issue just that having it run at the same time as ss2 and a bunch of weapons leveled list changes is to much.
 
I'm still new to mods and I've been using Vortex exclusively, so how do I install the public beta?
Download it from the link provided in this thread then start vortex deactivate the old ss2 mod then use the install from file button on vortex to download the file.
 
Okay so I thought I had to unzip the files and add them independently, I didn't realize that I could just select the zip file and Vortex would do everything for me and it would work. What an age we live in!

Thanks for the help folks!
 
This is what Deepfreeze said in another thread:
"The quick way to get around this, until this is fixed, is to accept the quest from Lacey then open the console and type in:

setstage ss2_characterquest_laceybuckles 40

This immediately kicks you to the settlement select menu for Lacey, and ends the quest."
Wouldnt happen to have a Set stage command for Blackmoon and Carl Meade would you? Both of those are bugged for me.
 
Top