In need of help NMM crashing !

[Gus]

Hi ! I've been using NMM community edition to mod FNV and it's been a really useful tool. I was modding just now and while downloading mods NMM crashed. It is now impossible for me to open NMM. I have excluded it's folder from antivirus scans but it didn't fix it. I am very scared of uninstalling and reinstalling as I have sent very long hours elaborating a precise mod list following FNV Ultimate modding guide. It would be a huge bummer if I lost my mods and the way they are organised. Maybe you could help me ?

Screen of crashing message : https://imgur.com/un89ChR

I have the crash log but can't submit it here for some reason

[The Villain]

Mod Organizer 2 is a far superior mod manager.

[mikk011]

Originally posted by The Villain:

Mod Organizer 2 is a far superior mod manager.

ATTN: The Villain. While I agree that MO2 is a better manager than community NMM, your comment wasn't helpful in the context of the question. OP was using NMM because it is what their modding guide specified. Also, NMM is not necessarily the CAUSE of the problem. My FNV modlist was installed using NMM because that was what I was using then and it still works just fine.

PLIPLOPLIP, your screenshot did not give enough information to be useful. If you want to share that information, go to the file named in your screenshot C:\Users\gusta\Documents\Nexus Mod Manager\TraceLog20210704182526.txt, open it and copy and paste what it says to a forum post.

Next, the major cause of your problem was Sinitar. Somewhere in setting up your computer and game, or installing the mods and making the .ini edits you missed something or made a mistake. I would never recommend Sinitar's FNV guide; his stuff works, but unless you have a good background in modding Bethesda games in general and FNV in particular it is amazingly easy to make errors trying to follow a guide this complex. Also, while his custom edits work, his guide adds complexity because there are newer mods out there that do essentially the same thing with less hassle (for example, if you are running Window 10, New Vegas Tick Fix by itself replaces New Vegas Stutter Remover and several of the guide's manual edits).

Ironically, Sinitar's guide actually covers some of the points I would look at, regarding how your system is set up.
-Do you have all the requirements (have the DLC, computer meets minimum specs etc)
-Do you have VC++2013 installed?
-Is your game installed in C:\...\Programs (x86)? If it is, this is a big no-no for BGS games modding.

What to do?
-You might try to contact Sinitar, since he is the person most likely to recognize the source of a particular error.
-You can post the full error report and the answers to the above questions and maybe somebody will be able to see if there are any obvious mistakes.
-You can also go back to your guide and line-by-line, doublecheck that each step was completed fully and correctly, and that the edits are actually correct in your .ini files.

I am sorry that I don't have good news, but standard procedure when modding any bethesda game is to add only 1-2, or 1-3 mods at a time and testing for function. Installing an entire modlist and then trying to debug it is at best a very difficult task. There is a very real possibility that you will need to do a clean reinstallation and start over.

[FlickGodNA]

I'm not 100% familiar with NMM Community Edition but it could be your plugins.txt file causing the crash. Your trace log may confirm that if we could see.

You could try creating a backup of your plugins.txt to somewhere like your desktop, then deleting the original. Then load up NMM and see if it crashes. It should generate a new plugin.txt file and hopefully resolve the crashing.

You could also ask the forums for assistance, show them your error message and trace log, and they may be able to help.

[The Villain]

Originally posted by mikk011:

Originally posted by The Villain:

Mod Organizer 2 is a far superior mod manager.

ATTN: The Villain. While I agree that MO2 is a better manager than community NMM, your comment wasn't helpful in the context of the question. OP was using NMM because it is what their modding guide specified. Also, NMM is not necessarily the CAUSE of the problem. My FNV modlist was installed using NMM because that was what I was using then and it still works just fine.

PLIPLOPLIP, your screenshot did not give enough information to be useful. If you want to share that information, go to the file named in your screenshot C:\Users\gusta\Documents\Nexus Mod Manager\TraceLog20210704182526.txt, open it and copy and paste what it says to a forum post.

Next, the major cause of your problem was Sinitar. Somewhere in setting up your computer and game, or installing the mods and making the .ini edits you missed something or made a mistake. I would never recommend Sinitar's FNV guide; his stuff works, but unless you have a good background in modding Bethesda games in general and FNV in particular it is amazingly easy to make errors trying to follow a guide this complex. Also, while his custom edits work, his guide adds complexity because there are newer mods out there that do essentially the same thing with less hassle (for example, if you are running Window 10, New Vegas Tick Fix by itself replaces New Vegas Stutter Remover and several of the guide's manual edits).

Ironically, Sinitar's guide actually covers some of the points I would look at, regarding how your system is set up.
-Do you have all the requirements (have the DLC, computer meets minimum specs etc)
-Do you have VC++2013 installed?
-Is your game installed in C:\...\Programs (x86)? If it is, this is a big no-no for BGS games modding.

What to do?
-You might try to contact Sinitar, since he is the person most likely to recognize the source of a particular error.
-You can post the full error report and the answers to the above questions and maybe somebody will be able to see if there are any obvious mistakes.
-You can also go back to your guide and line-by-line, doublecheck that each step was completed fully and correctly, and that the edits are actually correct in your .ini files.

I am sorry that I don't have good news, but standard procedure when modding any bethesda game is to add only 1-2, or 1-3 mods at a time and testing for function. Installing an entire modlist and then trying to debug it is at best a very difficult task. There is a very real possibility that you will need to do a clean reinstallation and start over.

Lol oh shut up. Nobody asked you for your condescending horse flop, oh arrogant, pretentious one.