drworm
Member
- Messages
- 63
Problem: The moment I cross the little bridge from vault 111 to Sanctuary for the first time my game crashes to desktop.
Platform: PC
Background: I have been trying to start a new FO4 modded game for some time. I added some environmental mods that I've never used. When I first started testing their effect to FPS I was having the problem listed above. I've done this sort of thing before, so I went back to my original save with only my SS/Conq mods enabled (post war Vault 111, with all the city plan prebuilds done), and tried different environmental mods. When I tried to cross the stream I got the same CTD.
Several more tests later I wondered if there was something wrong with the save file, so I deleted all the saves, made a new Vortex profile with only the vanilla game + DLC, and started a fresh save. Played it to the vault exit, ran down the hill, and entered Sanctuary just fine- game files okay. I then enabled my trusted standard mods, some character creation cosmetic mods that I've also used for several saves, and SS/Conq mods with add on packs. I started a new game again, and got a crash when doing prebuild, but that was a different issue, is in a different thread, and has been solved.
After I got that problem solved (with the mods already mentioned enabled) I got to the vault exit and made a save (let's call it a Foundation Save). I then exited to desk top and started enabling mods. I got a little enthusiastic and exited the vault with a lot more mods enabled than I should for testing, walked slowly down the hill, and got a CTD. Balls!
Fortunately I had recorded precisely what mods were enabled when I made my Foundation Save at the vault exit, so disabled every other mod, loaded that save, and left the vault. I honestly figured this would be my baseline, and didn't expect to get the CTD when entering Sanctuary, but alas I did. Double Balls!
So now I'm left with the fact that it is something I've done wrong with my SS/Conq mods, or one of the other mods is. Those other mods are things like cosmetic appearance mods, Looksmenu, MCM, UFO4P, Settlement Menu Manager, See Through Scopes, and the like. Those mods are up to date, and very stable. The only one among them that has anything to do with the environment is Boston FPS Fix AIO, and that is also unlikely- I don't even think it reaches that far north. I'd list all the mods but I can't find if or where Vortex saves them as text files, and I don't have the time at the moment.
No ENB, no Lighting mods, no Weather mods.
Possibility: Could this be a result of the script data limit I've heard can cause problems for Conqueror? When I set up Conqueror to prebuild, I left all of the default settlement exclusions alone, and added 5 more for me to build at. Abernathy was not excluded, so there is some extra load on those cells, but that's the only prebuild in that triangle of death (as KG calls it).
Platform: PC
Background: I have been trying to start a new FO4 modded game for some time. I added some environmental mods that I've never used. When I first started testing their effect to FPS I was having the problem listed above. I've done this sort of thing before, so I went back to my original save with only my SS/Conq mods enabled (post war Vault 111, with all the city plan prebuilds done), and tried different environmental mods. When I tried to cross the stream I got the same CTD.
Several more tests later I wondered if there was something wrong with the save file, so I deleted all the saves, made a new Vortex profile with only the vanilla game + DLC, and started a fresh save. Played it to the vault exit, ran down the hill, and entered Sanctuary just fine- game files okay. I then enabled my trusted standard mods, some character creation cosmetic mods that I've also used for several saves, and SS/Conq mods with add on packs. I started a new game again, and got a crash when doing prebuild, but that was a different issue, is in a different thread, and has been solved.
After I got that problem solved (with the mods already mentioned enabled) I got to the vault exit and made a save (let's call it a Foundation Save). I then exited to desk top and started enabling mods. I got a little enthusiastic and exited the vault with a lot more mods enabled than I should for testing, walked slowly down the hill, and got a CTD. Balls!
Fortunately I had recorded precisely what mods were enabled when I made my Foundation Save at the vault exit, so disabled every other mod, loaded that save, and left the vault. I honestly figured this would be my baseline, and didn't expect to get the CTD when entering Sanctuary, but alas I did. Double Balls!
So now I'm left with the fact that it is something I've done wrong with my SS/Conq mods, or one of the other mods is. Those other mods are things like cosmetic appearance mods, Looksmenu, MCM, UFO4P, Settlement Menu Manager, See Through Scopes, and the like. Those mods are up to date, and very stable. The only one among them that has anything to do with the environment is Boston FPS Fix AIO, and that is also unlikely- I don't even think it reaches that far north. I'd list all the mods but I can't find if or where Vortex saves them as text files, and I don't have the time at the moment.
No ENB, no Lighting mods, no Weather mods.
Possibility: Could this be a result of the script data limit I've heard can cause problems for Conqueror? When I set up Conqueror to prebuild, I left all of the default settlement exclusions alone, and added 5 more for me to build at. Abernathy was not excluded, so there is some extra load on those cells, but that's the only prebuild in that triangle of death (as KG calls it).
