So, for some time I've been having CTDs when approaching Concord (or any heavily scripted area) like MANY of you, and I may have found the source of the problem for you because yesterday I've fixed my CTDs [YAY! :D] (even when using mods such as Horizon which is a complete overhaul).
So, after A LOT OF RAGE AND DEBUGGING, I found out the problem! It is due to the Levelled Lists that the weapon/armor/etc mods uses. The reason probably is due to the mods not using scripted injection and directly implementing on FO4 LLs (maybe due to most of them not being maintained past some FO4 patches or not going into further development).
I've already posted this in both Horizon and W.A.T.M, so if you have any major mods, they are going to have trouble running with mods that alter Levelled Lists that are not made properly with their own scripted injection. So please, check it out if your weapon/armor/item mod have a PROPER SCRIPT INJECTION for the LLs, otherwise they are going to cause crashes in scripted areas that have a lot of spawns (which in order make heavy usage of LLs), like Concord.
Now going further in the technical aspect of computers, my theory is that those mods that causes CTDs are accessing memory from your computer when it is not necessary, when it doesn't exists (corrupted or missing LLs that the badly/not maintained developed mods made) or when accessing the same memory record that another mod is using. THIS IS JUST a theory due to my computer knowledge background.
Again, if you are experiencing these crashes, MAKE A NEW INSTALL OF FALLOUT 4, CLEAN THE DLCS MODULES WITH FO4EDIT AND INSTALL ONLY We Are The Minute Man, Unofficial Patch and Sim Settlements 2 (This was the trio that was reportedly crashing Concord when used together) AND GO TO CONCORD. If it doesn't crashes, it seems that you had the same problem (which is very likely).
IF THIS DOESN'T FIX, the problem could be the following:
1 - You were very very VERY stubborn (like me in the first 3 hours of debbuging and going insane insulting FO4), wouldn't let go of your mods, thinking it was the modders fault and wouldn't do a proper test
2 - Your save is already FILLED with corrupted content so you need a new game save (before exiting Vault 111)
3 - You are messing up when installing mods and organizing your load order.
So, after A LOT OF RAGE AND DEBUGGING, I found out the problem! It is due to the Levelled Lists that the weapon/armor/etc mods uses. The reason probably is due to the mods not using scripted injection and directly implementing on FO4 LLs (maybe due to most of them not being maintained past some FO4 patches or not going into further development).
I've already posted this in both Horizon and W.A.T.M, so if you have any major mods, they are going to have trouble running with mods that alter Levelled Lists that are not made properly with their own scripted injection. So please, check it out if your weapon/armor/item mod have a PROPER SCRIPT INJECTION for the LLs, otherwise they are going to cause crashes in scripted areas that have a lot of spawns (which in order make heavy usage of LLs), like Concord.
Now going further in the technical aspect of computers, my theory is that those mods that causes CTDs are accessing memory from your computer when it is not necessary, when it doesn't exists (corrupted or missing LLs that the badly/not maintained developed mods made) or when accessing the same memory record that another mod is using. THIS IS JUST a theory due to my computer knowledge background.
Again, if you are experiencing these crashes, MAKE A NEW INSTALL OF FALLOUT 4, CLEAN THE DLCS MODULES WITH FO4EDIT AND INSTALL ONLY We Are The Minute Man, Unofficial Patch and Sim Settlements 2 (This was the trio that was reportedly crashing Concord when used together) AND GO TO CONCORD. If it doesn't crashes, it seems that you had the same problem (which is very likely).
IF THIS DOESN'T FIX, the problem could be the following:
1 - You were very very VERY stubborn (like me in the first 3 hours of debbuging and going insane insulting FO4), wouldn't let go of your mods, thinking it was the modders fault and wouldn't do a proper test
2 - Your save is already FILLED with corrupted content so you need a new game save (before exiting Vault 111)
3 - You are messing up when installing mods and organizing your load order.
