i dont believe minute men or any other quest in particular causes the crash (at least the crash in monsignor area east of cambridge police station, which is the only one i've experienced so far). the other night i loaded a save at 7.5 hours that didnt crash, the next save was at 9 hours and did have the crash. i proceeding to play out the uncorrupted save for about 2 hours, did the same quests and still didnt crash. the only differences i made the second time around that i can think of is that i took a slightly different route to diamond city, and maybe some other minor things like not getting a haircut in diamond city.

from what i can tell it is something rather random that causes the crash, which would make sense seeing as a small minority of players are experiencing it. which is why i'll probably keep playing that old uncorrupted save and just be careful to make new saves often and check back on the crash area every now and then. unless of course there is a patch that gets released monday after the folks at bethesda's weekend is over. but honestly, the way things are looking i will probably be able to make up the 17 hours or so of gameplay i lost before there is a patch. whether or not i encounter the crash again, who knows, but that other guy said he restarted and has gone 30+ hours on his new save without getting the bug again so that gives me a measure of hope.

Also, if everyone comments on that Gamespot article, it might make them realise quite a few people are suffering from it. Don't go crazy on the people that are saying it's not game-breaking tho, they won't care either way. Saying thanks to the person who wrote the article would be great too as she asked Bethesda and is bringing a fair bit of attention here and other gaming outlets may report on it.

It's always good to know it could potentionally be a random number generator that causes the issue hahaa. Best of luck with your new save dude

So trying to get to that quest i'm crashing right around the Vault-Tec Regional HQ entrance. When doing the main quest I'll normally crash East of CIT ruins in the first Raider encampment. I'll try heading from the west this time...and nope still crashes. I'm gonna see if i can get high enough to see the character before i crash so i can move him to me.

First post, created an account just to post in this thread. I've been having this issue for quite some time now, and have managed to work around every quest that's taken me here so far through use of the console. Some solutions were simple, such as the ones listed in the OP of this thread. Just now, I finished Rockets' Red Glare, a quest that involves a seemingly unavoidable route directly through the Mosignor hellhole. Unlike other quests, setstage and movetoqt are not enough to fix this problem, due to several scripts that have to fire off. My solution to this problem was EXTREMELY janky. If you're going to try this, please hard save beforehand. Also, please note that this quest is towards the end of the Railroad quest line. As such, my workaround may contain spoilers.

Details for the workaround to complete Rockets' Red Glare:

1. Proceed with the quest as instructed, including the boarding of the Vertibird.

2. Once the Vertibird takes off, open the console and enter "coc santuaryExt" -- This will place you in Sanctuary, off of the Vertibird. (You can actually coc to basically any cell that isn't in the Hellhole or the Prydwen, but you want to be able to sleep and Sanctuary is easy mode)

3. Find a bed and sleep for two hours, which should be enough time for the Vertibird to reach its destination without you.

4. Open the console and enter "player.moveto 001A7A50" (credit to SeveralZombies for streamlining this step) to teleport to the Prydwen. Walk to the quest marker to complete the "Fly to the Prydwen" objective.

5. Enter the Prydwen, continue the quest as instructed, until you reach the objective "Escape the Prydwen".

6. Board the Vertibird and escape. Occasionally the Vertibird might ignore you and pretend you're not there, making this quest obnoxiously difficult to fix due to how many damn scripts get thrown out of whack. If this happens to you, continue to step 7. If the Vertibird takes off with you as expected, you no longer need this list.

7. Open the console and enter "setstage RR303 1100" to advance the objective to "Talk to Desdemona", followed by "movetoqt RR303" to teleport to her.

8. Desdemona will probably just keep repeating "Don't wait too long. The Brotherhood could be back here any minute." If this happens, open the console and enter "setstage RR303 1150". This will start the next quest "The Nuclear Option".

9. Desdemona should now talk to you and allow you to complete Rockets' Red Glare.

I apologize for how complicated and bizarre this workaround is, I was basically throwing crap at the console to see what would stick, and this managed to get me through it. I hope it works for others, because I tried about three hours of alternate solutions before I managed to find this one.

You are a serious god, thanks a lot for this. I've heard of somebody having a crash on this quest and I gave them some intructions (im not that far yet) and they said It's a very fiddly quest. So thanks again for the Workaround, I'll post this to OP with a link to this comment as you've already written intructions

Thanks again dude, Im sure other will really appreicate it!

So I've gotten a workaround to talk to Brother Thomas but after that I need a reference ID for Emogene to get her to me so i can continue. Anyone that has completed the quest can find her and get me that so i can see if this workaround...works...

Open console

Type "prid 000be957"

Type "moveto Player"

talk with him

???

Guys let's just wait for the patch. These workarounds are fine for basic stuff like going from A to B, but these quests tend to branch off based on conversations so by skipping them you we potentially lose out in content.

The workaround I used was only for Shadow of Steel. The video workarounds is a but lengthy, its easier to just use "setstage bos201 2" when ur flying.

But that is all I will use. Don't skip stuff.

maybe this information is irrelevant but i started a new save yesterday and played about 11 hours straight without any crashes (completed shadow of steel & hunter/hunted quests without problems.)

the only difference with my previous save is that i haven't started the quest for the minutemen (when freedom calls)

perhaps there's a bug in the minutemen quests?

I understand that dude and I'm personally waiting for a patch but others would rather progress in the story.

Thanks for posting! And yeah, some people have said that as well and it may be true but I think I remember some other people telling me they didn't get that far into the Minutemen.

Not only that, but using the console to skip quest stages is a great way to actually cause more problems. Scripts might not execute properly because you skipped the part where they were supposed to. This can screw up later quests and potentially get you stuck in them, with no way of progressing. I learned this the hard way in Skyrim.

Yeah dude I know, most of the quest Workarounds we use though just move you to the location or make a specific part of a quest become completed allowing you to continue. The ones that are more complex and findly, I've mentioned and said a save is highly advisable. A few people have said they've completed the game with the Workarounds too. Cheers for advice tho, hopefully nobody will get into that mess.

Anyway, I'm off to bed now but should be back tomorrow

Just got this bug too. I'm not really into using a workaround since i would like to actually explore the area too. Let's hope they release a patch soon

Hallow people, i got this bug too! How fun! Anyhow, as soon as i got time i will make a precise map on where i crash with a scheme on the pipboy map, so we can eventually compare it or keep it as "gathered info". Anyhow, right now I can't tell you which quests I did yet, but as soon as I can imma make a list of them. Hoping for a soon fix!

this thread should almost be pinned at this point

This bug also should be fixed at this point. But it isn't

Maybe they're all on holiday. Frontier did something similar immediately after releasing Elite Dangerous... Two weeks off, the entire development staff.

the longer they wait, the more people will catch up to the main story quest that takes you to the areas around monsignor plaza and complain of this issue. bethseda is going to have a lot more people discussing this issue realllllll soon.....

Well, lucky for us this news is starting to spread like wild fire.

http://www.destructoid.com/yes-the-first-game-breaking-fallout-4-bug-has-been-found-321108.phtml

http://www.vg247.com/2015/11/16/first-game-breaking-bug-in-fallout-4-discovered

Bethesda will be [censored]ting themselves pretty soon.

well this is literally most all i have left to do in the game. i finished it one time for one of the factions. the other factions use this area heavily and require skipping / completing heavily.

The problem here is that the only real option is to start over since there is a huge possibility that "fixing this area" will NOT fix your saved game, which is what happened in many other patches in different bethesda games.

The hope is not that the area will be fixed but also that the saved games can be salvaged in some form, like a console command to move / reset / kill something specific that will fix the area even if that thing stays bad.

It is all woven together. Either doing something or the lack of doing something triggers the issue:

The entire game can be summarized by 2 states:

walking to an area after X quests done, Y events triggered (random or not)

NOT walking to an area after X quests done, Y events triggered (random or not)

From there you can get specific with where you're moving and what quests you have / haven't done.

I don't think randomness applies, because that randomness would still trigger due to something, and trigger something that was broken. Thus even randomness would predictably have the same outcome: roll a dice 1-100000 and if it lands 66666 you get the bug. Randomness occurs, but that outcome is determined.

For example I saw the UFO crash event and it looked like it crashed at the plaza. Was that triggered? Randomly? Was that a determining factor in the bug? I ran to around where I saw it land and it wasn't there.

After 2 days played, and discovering the bug near the **60 hour mark** because I happened to avoid that area, it is hard for me to focus on fixing this or testing or starting over (especially with other games coming out these next few weeks). It would be a fairly repeatable provable thing to start a new game and just run directly to this crash area to see that it's working.

I still contend that there are 2 or more issue spots on top of each other because after nuclear option parts of cambridge that would crash no longer crash.

Another article:
http://gamerant.com/fallout-4-game-breaking-bug-802/

http://www.gamepur.com/news/21198-fallout-4-has-game-breaking-bug-monsignor-plaza-settlement-quest-no-fix-yet.html

http://twinfinite.net/2015/11/fallout-4-game-breaking-bug-discovered/

LMFAO@the comments.

It's funny how the people without the bug feel the need to argue that the bug is not game breaking.

TBH, when it's fixed I probably will restart now. Not because this bug might not resolve my issue, but because my frustration have contaminated my save...

Wow these articles are up everywhere now, that's pretty cooool. You've also got https://www.youtube.com/watch?v=WcU7-CWy4Ys but I'm sure that you've seen that.

So...by a random chance....could Bethesda finally get into their chair and fix this? We don't need a huge patch that adds Dog Power Armor, just the fix so people can go back playing the game...

Maybe it's not quest related. I think it could be some random encouter. That's why not everybody get it and sometimes it's occures in other area of the map. After reinstaling on ps4 game still crush but the area seems smaller.

Edit: 12 hours earlier save seems good

Edit2: Area didn't get smaller. It's just moved closer to Mosignor Plaza :/