Non-SS Bug Vault 81-CTD

[mamst]

When ever entering Vault-81, I get a CTD. It occurs while taking the elevator down into the vault 100% of the time. I removed all my mods except for SS2 and SS2 Extended (and required frameworks), but I still get the crash. I even attempted to use "tcl" to go the through the secret vault and enter that way but it still crashes. I'll post both load order of all mods and just my SS2 mods.
All Mods:
fallout4.esm
DLCrobot.esm
DLCworkshop01.esm
DLCCoast.esm
DLCworkshop02.esm
DLCworkshop03.esm
DlCNukaWorld.esm
Unofficial Fallout 4 Patch.esp
ArmorKeywords.esm
DamnApocalypse_CORE.esm
PANPC.esm
WorkshopFramework.esm
HUDFramework.esm
SS2.esm
SS2Extended.esp
NoAffinityCooldown.esp
NoNegativeAffinity.esp
Better Inventory Sorting - Armors.esp
Reverb and Ambiance Overhaul.esp
Vivid Weathers- FO4.esp
Vivid Weathers- FO4- Quest.esp
W.A.T.Minutemen.esp
Vivid Waters.esp
Vivid Weathers-F04-Far Harbor.esp
Vivid Weathers-Natural Bright.esp
Vivid Weathers-Nuka World.esp
Another Sanctuary Bridge.esp
MK18.esp
M1Garand.esp
P90.esp
M1Garand-AWKCR.esp
P90NPC.esp
Better Inventory Sorting-Misc.esp
Companion Infinite Ammo and Unbreakable Power Armour.esp
dD-Enhanced Blood Basic.esp
dD-Screen Blood Duration Medium.esp
EasyHacking.esp
EveryonesBestFriend.esp
EasyLockpicking.esp
HoloTime_2.esp
VisibleCompanionAffinity.esp
Vivid Fallout-All in Ones -4K.esp
BetterWeapons.esp
DamnApocalypse_CombatTweaks.esp
CraftableAmmo.esp
CraftableAmmo_plus.esp
Armorsmith Extended.esp
Pop-BoyFlashlight.esp


SS2 Only:
fallout4.esm
DLCrobot.esm
DLCworkshop01.esm
DLCCoast.esm
DLCworkshop02.esm
DLCworkshop03.esm
DlCNukaWorld.esm
WorkshopFramework.esm
HUDFramework.esm
SS2.esm
SS2Extended.esp

Again both sets of mods cause CTD upon trying to enter Vault 81

 

[Irealys]

Okay, because I got thinking about how someone could get quick save happy trying to avoid the molerat disease.

Nah... gamers wouldn't do that ;-)

 

[Bored Peon]

Nah... gamers wouldn't do that ;-)

Well you are right. I just duplicate the cure with the console instead, much easier.

 

[John Knapp]

I just remembered something I had read. Did either of you create a bunch of autosaves or quick saves while in Vault 81?

Apparently creating too many saves in a short period of time starts and stops scripts enough they can break, then once you leave the area the broken script can cause a CTD when you come back into the area.

I tried going back to a really early save, but still had Vim & Vigor started, and did a quicksave before getting to vault. Got down into vault okay this time. But I really didn't feel like redoing 5 hrs. so on a whim I tried entering the vault again from a save after I had almost finished Hole in the Wall and this time I managed to enter the vault okay . I don't see how something in one save file can affect other save files that had been good?!?

 

[Bored Peon]

I tried going back to a really early save, but still had Vim & Vigor started, and did a quicksave before getting to vault. Got down into vault okay this time. But I really didn't feel like redoing 5 hrs. so on a whim I tried entering the vault again from a save after I had almost finished Hole in the Wall and this time I managed to enter the vault okay . I don't see how something in one save file can affect other save files that had been good?!?

Well basically something got corrupted between the two saves if the older one is fine and newer one does not work.
For example, like I said earlier if a script went bad while you were in there last, it wouldnt crash the game then, but when that cell gets loaded again the script could cause a CTD when it attempted to resume.

 

[gentlemendemon]

I have the same issue. It seems this is related to SS2 cause if I disable this mod then I no longer get CTD when I enter vault 81. This started around after talking to Mansfield about looking for the lost patrol. I reloaded to an earlier save and don't seem to have this issue. So as long as I don't progress vim & vigor to the point where I need to look for the lost patrol, the game works fine. Is there anything I can do? I'd like to progress the questline further

 

[mamst]

Have you tried restarting vim and vigor now from the earlier save? is it still crashing? I was able to get it to progress past vim and vigor. I'm not sure of the exact cause nor whether the actually bug is connected to "vim and vigor" Its is possible the bug is something separate but not game breaking until "Vim and Vigor" which combine to cause the CTD. It's not guaranteed to happen though so you just have to load a save prior to the bug. Here is the step by step I posted earlier on how to do this.

1)load a save
2)check if Vim and Vigor is already started. If yes go to 3, if not go to 2a.
2a)if vim and vigor has not been started use the following console command. Cqf ss2_mqmaster skipToQuest ss2_sirick_mq09
2b)wait while ss2 simulates you completing the quests until you see Vim and Vigor start
3)teleport to exterior of vault 81 using the console command COC vault81ext
4)try to enter the vault.

If it crashes start again with an even older save. If it works and you can enter vault 81 then you found a working save. once you finding a working save you can just reload that save file (from before the console cheats) and just play from there.

Good luck, hope you find a working save without having to go to far back. I had to go two play hours back on mine.

 

[gentlemendemon]

Have you tried restarting vim and vigor now from the earlier save? is it still crashing? I was able to get it to progress past vim and vigor. I'm not sure of the exact cause nor whether the actually bug is connected to "vim and vigor" Its is possible the bug is something separate but not game breaking until "Vim and Vigor" which combine to cause the CTD. It's not guaranteed to happen though so you just have to load a save prior to the bug. Here is the step by step I posted earlier on how to do this.

1)load a save
2)check if Vim and Vigor is already started. If yes go to 3, if not go to 2a.
2a)if vim and vigor has not been started use the following console command. Cqf ss2_mqmaster skipToQuest ss2_sirick_mq09
2b)wait while ss2 simulates you completing the quests until you see Vim and Vigor start
3)teleport to exterior of vault 81 using the console command COC vault81ext
4)try to enter the vault.

If it crashes start again with an even older save. If it works and you can enter vault 81 then you found a working save. once you finding a working save you can just reload that save file (from before the console cheats) and just play from there.

Good luck, hope you find a working save without having to go to far back. I had to go two play hours back on mine.

So I have tried this and everything works fine right up until the part of vim & vigor where mansfield asks me to look for the lost patrol/his sister. Once I reach this point then the game will CTD when I try to leave the vault

 

[mamst]

Sounds like you might have a different issue then. I misread your original post and thought you were have the CTD when entering vault 81. My issue was a CTD when trying to load into vault 81 after vim and vigor started. Once I got into vault 81 I was able to progress no problem including the lost patrol section. Have you tried using console commands to complete vim and vigor? do you still crash on exiting the vault?

 

[GuardianMF]

Buffout 4 has a huge list of bugs that will cause CTDs and potential save corruption. I wouldn't touch it with a 10 foot pole.

The Bugs section for Buffout 4 is misleading at face value. Most entries are actually requests (people reporting engine bugs that could potentially be fixed by Buffout 4) and there are bug reports that were solved but not marked as such. Also, most early issues were from the interaction between Buffout 4 and other mods (I had one with Wheel Menu and that was fixed).

 

[BinaryMisfit]

Buffout 4 has a huge list of bugs that will cause CTDs and potential save corruption. I wouldn't touch it with a 10 foot pole.

I think you completely misunderstand what Buffout 4 is. It doesn't cause CTD's. It fixes the enigne for FO4. The reports you see is the proper error reports it produces that helps you track down errors with mods. It is the single most useful tool I have seen for FO4 to date. It has not been responsible for any save corruption that I am aware of.

With respect to you, maybe read up on what it is before making a statement like this and causing misinformation to be spread?

 

[gentlemendemon]

Sounds like you might have a different issue then. I misread your original post and thought you were have the CTD when entering vault 81. My issue was a CTD when trying to load into vault 81 after vim and vigor started. Once I got into vault 81 I was able to progress no problem including the lost patrol section. Have you tried using console commands to complete vim and vigor? do you still crash on exiting the vault?

I haven't tried using console commands only because I do not know them. Sorry I'm fairly new to this lol. If you know the commands, I'd be willing to give it a try.

 

[1000101]

I think you completely misunderstand what Buffout 4 is. It doesn't cause CTD's. It fixes the enigne for FO4. The reports you see is the proper error reports it produces that helps you track down errors with mods. It is the single most useful tool I have seen for FO4 to date. It has not been responsible for any save corruption that I am aware of.

With respect to you, maybe read up on what it is before making a statement like this and causing misinformation to be spread?

No, I wasn't referring to the bugs that Buffout reports, I was referring to the list of bugs in Buffouts own bug tracker with Buffout itself. While since I've looked at it most have been fixed that doesn't change that when I posted my comment more than two months ago there were still a number of outstanding bugs.

With respect to you, maybe read up on it's own bugs and don't assume people are spreading misinformation when the information they are referring to is documented in the projects own tracker.

That all being said, since my post from two months ago, I have given Buffout a try and it does seem to work, at very least it does not seem to cause any additional issues. I can't say for certain that it is actually preventing any crashes as I didn't have that many to begin.

 

[BinaryMisfit]

No, I wasn't referring to the bugs that Buffout reports, I was referring to the list of bugs in Buffouts own bug tracker with Buffout itself. While since I've looked at it most have been fixed that doesn't change that when I posted my comment more than two months ago there were still a number of outstanding bugs.

With respect to you, maybe read up on it's own bugs and don't assume people are spreading misinformation when the information they are referring to is documented in the projects own tracker.

That all being said, since my post from two months ago, I have given Buffout a try and it does seem to work, at very least it does not seem to cause any additional issues. I can't say for certain that it is actually preventing any crashes as I didn't have that many to begin.

My apologies. I actually didn't look at how old the post was when I replied. We have been recommending Buffout to people to try and track issues and seeing a post from a respected member and builder was a bit of a shock and I may have responded quicker then I should have.

 

[GuardianMF]

Oops, didn't notice this was an old thread either. Buffout 4 did have a number of bugs/issues when it was released.

 

[mamst]

I haven't tried using console commands only because I do not know them. Sorry I'm fairly new to this lol. If you know the commands, I'd be willing to give it a try.

If you haven't fixed it yet and still need console command help, here is how to skip Vim and Vigor. I would suggest making a save prior to skipping the quest incase it doesn't work.
1) press the Tilde key looks like: ~
2)then copy and paste the following command: Cqf ss2_mqmaster skipToQuest ss2_sirick_mq10

that should skip the quest. I'm not certain it'll fix your game though.

 

[Deleted member 10215]

If you haven't fixed it yet and still need console command help, here is how to skip Vim and Vigor. I would suggest making a save prior to skipping the quest incase it doesn't work.
1) press the Tilde key looks like: ~
2)then copy and paste the following command: Cqf ss2_mqmaster skipToQuest ss2_sirick_mq10

that should skip the quest. I'm not certain it'll fix your game though.

I've been using that myself the past few runs of the questline (since I'm getting V81 crashes too), and it doesn't SEEM to cause any problems to do that.