Jump to content

Monsignor Plaza, Ticonderoga, game freeze CTD


Perraine

Recommended Posts

I'm hoping you guys may be able to track down the cause of this bug. It seems that after a certain point in your characters progression, the area around Monsignor Plaza, Ticonderoga Ruins becomes an instant game crash whenever you go near the area.

 

It was supposedly fixed in a patch some time ago, but I have just encountered this bug. As that area is used for several very important main, and side quests, so it it extremely game breaking.

 

I was able to complete the first Railroad Mission = escort H2-22 (or whatever the Synth is called) to Ticonderoga, but now that my game has progressed significantly I can no longer go near the area.

 

It seems to only effect the outdoor cells, as using the "movetoQT ,quest id> console command on PC and if it's an indoor area (say Ticonderoga) the game plays fine. You can also "view" the area from rooftops some distance away, but whether it's by fast traveling or walking/running, as soon as you get near that area of the map, regardless of which direction you approach from,  the game will freeze and crash.

Link to comment
Share on other sites

Just an update, I can't go near Greenwich Genetics either, so that whole area = hard drive hammering for 5 mins, then zero HDD activity, and a few seconds later, the " xxxx has stopped responding" windows popup. Whether it's by fast travel or walking in makes no difference ...

 

This issue WAS NOT FIXED in the FO4 1.2 patch, despite Bugthesda's claim it was. I understand that most people are probably way past this point in game progression by now, but for new players, or new playthrough's this still seems to be an issue. I really hope you guys can figure out why it's happening.

Link to comment
Share on other sites

It's problematic to claim that it was not fixed in the 1.2 patch when we actually don't know what they fixed: They never told anyone what exactly was causing that CTD. Considering that there are many causes for CTDs, they may even have fixed ithe issue that was annoying players at that time.

 

About two months ago, I started a new game in survival mode. Around two weeks ago, after about 100 hours of game time (this was the net value displayed in the load/save menu; the actual game time played was much longer, because I had to reload often) this game became unplayable, for a very similar issue as the one you described above. In my case, it was County Crossing which I could not approach without an instant CTD, no matter from which direction I tried to approach it. This was not the first time I had encountered such issues in that playthrough; it happened before at Bunker Hill and Sunshine Tidings, but in those cases, there was no urgent need to go there, so I abandoned trying this (after several attempts in a row all ending with an instant CTD) and kept away from those places for some time. Eventually, they became accessible again. In the case of County Crossing however, I had to respond to a settlement attack, and this mission turned out to be impossible to complete, and I abandoned that playthrough.

 

Subsequently, I started another game at the "very hard" level. There are some noticeable differences now in the overall behaviour of the game: CTDs are very rare, while they were pretty frequent in survival mode. Moreover, a lot of glitches that I was inclined to attribute to recent patches have gone away entirely. There was one particular issue that I only had in survival mode so far: traps were not properly reset after reloading and returning to the area. In some cases, the mines were gone or were exploding despite being invisible. I remember that this also happened in Skyrim, especially when you relied on quick saves, and thinking along this line further, a noticeable difference of my game in survival mode was that I had to rely on quick saves entirely (other modes of saving are disabled), while I am never using quick saves otherwise.

 

Long story short: I suspect that quick saves are ruining the game.

 

If you are using quick saves often, try it without them and tell us whether this makes a difference.

Link to comment
Share on other sites

I do use quicksaves frequently. My computer isn't very powerful or new, and sometimes, if I swap areas too often or swap between "countryside" and  "Downtown Boston" my HDD activity just goes crazy and my frame rate drops to about 5 FPS, so I usually just quicksave then Alt-Tab out and close FO4, then reboot my computer. and start again from the quicksave.

 

I play on Very Hard as default and don't use Survival Mode, because I hate the Fast Travel restriction, and I build a lot of settlements, so not being able to respond to raids quickly is a PITA.. Plus I hate running out of ammo all the time, so I carry a tonne of it around :)

 

I'll try loading from a "Hard" save and see what happens.? Or is my current playthrough possibly now totally 'borked' regardless?

 

...

 

The only reason I brought up the 1..2 Patch, was be cause the area around Monsignor Point was causing a tonne of issues for people around Nov - Dec 2015 and many people asked if the 1.2 Update solved the issue. Most posts end about then, so I assumed that Bugthesda had fixed the "something" that was supposedly causing it. But seeing as I am now having the exact same problem, in the exact same area, I thought it might be significant.

Link to comment
Share on other sites

The only reason I brought up the 1..2 Patch, was be cause the area around Monsignor Point was causing a tonne of issues for people around Nov - Dec 2015 and many people asked if the 1.2 Update solved the issue. Most posts end about then, so I assumed that Bugthesda had fixed the "something" that was supposedly causing it. But seeing as I am now having the exact same problem, in the exact same area, I thought it might be significant.

 

I may be significant. It's just that we were not told what caused the bug they fixed, so we have no chance to verify this.

Link to comment
Share on other sites

About all I can tell you on the Monsignor Plaza bug is that I used to get the crash way back when, then Patch 1.2 came along and it stopped. So whatever it was, they fixed at least what seems to be the most common one.

Link to comment
Share on other sites

I tried loading the game from a "hard" save and then entering the area, and it did behave slightly differently. My framerate dropped to about 1 frame per 10 secs,, with my HDD activity going crazy, and the game seemed to take about 10 seconds to process movement input, so it tuned into a sort of very, very  slow "slide show". HDD activity eventually stopped altogether, as if the CPU or GPU was doing calculations, and stuck in a loop.

 

I tried to "back out" of the area, to see if the game would recover itself, but eventually I got the "Program not responding" popup.

 

I abandoned that game, ad am going to start a new playthrough, and not use any quicksaves at all, and see if the problem returns. The only issue is that I have no idea "when" the bug gets triggered, as the last playthrough, I could originally enter the area no problem, so maybe it's after a certain story mission, or when I'm a certain level, or any number of other variables.

Link to comment
Share on other sites

I doubt very much quicksaving has anything to do with the problem. My own game has made extensive use of it and thus far hasn't seen anything like that happen. It's probably just a sensitive location, like Windhelm is for Skyrim.

Link to comment
Share on other sites

Is there any scripted spawns or events that are supposed to occur there after a certain point in the game? I know several quests happen in and around the CIT ruins and Ticonderoga, but those are generally "indoor" cells. I hadn't pursued the main quest in my last playthrough short of going to Diamond City and picking up Piper as a companion, I went straight to the Railroad questline.

 

Like I dunno, maybe a Vertiird is supposed to crash there after you reach lvl 50 or something, but if you haven't killed Kellogg, then the Pridwyn doesn't spawn, so their are no Vertibirds, so the script can't run and the game has a brain fart. Because it "seems" like it's trying to do something, or load something or calculate something, and the game gets stuck in a fatal loop and dies.

Link to comment
Share on other sites

I don't think anything that specific takes place there but it's entirely possible for a regular spawn point to corrupt. I haven't heard of any instances of this in FO4 (or Skyrim) but it was a relatively common issue in the games before that. Corrupted vanilla spawn points are pretty hard to undo because there's nothing you can really do besides find an isolated spot and pass about 200 hours of in-game time by.

Link to comment
Share on other sites

Update # 2:

Well I started a totally new character, complete different. Changed my companion, totally different level, totally different stats, totally different equipment, totally different quests completed, totally different locations discovered (except for the obvious ones) . This toon also was able to do the H2-22 delivery to Ticonderoga, but after leaving the cell and exiting re-starting the game, I cannot go back there ... again.

 

Obviously "something" in my game dislikes that area of the map.

 

Is there a program I can use to "monitor" FO4 and see if I can catch what is causing it?

Link to comment
Share on other sites

  • 2 years later...

Greetings from 2018!

 

For those who still struggle with this bug, I have found a slight workaround: 

1) In order to get anywhere near Ticonderoga, you must fast travel to the C.I.T Ruins. I've narrowed it down, and trying to get there from the Bunker Hill side forces the game into this godforsaken bug for some reason.

2) Turn around and walk backwards in first person view towards Ticonderoga with the camera facing downwards at all times. Use the road to keep your bearing.

3) Once you get inside of the Ticonderoga apartments you should be fine to move freely, but don't dawdle or your game might crash from force of habit.

 

To those who still play this bugged out mess, I hope this helps...

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...