W_nker

Not even going to question it, just gunna leave this hanging.

silly brits and your mastvrbatory slang

Yeah. I've read (on this thread no less) that there MIGHT be a correlation with having done quite a few minute men quests (which I have) and the crash occuring. But i've also read that people have done alot of MM stuff and haven't crashed.....this bug really has me stumped.

why are people under the impression once a fix is applied, people will need to restart their games? i can't see a large majority of people restarting their game because a game-breaking fix/patch was not retroactive.

i don't know, people were saying spooky things earlier like how we are all gonna have to restart. i have no experience with developing video games so i have no idea if its a possibility or not.

not to brag or anything but i did once open Visual Studio C++.

Is it only speculation or are there any actually evidence that having done few/many Minutemen quests and the seeing the UFO might cause this crash? I'd done few Minutemen quests, but I did visit the UFO tho.

i don't believe anyone has pinpointed what is causing the crashes. i had not seen (or heard) of a ufo up until reading this thread and i most definitely was crashing around the monsignor plaza area.

speculation. most evidence, if you can call going back and replaying from a working save "evidence", has yet to show that any quest in particular is the cause.

Yeah, as others said we've have a lot of speculation. People have even gone from quest to quest. I personally haven't seen the ufo and have done quite a few Minutemen quests.

I have some really basic like reaaaaaly basic programation skills(made a tic tactics toe and a couple other games like that in java) and even for a small game like that there can be a tons of bugs and glitch if you make a slight mistake or forget something when you write your code so I don't even imagine how tough it is to program a game with such a massive scale like fallout or ES.

One thing I can say though is that since I did those in my it support class I don't complain as much when games have bugs considering how even the smallest games don't need a lot to be buggy.

That was a very heartfelt speech, my eyes aren't watering, it's just a scratch.

Can everybody please stop crediting K_Lou? He is the cancer of this thread and his ego shall only increase, I would ban him so hard from every forum in existence if I could.

Nah but in seriousness, what you did was really helpful and lots of us appreciate it. I was going to add more refrences of people going through quests but there is sooo mannny postsss.

WELL IF YA EVER MAKE IT BIG TIME AND NEED A WEBDEV WITH A TERRIBLE SENSE OF HUMOUR, I AM YOUR MAN.

getting in at the ground level, i am. Seriously tho, I do know how annoying a single error is, serious kudos to games programmers - yo da real MVP

Thanks for the answers guys!

Still can't decide if I want to use the workarounds or keep waiting for a patch... Afraid of missing stuff, but using the workarounds still let you explore the inside of the buildings of the quests so maybe workarounds would be fine. Getting really frustrating this!

It's bethesda, they make huge open world games that involve tons of different scripts and [censored], i expect there to be bugs. it just would have been nice if they started taking notice last week. at least we know they are looking into it now, although i am still not sure if i should be continuing my old crash save tonight or continuing my restart save. oh well.

so far, i've only used a workaround for hunted/hunter since it teleports you inside the building and you still have to fight from the beginning to end of the level. I am getting to the point where i may need to use work arounds for a lot more quest but i am hoping they do something before then...

only Todd can ban me from this hell-scape.

Just tried loading an old save (6h game time instead of 42h) and was able to reach the Plaza. That does'nt help me tho... xD

Almost afraid of playing more, if this crash forces us to start over.

I can't wait for the epic battle between K_Lou and Todd Howard

The only way I can see this requiring a restart is if it turns out that the error is being caused by an orphaned script, because cleaning scripts out of saves is a nightmare and as any of us who have played a Creation/Gamebryo game before know, scripts get baked into your save.

That said, a lot of people have concerns about using the console to workaround this error. Those concerns are very valid, but for those that are worried that they might miss out on branching quests due to skipped dialogue, this is the way I see it: we know the Creation Kit is due out sometime early next year, and we know Bethesda is keeping an eye on this bug. So best case scenario it gets fixed this week, and worst case scenario it gets fixed in 2016. In the meantime, however, we have no idea what causes this bug. The only thing we do know is that it exists in 100% of copies of this game. It's not tied to any particular platform or patch. It's triggered by an in-game event that we have not yet identified, and until we identify it there is no way to warn people or advise them on how to avoid it.

That's unfortunate because the area this bug affects is used in every single faction main quest line with the exception of the Minutemen. The Brotherhood will send you through there during Shadow of Steel, our friend in the glowing sea will send you there during Hunter/Hunted, and the Railroad will send you there for Boston After Dark and once again for Rockets' Red Glare. For those of you who think this is not a gamebreaking bug, what is necessary for a bug to be considered gamebreaking? This impedes the main quest line entirely on consoles, and is 100% replicable. If you're unfortunate enough to have triggered the mystery event that causes this issue, you're screwed unless you're willing to lose hours of gameplay reverting to an old save and still be at risk of encountering the error because we don't know what causes it. If you don't have this error, that does not mean you will never have it--it only means that you have been fortunate enough to not stumble on the trigger yet.

So from my perspective, my options are this:

1. Wait for Bethesda to fix the glitch. Doing this means I cannot proceed in the storyline AT ALL, putting me at heightened risk of finding spoilers online, and not addressing the possibility that the bug is caused by an orphaned script and will require a new save.
2. Use console codes to work around the glitch. Doing this allows me to continue the storyline and finish it, at the risk of missing out on sidequests due to skipping quest events and dialogue options.

I don't know about you, but I'd rather miss out on side quests than main quests. And the argument could be made that "oh, if you're patient you can get both, maybe" but I can make the same argument that if we did miss out on sidequests, we can trigger them with the console anyway. The simple fact of the matter is that everyone's copy of the game contains this exact error, regardless of whether or not that player has triggered it in their save. This is not one of those rare problems that some people will have and some people will not. Everything we do in this thread, every amount of information we compile, and every workaround we detail, is going to help Bethesda pin down this bug and squash it, and allow those fortunate to have a PC copy of the game to workaround the bug if they so desire.

Just my two cents, guys. Yes, this svcks. And yes, a bug like this should have been caught by QA before the game shipped. It's a damn shame something as volatile as this made it into the release version of the game. But this is the Creation engine, and honestly, I fully expected something like this to happen. I've spent almost as many hours modding Skyrim as I have playing it and I can tell you horror stories about the tangled scripts and fragile quest lines over there. The Creation engine is incredibly complex. It's also incredibly outdated, which is hopefully something Bethesda plans on working on before the next Elder Scrolls game.

Spoilers below potentially;

New symptom following workaround. Using TCL to get onto the Prydwen makes it so Companions will not follow you. Talking to them always shows the "Follow" command. Fast Traveling while they're in your party causes them to disappear entirely, to the point where not even placeatme or player.moveto will not actually put you or them near one another. Unsure what to do, but I'd recommend avoiding turning off collision in any workarounds. For the Rocket's Red Glare situation;

1) Get on the Vertibird at Cambridge Police Station

2) Use console command "coc sanctuaryExt" (or any other coc command) as soon as it takes off, repeatedly, until you appear where you meant to go.

3) Wait for two hours by sitting or sleeping.

4) Use console command "player.moveto 001a7a50" to teleport to the deck of the Prydwen.

5) Move to the quest marker to complete the objective "Fly to the Prydwen" and continue the mission as normal.

6) Once the objective changes to "Escape the Prydwen", get back on the Vertibird at the quest marker. If it doesn't take off, use "setstage RR303 1100" to take off.

7) If the Vertibird still doesn't move, use "movetoqt RR303" to teleport to Desdemona and wait. Eventually her lines will change and you'll be able to speak to her normally, initiating "The Nuclear Option". If she doesn't, use "setstage RR303 1150" to complete the quest.

Thanks to Northfield for the last two steps

This is pretty much what's going on, really detailed as well. It's worth noting a lot of people aren't getting this bug at all and have completed the game but there must be some sort of trigger unless Bethesda played Russian Roulette with us as this issue has been seen on all platforms. About the Workarounds, I've heard a lot of people that say they could hurt the game and some of them potentially could but I have said they are fiddly and to save beforehand whilst some are straightforward and simply require teleporting to the location or completing a objective.

Also, you didn't even have to edit. I edit my posts that have 4 words in them^{im so bad at life}. Dayumm.

This is aweeesome. I'm guessing this is the full intructions for Red Glares' Situation? Thanks for this bud !

Unfortunately for Todd, lies can only hurt a person on the inside.