Bethesda - https://bethesda.net/#en/events/game/thanks-and-updates/2015/11/19/53

Yesterday - 19th November

I think it'll be soon, if not next week then soon. They've had ours saves for a while now and will probably be working on the bigger bugs first so I'l expect soon

The patch details will also be revealed closer to the date so we should know soon

This seems plausible, in a manner of speaking. It would have to be an element that is random yet unchanging once placed. For instance, I've saved/reloaded games in the same spot and mines that were right in front of me were no longer there when I loaded. That's an example of something it most likely cannot be. So it would have to be a random element that's consistent in your game world despite saves/reloads; as in, possibly a pre-defined variable from either the VERY START of the game or a trigger. From the data at hand, if there is a trigger, it's a VERY early one, because of the huge disparity in time occurrences and even locations.

I personally don't know how objects and items are spawned/determined, or if they're all consistent across every person's game (as in, will Stimpak A always be on Desk A in a building, and it just has to "load in"? Or is it [Consumable] Item A-Z can be on [Area] Desk/Floor/Shelf A-Z and it's already loaded/waiting to be picked up?). I don't believe it applies to monsters/enemies because those can spawn as different things depending on your difficulty.

In any case, if this bug isn't fixed in the coming week, I hope they at least address what they've discovered regarding it. Not knowing is the real frustration for me. Just because, I like to solve problems xD.

In essence, I feel like those that sent save-game files should have provided the tools for them to find the bug. Cross-referencing the "bad" data/variables to see commonalities then contrasting with "good" saves should identify the problem...at least, it seems simple (now) in my mind. Without any knowledge in this area, of course.

In any case, I just hope it's fixed, because this is my first Fallout game, and I'd hate for it to fall out of favor in my eyes.

just finished trinity tower, fast travelled from top, it was fine.

got to the bottom and unlocked strong, was fine too.

maybe its the order you do things?

this time i got valentine then cait, then did trinity and it worked fine.

my bugged game i cleared trinity with piper, then got cait, then got valentine. Not sure at which point it messed up though. Just know for sure it's after trinity and before valentine.

maybe if you do trinity before getting cait or valentine it messes up?

As far as the mines go, thats a glitch. If you set off a mine and then reload a save in the same area, the mine doesn't get put back till you leave and then come back. It's how they are cutting down on loadtimes with saves. A lot of stuff doesn't get saved/loaded so that quicksaves/loads in one area are extremely quick. The problem is, stuff like the mines happens. You can also see this if you quickload at the right time after making enimies hostile (they will still be hostile after the load, even if you saved before making them hostile) and if you are standing in radiation (if you save outside of radiation, then run in it and quickload, when the game first loads up you will take some radiation damage till the game realizes you are not in it anymore).

In me experimenting with the only random encounter I personally know I have had (the one related to a certain blaster), I got super lucky and had a save right before it. I found that loading that save, and then going anywhere (even fast traveling) with in a certain radius of where I was still triggered the event. I found that if I loaded the save and fast traveled outside of that radius, the event wouldn't trigger, but would imminently after I got back with in it. This is on par with the crashing behavior. If it is a random event, the game has one triggered to go off at that location, and as soon as you get close enough, it triggers and crashes to desktop. The event most likely has more the one place it can trigger and is only causing the crash triggering in that one location.

If we had away to trigger event manually someone with a clean save can just can stand there and trigger them one by one, but I don't think we do.

Originally Posted http://www.gamesas.com/topic/1556922-1st-fallout-4-patch-to-release-next-week/by mark5917. Putting it here because someone accidentally posted there instead of here when I linked there.

At the moment, we have no idea whether it fixes this crash, if it doesn't though then I would expect a patch soon does.

You can find the original post by Bethesda https://bethesda.net/#en/events/game/thanks-and-updates/2015/11/19/53

______________________________________________________________________________________________________________________

>>> Bethesda has said to expect the first beta patch for Fallout 4 to arrive next week. <<<

Thank you! We can't say it enough- thank you for the amazing support you've given us. We're incredibly blessed to have so many incredible fans.

You've made Fallout 4 not just our largest game launch ever, but one of the industry’s. It's beyond anything we hoped for.

According to the company, it is “hard at work addressing the top issues,” and the beta patch will be released first on Steam.

“The freedom in our games can lead to unintentional consequences that are sometimes bad, when the game combines too many unexpected elements at once.”

Given the scale and complexity of the systems at work, especially when allowing you to build your own settlements,

and we’d like to thank our amazing QA staff who worked as hard as anyone to break the game so we could fix it during development.

But a hundred testers will never replicate the many millions playing the game now, and we’re hard at work addressing the top issues.

After the beta patch is released on Steam, it will be followed by full release on PC, then release on the consoles.

Test patches have been released for previous Bethesda titles, which the company said has “worked well” for it in the past as it allows it to “get more fixes out faster.”

“Expect to see more updates, that are smaller and more frequent, than a few big ones,” said Bethesda.

This allows us to make sure each fix is working right, as any change can have unintentional side effects in a game this huge.

“We expect the first beta patch to be up next week.”

-------------

If you have feedback or issues to let us know about, contact our support staff.

Thanks again for everything. We look forward to our continued journeys together.

^■BETHESDA

Game Studios

While I'm not getting the crashing myself, I discovered last night that the affected area seems to be where [some?] objects that fall out of the map get sent [sometimes?].

Upon loading a save, the terrain didn't load properly before giving me control, and I fell through the map.

After falling for a few seconds, I got teleported across the map to just outside Greentech Genetics. (seems to be the exact center of the map?)

Is it possible that some NPCs or objects are erroneously being sent here, and that's what's causing the crash for people?

I haven't been able to reproduce this (either by loading again or manually with tcl), but I remember seeing this thread and figured this was too much of a coincidence not to mention.

My quicksave was standing on top of Fort Hagen right next to the roof access door, and I loaded after dieing in one of the rooms immediately just inside.

Here's my workaround for the quest Kidnapping from Greentop Nursery.

1. Type "movetoqt MinRecruit02" in the console command.

2. Talk to the kidnap NPC.

3. Retype "movetoqt MinRecruit02" to travel back to Greentop Nuresury settlement.

Note: I don't know if the order of the quest will change the i.d number. If it doesn't work try other number. ex. "movetoqt MinRecruit03", "movetoqt MinRecruit04"....

OK,

Posting an update. I took my save that was "OK" and climbed back to the exact same place in Trinity Tower where I was in the crashing save. Teleported to the problem area from there just fine. I guess it must be a totally random thing. That's too bad because that means even if you restart you will never know if you hit the bug unless you keep checking after every mission.

I have a similar crash just like this one but in a different area. Its just south of the other Monsignor Plaza crash point. It starts at the amphitheater, goes east to Vault 114 which I've been to before and to the Comic store, then it starts at the west at Back Street Apparel. Not sure how far south it goes but not too much farther south than the comic book store. I can also go to Monsignor Plaza just fine with no problems but I cant go the the comic store or back street apparel for quests which is slightly irritating.

I've just tested this to see if it helps mine at all, I hadn't even started the quest and after getting radded up from the water, it hasn't made a difference in mine

Here's a weird thought that might've been discussed already; steam updates.

Most of us probably started fallout straight up without any ini tweaks, or did xyz before startinga new game. Now if steam does what steam sometimes does, it'll see ini files as "not verified" and would replace them and one might not even notice.

Load up save, different ini then before, problem.

Could be an issue there, probably not though as most ini tweaks just handle performance/mouse. In any case the patch is coming so that'll answer a few things i hope

I have the bug and I haven't touched any ini files.

On a new game. I've completed Out of Time and When Freedom Calls. In progress are Fire Support (BoS radio signal), The First Step, Jewel of the Commonwealth, and under Misc. I have Bring Jet to Mama Murphy and Talk to Sturges.

Decided to go for a hike. I can get to the area around Kendall Hospital, went past the CIT Ruins and over the bridge with the USS Riptide. No problems.

I decided to head SW from D.B. Technical High School. Got across the overpass, and CTD going around the building.

Frustratingly, I also had the UFO go screaming by overhead to crash just as I was leaving Sanctuary to go to Lexington during Out of Time.

Dumb.

Yeah i figured it would be something that's not the cause. Worth an idea though.

Welp, starting fresh. Fresh download, will only change settings/graphics options and nothing else. Will set everything ready so that when i hit new game i won't have to change one single thing. Will save only with basic saving, no quicksave and no autosave.

Have to see if i run into this then, atleast will have a good base for it if nothing else and it's fun to start fresh

Hi there!

Thank you for this thread.

I also get an instant crash in the Monsignor area, specifically if i COC to the cell greenetechext. Fasttravelling to the Cambridge Crater works and only crashes if I get near the red Dinner near Monsignor Mall.

Revertworld works but sets back everything :/

I have noticed the crashes after the Boston in the Dark quest.

Following quests are already finished:

• Silver Shroud
• Reunions / Dangerous Minds (done them yesterday because i cannot proceed with the Boston in the Dark quest)
• rescued Strong and Rex from the trinity tower, and I have also been at the top
• Kidnapping from Greenetop Settlement crashed also a few times but worked suddenly.

Really weird. Re-installed fallout, no tweaks, all pure 100% original. Same as before when i started. But this time I'm barely 5 minutes in and i got a CTD when talking to the vault-tec rep. Then another when you're at the babycrib. This is all pre-vault even.

Now i'm getting CTDs all over the place and everything is like it was when i played for over 30h without a CTD.

Awesome, a patch is coming. Now all we have to complain about is why it's not coming out before the weekend...

Oh, and can Gstaff or someone somewhere tell us what the issue was? If its something I can avoid until the patch comes, then I'll just do that. But right now I cant play it at all for fear of triggering it after one hour only to have it surface after 50.

Yeah. I'm a bit boned without one. Getting CTD the moment i pick up a pipboy for the first time, without fault every time at either load in, while picking up or right after.

No such thing before and took hours before i even ran to the basic ctd problem O.o

Worst case scenario is that somehow, somewhere, it all starts on new game from the get go and then appears at some random place.

The problem occurs with the ‘Weathervane: Broken Monorail’ mission on XBox One.

Reproduction steps:

* go to Haymarket hall, take the leftside door all the way to the back and open the expert lock to the Financial District.

* the area you enter is now glitching, with partially rendered views, obviously not right

* now go back inside Haymarket Hall, up the stairs and take the elevator to the eight floor, there take the left door, shoot the turret, go right, shoot the machine gun turret and take the left door outside to haymarket hall roof

* again a glitched environment (whereas you should be on the roof), you will now fall down the glitching floor to your inevitable death

Even loading back multiple save games and now not opening the locked door in the back gives me the glitch issue.

Good that we will finaly get patch. Shame that it will show on console later.

I'm just wondering (propably like all of You) what is the cause for that bug and will it fix are savefiles or we'll have to start all over.

If someone from pc can give the answer to the second question when the patch will be available I be very grateful.

Posting this here too as some people might only check this thread;

New driver available. Loaded new geforce driver via geforce experience, express install, tried loading the previously problematic save(which crashed to desktop when fast travelling etc), now there's no issue. Tried running around the problem area(BoS), fast travelling and all good.

No idea if the stars aligned, or if my computer decided that i've suffered enough, but worked for me so might work for other geforcer peeps out there.

Also added a minor amount of performance and my GTX runs cooler now. Added +.

I know this isn't a fix-all thing, but if it helps even some then, step closer.

I'm having the same issue on PS4. I can't do a few quests that take place in the area now including shadow of steel which I'd really like to do because the brotherhood of steel is awesome.

I'm at work right now, can anyone else confirm this? Or is this retribution for my behaviour the other day?

Granted there is indeed a new driver update. I didn't think it would fix this issue though, unless both P4 and XBOX use nvidia.

Have to say again, this just fixed it for me. Probably won't affect xbox/ps4 and it could very well be that i had thesame issues for different reasons. But who knows, better to suggest then sorry