Question Beantown Brewery Exterior CTD

Seconded. This is the same exact behavior I experienced earlier today with 4.0.8 SS 3-in-1 + 4.0.8 Conqueror. Happened every time I got close to Beantown Brewery! I had to use the coc console command to get into the interior cell in order to finish the Tapped Out quest.

Update: rolling back to 4.0.7a SS 3in1 and 4.0.7b Conqueror has fixed this for me; now I can walk near or right up to Beantown Brewery again.

snarkhunter said:

Seconded. This is the same exact behavior I experienced earlier today with 4.0.8 SS 3-in-1 + 4.0.8 Conqueror. Happened every time I got close to Beantown Brewery! I had to use the coc console command to get into the interior cell in order to finish the Tapped Out quest.

Click to expand...

I also had to do this, hopefully Kinggath can narrow down this issue and see whats going on.

strange development. Havn't made any mod changes. I fast traveled to bean town exterior with tmm 1. And I was able to get near it but now i cant enter it. im also able to coc to the interior but not use the door.

Robert David Puig said:

strange development. Havn't made any mod changes. I fast traveled to bean town exterior with tmm 1. And I was able to get near it but now i cant enter it. im also able to coc to the interior but not use the door.

Click to expand...

The Suggestion is to post which Contest City Plan's you guys are using.

To view this content we will need your consent to set third party cookies.
For more detailed information, see our cookies page.

Accept third party cookies

RayBo said:

The Suggestion is to post which Contest City Plan's you guys are using.

To view this content we will need your consent to set third party cookies.
For more detailed information, see our cookies page.

Accept third party cookies

Click to expand...

Standard non-complex city plans from vanilla Sim Settlements.

Same configuration as Robert. No other third party SS Addons or city plans loaded.

same here i have non-complex city plans from sim settlements.
the issue is clearly with the code from 4.0.8 because if i fall back simsettlements 3-in-1 and conqueror the issue goes away.

Same or similar problems with a new survival test save + minimal load order (SS 3n1, Conq, WsFw, and a few supporting mods). Hard CTDs upon reaching most settlement boundaries with 4.0.8, better with 4.0.7a/b but still seems unstable. I'm about to go back to 4.0.6 tonight because I'm a damn masochist.

Seems the crash is coming from Oberland Station itself. Wonder if we can get @kinggath to comment on this?

So far I can't replicate any of this on the 4.0.8 version along with nearly 200 mods installed. Nothing in the code base related to City Plans was changed other than correcting the way beds are detected within the CP records - and that fires only when a plan is built, not when you approach a settlement.

Anytime there is crashing because of a specific cell you have stuff built in, whether manually, from a plot, or from a City Plan, the issue is almost always one of two things:

1. Most common, too many items for your system and load order to handle.

2. A particular item, either on a plot or from the City Plan is corrupt/missing its model file and crashing the game.

Since I recognize most of you here, I think you've long determined what your systems can handle, so my assumption is this is most likely an issue from a plot. So the next thing to try would be to disable all addon packs and see if that eliminates the issue. If yes, you should compare addon lists to see which you have in common to speed up narrowing it down.

Alright, given I was just about to post here as well, I've got the 3in1/conqueror, the two mega packs, ruined homes and gardens, intimate spaces and defense, wasteland venturers.
Looking over the papyrus log there were only errors from sim settlements (something involving furniture/the furniture store/and Perks) and wasteland imports, not sure if either of those mean anything.

Edit:
With everything disabled except for workshop framework and Sim settlements/conqueror, this CTD still occurred at both Oberland and Jamaica Plain.

I hope it's ok I chime in here, instead of opening a separate topic, since I believe my issue is related:

My game crashes trying to approach Revere Satellite Array with SS 3-in-1 and Conqueror 4.0.8 installed. I have a save file just steps before the crash reliably occurs.
Switching to 4.0.7a and 4.0.7b in my load order and loading up the same save file, I can successfully enter and clear Revere Satellite Array. Nothing else changed in the process: Same load order, same set of additional mods, same set of addon packs, and so on.
There are (to my knowledge) two settlements in the vicinity which might play a role, Finch Farm and County Crossing. Both I haven't touched or entered or even scouted out/discovered yet, so they should be pre-built to level 1.

My (uneducated) guess therefore is: There is something going on with 4.0.8 in the background which overwhelms my system, but my system can handle with 4.0.7, even though I'm not in a settlement at this point, just in the larger vicinity.

Some additional info that might or might not help:
I am one of the unfortunate people cursed with a rather unstable system when it comes to city plans, so I have developed a personal set of 'best practices' which work for me, like starting a new game with just a minimal set of mods, being really careful adding mods, regularly checking my saves in Fallrim Tools, rolling back whenever there are unattached script instances, sitting in interior cells to let scripts cool down, and so on. I only ever build one city plan in the Sanctuary-Red Rocket-Abernathy Triangle and leave the two others empty, avoid building too many plots in Starlight, stuff like that.
(Probably unrelated,) this particular playthrough is supposed to be a Children of Atom playthrough, so I'm using the CoA Faction Pack, started the game with Start Me Up in Parsons Creamery and went straight to Far Harbor (Conqueror not enabled at the start, I enabled it only later, before I unlocked the first workshop, sitting in an interior cell and waiting through the entire Conqueror pre-build process which takes about 3 hours in my system), stayed in FH for 30+ levels, I have one manually built Outpost there and three Vassals all with city plans at L3, and strangely enough didn't have a single crash in all this time which is quite unusual on my system. Only now, returning to the Commonwealth, I ran into this strange issue...

Again, I hope this helps somehow, and whatever is going on with 4.0.8 I'm sure you guys will figure it out eventually. And I will keep on playing whatever content you put out in the future, finding ways around my system's limitations where necessary, because I love this sh*t so much-

Keep the good stuff coming!

I just did another set of tests: I can reproduce my crash with SS 3-in-1 4.0.8 and Conqueror 4.0.7b loaded, it doesn't happen with SS 3-in-1 4.0.7a and Conqueror 4.0.8

Once again, hope this helps. If not, please ignore my wall of text above. I got carried away, it seems... ;-)

i reported this issue a week ago, and i can give you a save game to test if you want?

as i have put in other posts, i will get a ctd when i walk to red rocket from abernathy or from concorde with 4.0.8. if i go back to 4.0.7 there is no issue.

here's the odd thing - i have never built at red rocket in this game, so i cannot nuke the settlement, as there's nothing there.
nor can i simply wait around 15 minutes for *something* - presumably in 4.0.8 - to start/process/complete because i get an instant ctd.

if i revert to 4.0.7, the game works with no issue.

i don't believe that it could be a consequence of the triangle of death because my sanctuary is tiny and not a city plan, but it does have simsettlements plots and my abernathy has 16 settlers although it is a level 3 city plan, however, I'm not ruling it out because it could be that the combo of simsettlements plots in abernathy and sanctuary are causing the ctd - but i have no way to tell.

since 4.0.8 was released, i've had more ctd's than i've had in about 12 months. there is something very odd in that code base which is disagreeing with my game, but i've tried as much as i know, and cannot find anything tangible, which annoys me immensely because i want to know how to fix this. (It's how my mind is wired, i MUST know the answer ).

if you see this and can tell me how to get a save game to you - let me know.

Also using the SS 3-in-1 and getting crashes.

If people are having similar crashes I'm deducing that it's either a plot from a plot pack interfering with latest back-end (or just something with the code) as people are having better luck with the earlier build. I did another build and disabled Oberland Station from conqueror prebuild and didn't receive any crashes COCing there. Beantown was also crash-free. Other Settlements are free from crash as well.

We discovered the problem building plan, it's Caps General from SS. Will have it fixed for Friday's patch. Unfortunately, because this is an SCOL model, and not just a nif, I can't hotfix it now without risking save file corruption. So if any of you has this issue, either wait for the patch, or go back to 4.0.7 for now.

(Sorry Xbox players... unfortunately, Bethesda does not make it easy to keep multiple versions up.)

you're amazing. no, really.
in my sanctuary settlement, where i first encountered this, i have that model in a general store. i am going to guess that because of the proximity of red rocket to sanctuary, that is the reason i get a ctd in a vanilla and empty settlement? i am going to swap it out for any other model, then load with 4.0.8 and see if that stops the ctd.

kinggath said:

We discovered the problem building plan, it's Caps General from SS. Will have it fixed for Friday's patch. Unfortunately, because this is an SCOL model, and not just a nif, I can't hotfix it now without risking save file corruption. So if any of you has this issue, either wait for the patch, or go back to 4.0.7 for now.

(Sorry Xbox players... unfortunately, Bethesda does not make it easy to keep multiple versions up.)

Click to expand...

yea, legitimately you and your team are wonderful! Thank you!