Questdog

Exactly my point. If the priority number was given in the conflict list, then no searching would be required.

Not unless you have your left mod-list sorted alphabetically, which is otherwise a useless sort.

In the conflict page of a mod, it would be very helpful to show the priority numbers of the conflicting mods so that we could locate the offenders a lot quicker.

I will do as you have asked when I get some time. I don't save the archived files because of disk space, so all I have is the mod folder with the meta files. But the issue happened even if I de-activated every mod.

I re-installed MO 1.2.18 over my current installation and there was no change; still could not play. I made a completely new MO 1.2.18 installation and copied my mod folder/profiles/etc. from the old installation and still could not play with mods activated or not. I made a completely new 1.2.18 installation and tried to play with no mods installed yet and it worked. Downloaded a mod and activated it and it still worked, so now I am re-downloading all 8,237 mods I have acquired over the years. What fun! P.S. The mod total reported may be a slight exaggeration.

I tried offline. I'm not saying it is MO's fault, but I'm saying it only happens in MO. I can play from steam launch and 1.3beta (w/o fnv4GB.exe).

What details do you want? The only change was that I installed the new Nvidia driver and I already uninstalled that to see if it was the problem, but no dice. P.S. 1.3 beta seems to work with the NVSE launcher, though it crashes when trying to launch with fnv4gb.exe

I am having the same problem. If I try to launch with the FNV4GB or NVSE the game hangs at the Bethesda logo. If I try to launch with falloutnv.exe it crashes. It does not matter whether I have any mods enabled or not. I played earlier in the day with no issues and now I can't play. I tried the blacklist.txt file and no change in behavior. I am running win7 ultimate 64-bit. I can launch the game from steam and I can launch Skyrim and Fallout 3 with no problems from MO, but not New Vegas. P.S. I haven't played Skyrim for a while and the MO version for it is still 1.2.14. Fallout 3 uses 1.2.18, though it is not a steam game on my system. Verified game cache, etc., etc....

Well, I just finished a run through Fallout 3 with 1 BSA active above the limit you mentioned. I had all the official ones, the Unofficial Patch, Streetlights.bsa and Zumbs' Overhauled Real Time Security.bsa. And that was with MO managing the archives.

Quite a few (Seems most mods want to have BSA's nowadays). I installed a fresh version of MO with no mods and the game loaded fine whether or not MO was managing archives. So, I will reload the mods that use BSA's and extract them. Thanks! P.S. However, the game DID load fine and run with all these BSA's as long as I did not check the box for MO to manage them.

Thanks!

If I check the box to have MO manage archives, FO:NV crashes on start up. Is this a known issue? I searched and could not find anything relevant.

Never noticed this happening before, so I guess it is a new feature, but it is one that I do not like. Is there a way to turn this off? What I am talking about is the fact that now mods with the same Nexus ID are gouped together in a folder-like structure in the left pane. This makes some sense for mods that actually have the same Nexus ID (though I still prefer it the old way - makes it easier to arrange load order), but for mods that have no Nexus ID, it is unfortunately grouping them all together even though they have no relationship to one another other than the fact that they have no Nexus ID.

I would just like to report that this issue has been fixed in the latest build (1.2.18). Thanks!

Deleting a long list of saves seems impossible due to the fact that the confirmation window that opens drops off the bottom of the screen and cannot be resized or moved so that the button is clickable.