Yup. Same areas, same crash. Still unplayable. It's possible that they fixed Monsignor but I've had this problem in at least four other places on the map and couldn't even get close to Monsignor.
Yup. Same areas, same crash. Still unplayable. It's possible that they fixed Monsignor but I've had this problem in at least four other places on the map and couldn't even get close to Monsignor.
That svcks dude. It sounds like the beta patch fixes the crash around Monsignor and you aren't just having that though so it sounds like a different bug. You can always try creating a thread/adding to bug report and the such but I dunno what else to suggest. It was pretty hard to get this bug known as you can probably tell by the number of pages and the OP :/
All the best dude, hope it gets fixed for you asap.
edit: patch works for my save game. It's beeeen a long time since I played as him ahah
I sure hope the patch doesn't solely fix the crash at Monsignor Plaza, as I have only gotten crashes NEAR Monsignor Plaza when nearing the Greentech Genetics building. Fingers crossed.
I remember a workaround that had to coc to Greentech so I think thats in the area?
Hello, I have the same problem and the beta-Patch has not resolved it.
I going back to a previous save, that not crash in the area (in my case Raildroad HQ).
And i found the trigger quest.... "Mercer Safehouse" from PAM....
when i travel in this area...game crash to Desktop.
(befor i get the quest...no Problem with this type of crashes.....)
To solved this, i have make the quest...teleport PAM with console to me (grid 000508ec) and finish the quest....
but when i fast Travel to railroad HQ...the game crashing, too......
PS: sorry for my englisch, i am no native speaker
So far so good, strolled through the crash zone, disintegrated some raiders, drank a nuka-cola.
I expect nothing less from you Decoy Octopus, I expect nothing less
No idea, I didn't even know it was fixed until I got a ton of emails hahah
Really sorry to hear this dude, thanks for posting though as somebody else may have the problem and maybe Bethesda will lurk here at somepoint
Hope its fixed for you soon dude!
Hi.
Lastnight i installed the beta patch and go to the Faneuil Hall, to do two missions (Rescue a citizen and The Gilded Grasshopper) i didn't have any problem to do the missions, i entered to the building completed the Rescue and then go to the roof to take the gilded grasshopper but when the missions ask for "Go to the somebody grave" I left the building and turn to the right and the game crashed.
So i load another save and then turn to the left and go to the market location and the game didn't crashed. I attached a image to explain better the crashed zone:
i767. photobucket. com/albums/xx319/canojuancho/hall.jpg
the blue square is the place to go, the red circle the zone that crashed and the green circle the safe zone that didn't crashed
Anticipated the patch in the same enthusiasm I had with the launch, and it doesn't fix the crash. What a huge let down.
I first encountered the crash with "the lost patrol" quest (around 5 hours in). Just go near the area and the game crash. I tried to skip the quest to do other, and it seemed working for a while, until around 12 hours in, after I did a few more Brotherhood quest. Now I can't even load the old file without crashing.
Updated the new beta, and it doesn't do [censored]. Same crash, etc..
Sorry about my English, not my first tongue.
Sorry to hear this guys, I've heard of a few other people who said this hasen't fixed it for them - I'm unsure if they're experiencing the exact same bug as we were though. I loaded up my save and ran straight into the area where it usually crashed and it didn't and the others haven't reported back saying its crashing again so not sure what to suggest.
I hope it's fixed for you in future patches, svcks to hear you still can't play the game properly.
I suppose I can share my Fallout experience here as well. First of all, I'm not a native speaker, so blame any grammar mistakes on that.
Now, I'm a pretty hardcoe TES and Fallout fan, I know most of the lore and played most games of the franchise. To be bluntly honest with you: I pirate most games. If I want to play a Call of Duty or an Assassins creed, it's the Arrrrr Ye Matey! for me. But Bethesda's games simply have this charm around them, and I usually actually buy them (retail version). For Fallout 4, I even bought an entirely new gaming rig, though I'm on a budget, I topped the minimum requirements everywhere and reach the recommended specs here and there. So don't ask if my PC can handle it, or if I have the latest drivers for everything because yes I do.
In short, I spend a [censored]load of money just to play Bethesda's "Most ambitious game ever". So, eager as I was, I installed the game through steam (took me forever for some reason). And I opened the launcher to find that the settings are set for the lowest quality. I didn't need or expect Ultra settings, but it could be high or at the very least medium for a new rig, right? But no, low settings for me it seems. A bit disappointed I decided to play it anyway, and then it happened: CTD. Not even an error message, just black screen for two seconds and it didn't launch. Now in all honesty, this is a common thing for pirated games, I thought, but it seems these issues can be found in the retail versions too. But, experienced googler as I am, I found a solution: I had to open it in borderless windowed mode, and tweak for the resolution in the .ini files. But once more: CTD. And guess what? While googling on this issue I found someone else online stating that the automatic hardware detection also set the game on low settings for him, while he even exceeded the recommended specs.
Anyway, it took me a couple hours until I lost my mind and started pressing the launch button over and over again, CTD's over and over again. Until the eleventh try. Suddenly, it worked... sort of. It didn't play the game, but instead launched the launcher again. both the Fallout4.exe file, the steam button, the Fallout4launcher.exe file and the play button in the launcher, just started the launcher instead of the game. So I was stuck in an infinte loop there. Losing hope, I went to the Arrrrr Ye Matey! and downloaded the 1.1.30 update, which for some reason didn't show in my steam. I tested it again with this update and apparently the game did launch, every ten tries or so. So it wasn't perfect, but I could start playing whitout too much ingame issues. yay. I had spent hours tweaking .ini files, searching the internet and testing the game, I even had to illegally download a patch to get it in a sort af working condition.
Though dissapointed because of the bad graphics, I played happily for a while. Until I decided to do the Curtain Call mission. Once I enter Trinity tower, the game crashes. I usually got five seconds in combat there before the same ctd happened. Waiting for an official patch, I played the rest of the game. Until the freedom trail quest. The same thing happened (and keeps happening) around the old corner bookstore. It won't allow me to find the railroad, and it wont allow me to do the main quest. (please don't spoil where the railroad is and say it's a 'workaround', I want to actually play the game properly).
So once more I set out in the murky waters one calls Google, and found this thread right here. The crash I endured was described here perfectly, so I guessed it was the same issue. As I read, it seemed a lot of people had this bug in different places, the most common place being Monsignor Plaza. The new beta seems to solve this, but not the crashes in all the other areas. Actually, it made everything worse for me. After the beta was installed (v1.2.33) I received the application load error 3:0000065432, my faithfull companion google told me it had to do something with deepguard from F-secure or something, a program I'm not using.
After backing up my saves, I deleted everything I had from fallout 4: the gamedir, the backup .ini and the pirated update. And I downloaded it again, but this time straight from the Arrrr!, including the 1.2.33 beta patch. Surprisingly, the game now actually launches on the first try, rather than the eleventh or so. The CTD in certain areas remain, however, and the game remains entirely unplayable.
Quick recap: I've had every error you can think of, every issue possible and solved most of them. The pirated version also seems far more cleaner and more stable than the actuall retail and steam versions(also less stuttering and higher quality it appears), but the gamebreaking crashes persist over and over again.
So, I am out of options here. no patch works, no .ini tweak worked, no illegall version does anything else than crashing in these few spots. And my pipboy is full with quests I simply cant do because of this. Fallout 4 is just a postapocalyptic version of the sims right now, where I can go shopping in Diamond city, build a house and that's it. I can start wandering the commonwealth though but it's with the constant danger of facing an even larger threat than the Deathclaw: the CTD.
Sorry for the long post, I needed to vent a bit. This is not how I imagined "the most ambitious game ever". I also doubt I'll ever buy any game from any developer again, what happened with: "buy, install, play"?
Oh and a quick edit: I did buy the game, to actually support Bethesda for the amazing work they are doing (not so sure about that anymore though). So don't respond to me saying that I probably didn't buy it and that I'm lying and all that because that is not the case. if there is a way to prove that I have the disc right here, please say so. I wasn't planning to use the site that was censored everywhere in my post, but I had had to, just to start playing this game.
Hi dude,
I just read through all that and that really hit me, I know what its like to have no money but look forward to a game so much to upgrade everything and I know the feeling of constant crashes and knowing you can't play the game without the worries of a CTD. Theres a few games where it would crash every 15-20 minutes and just knowing it could or couldn't happen just seriously svcked and I raged like a [censored] ahaha. I've heard of the CTD's in other areas but never looked into it unfortunately and seeing as tons of people have played the game saying its the least buggiest Bethesda game yet, I dunno what to suggest. It does sound like something on your end though, I haven't heard of that many bugs that quick. I know you made sure you reach min but sometimes that isn't always enough; hardware is weird (I'm not certain on that though). My personal recommendation is to just keep asking about it, tweet Pete Hines a link to that comment (he replies to a suprusing amount of tweets even if he never answers technical questions often), create a thread, post on Reddit, phone Bethesda, send feedback and the such. I got the ball rolling on this thread by spamming Reddit;)
All the best, hope you can get the game working dude.
I actually think your english is better then mine btw hahaa
edit: Turns out Bethesda is actually asking for saves related to CTDs as you can see http://www.gamesas.com/topic/1559956-monsignor-plaza-bug/?p=24588290so hopefully they'll be some future patches.
Ya, I was too excited about this game, not only this is the first game I ever paid full price for (normally I wait 1-2 year until price drops), I bought 3 copies, 2 of which I gifted my friends.
Damn you Bethesda
Thank you again for all the help Joe! Happy to see this fixed!
No problem dude! Hope you enjoy the rest of the game
Installed the beta as soon as I saw this yesterday and took 5 min just running to the closest area that I experience crashes. Got some minor image lag but no crash.
Was really thrilled and today when I got back at it I played for a couple of minutes, and then CTD.
What I noticed were that I got less frequent ctd's. Instead I got some lag/freezes in places I previous would have experience ctd, but I still have a lot of ctd's
When I restart the game and go in the same direction the ctd occurs in the same area. Sometimes I can get through if I take a detour around the area.
I probably should have spend more points for Luck. Hey, maybe that's what causes the bugs? How cool would it be if these bugs are supposed to be there to torment players with a low Luck stat.
Anyway, I send a message to customer support, let's hope they can fix this.
The beta patch fixed the problem for me, luckily.
Post Beta Update 1.2.33 I am still crashing when I approach the area around County Crossing.
I have identified a saved game taken about an hour before the being of the crash.
Interestingly enough I was building on the settlement in that save game and my quest list is the same between the two; thus I have the suspicion that I did something to the settlement.
The new beta patch solved the crashes for me. Hopefully I can finish the game now. Also updated to Windows 10 1511 and AMD Crimson Drivers which also gave me better performance overall. Updating all this also gave me a very slightly annoying flickering on the radar. Since I did it all at once I don't know what caused it.
Related to my ongoing bug; I wanted to investigate further (and see if I can get back to playing).
Anyone know if there is a trick I can use to perhaps reset a cell or scrap everything in my suspect settlement remotely (as I cannot travel there)?