Scrapping Notes: MANUALLY scrap this settlement - do NOT use scrapall! As usual I recommend against scrap mods or you'll likely end up removing something I didn't plan for you to remove.
There's a few items that will only get removed if you manually scrap the counters they are attached to, as well as a couple debris piles that get removed with benches/tires/etc.
Here are a couple pics of the settlement scrapped as I did it:
I used Place Everywhere in INS mode to remove one concrete barricade and the two doors at the back of the settlement that open up into the BoS workshop where all Liberty Prime's bits are stored.
I noticed a couple times during test imports, the left half (to the mech's left) of this settlement wasn't powering up for no obvious reason. Simply re-snapping the conduit in the below screenshot fixed it for me:
I've already tried use next-gen version of Transfer Settlements. Settlement was imported successfully, but save/load/fast travel lasts too long, even long save bug fix was powerless to fix that. TS have failed me for the last time. Transfer Settlements is no longer actual for me as settlement importer, Workshop Framework is much better - it's more stable and faster, and game is not freezes after using layouts. If you don't like my statement, I understand this. Imenem Ordena Krovavyh Voronov i Imperatora! I pust' nikto ne upreknet menya!
This makes me want to try my hand at my own titan build since I've already made the BOS into the Imperial Fists. Liberty Prime will finally have a friend
I have now tried to get this working for 3 times. It imports, stabilizes, powers up, the settlement is there. But when I try to save after all is done, the game get's stuck while saving. I waited for about 15 minutes, nothing, had to force close the game and all was lost. I already use your Castle blueprint, which installed without any issue. I will give it another try tomorrow, maybe leaving the area without saving there works around the issue.
Edit: Yepp, moving far away by feet and saving there did it for me - settlements is up and running fine :)
Hello! I love your design, I just wanted to share a possible issue with an object within the settlement that was giving me a creature2dtexture ctd.. It was the vaulttech manager terminal at the top of the greenhouse causing me to ctd when boarding a vertibird or flying in from Cambridge PD.
I found it just by scrapping chunks until the CTD 2dtexture stopped and narrowed it down from the greenhouse>vault terminal. Bizzare crash I can't really explain how that works but there you go. Hopefully this can help others if they come across the same thing I did.
Thanks for the heads up, but I have never heard of this before. Not saying it was an issue with your game, but I would have expected to hear something before now if it were a frequent problem. The blueprint is 3 years old now :)
86 comments
There's a few items that will only get removed if you manually scrap the counters they are attached to, as well as a couple debris piles that get removed with benches/tires/etc.
Here are a couple pics of the settlement scrapped as I did it:
I used Place Everywhere in INS mode to remove one concrete barricade and the two doors at the back of the settlement that open up into the BoS workshop where all Liberty Prime's bits are stored.
I noticed a couple times during test imports, the left half (to the mech's left) of this settlement wasn't powering up for no obvious reason. Simply re-snapping the conduit in the below screenshot fixed it for me:
I used the "Rapid Preset" in Transfer Settlements in the 'General Settings' and then used the options in the below screenshot for importing.
Edit: Yepp, moving far away by feet and saving there did it for me - settlements is up and running fine :)
I found it just by scrapping chunks until the CTD 2dtexture stopped and narrowed it down from the greenhouse>vault terminal. Bizzare crash I can't really explain how that works but there you go. Hopefully this can help others if they come across the same thing I did.
Not saying it was an issue with your game, but I would have expected to hear something before now if it were a frequent problem. The blueprint is 3 years old now :)