Need help with new mods making game crash

[FistoMatic]

So I have been playing New Vegas for a while now and have used mods for a while also. I know how to install and use mods but that's about it I have no idea how they work or anything. Now when I started playing New Vegas on PC a few years ago I got a few mods and luckily they all seemed to just work together fine. Today I went back on New Vegas after not playing it for a few months and decided to download a few new mods (quests, weapons etc.) and suddenly the game has started crashing every time I open a container and go to my weapons tab as in to store my weapons in the container. It happens with every type of container every time I have tried. I figured it must have been one of the new mods I had installed so I turned all the new ones off then started to turn them on one by one until I found the one causing it. It is one of the new weapon kits I installed called 'Project Weaponry'. So I went to the mod page to see if there where any known conflictions but they were not listed. After that I went and read some tutorials on fixing mods, one said to download FNVEdit so I did and after watching tutorials on that found out that it is conflicting with a couple of weapon files in NVEC (I think). So the tutorials said to make a merged patch which didn't fix the problem. Another tutorial said to download LOOT so I did which from what i can tell hasn't found any issues (It says at the top of the window Errors - 0). So basically all I'm asking is, is there a way of making it work or do I just have to play without this particular mod?

 

Here is my load order;

 

FalloutNV.esm

DeadMoney.esm

HonestHearts.esm

OldWorldBlues.esm

LonesomeRoad.esm

GunRunnersArsenal.esm

ClassicPack.esm

MercenaryPack.esm

TribalPack.esm

CaravanPack.esm

oHUD.esm

NVEC Complete + NVCE.esm

Weapons.of.the.New.Millenia.esm

NVInteriors_Core.esm

Survivalist Bunker.esm

NVInteriors_ComboEdition.esm

SomeguySeries.esm

The New Bison Steve Hotel.esm

RockwellPursuit.esm

MoonQuest.esm

DK_BulletTime_NV.esp

HDTshop.esp

FalloutNV_lang.esp

One Perks per Level.esp

Weapons.of.the.New.Millenia.Cheat.Cabinet.esp

Weapons.of.the.New.Millenia.Honest.Hearts.Grunt.Patch.esp

Weapons.of.the.New.Millenia.Leveled.Lists.esp

EVE FNV - ALL DLC.esp

Run a Shop 2.esp

GRA-WRP-Patch-Two_Unofficial.esp

The Mod Configuration Menu.esp

RockwellDescentMod.esp

RockwellPursuit2014Update.esp

FlashlightNVSE.esp

TheInheritance.esp

KingOfTheRing.esp

DEagle.esp

001 Project Weaponry.esp (This is the one that seems to be the problem)

AutumnLeaves.esp

The Weapon Mod Menu.esp

m24.esp

Project Weaponry Merged Patch.esp

Total active plugins: 41

Total plugins: 52

Sorry if this is more information than needed just thought I'd get everything in. And thanks in advance if anyone can help me.

 

[FistoMatic]

Should also mention I have NVSE and ArchiveInvalidation

[dubiousintent]

Your container problem is likely due to an XML conflict. Take a look at this post, in particular the 4th point about "MCM/oHUD/UIO" and the article it links to. You are using oHUD, MCM, WMM, and FlashlightNVSE, which have XML files. So you may have other XML "install file" conflicts that are not apparent in your LO.

 

-Dubious-

Edited May 19, 2016 by dubiousintent

[FistoMatic]

Thanks for the help! After reading your other posts I went and checked the new mod I got that is causing the crash this 'Project Weaponry' and it does not have any .xml files to cause a conflict, or does this not matter?

[dubiousintent]

Well, if it doesn't have any XML files then they (from "Project Weaponry") can't be the source of the problem. Did you look into the install order of your HUD/UI/Menu mods? While not directly related to "Project Weaponry", they might be causing the CTD upon opening a container if they aren't installed in the right order.

 

That leaves the record conflicts you found (though why they would only be causing a CTD when you open a container is beyond me. Usually the last loaded wins the conflict and you only get a CTD if something is missing or out of order. However, conflicts in "leveled lists", which are probably present, are another matter).

 

You say you tried creating a "merged patch" file. I presume that was manually? You might try to use "Wrye Flash" to create a Bashed Patch. That is actually an easier process, though you have less total control but it does handle "leveled lists" for you. Last night I updated the post I linked above to include links to all the referenced tools.

 

-Dubious-

Edited May 19, 2016 by dubiousintent