Mod Configuration Menu (MCM) help

[Rocketpants]

I installed MCM to use with Project Reality and it worked fine. I then installed Unified HUD Project to use with a HUD mod and it's made changes to some .xml files which has now broken MCM. Uninstalling the HUD mods hasn't fixed it, neither has reinstalling MCM. When I go to the pause menu I get the error:

"The Mod Configuration Menu cannot access its menu files. Either the files are missing, or a firewall/UAC is preventing access. You may need to reinstall the mod, update your 32-bit Visual C++ 2010 Redistributable Package, or change your firewall/UAC settings."

It's not the firewall, and it's not C++. From what I can tell it's something in an .xml file that's ♥♥♥♥♥♥ up but I can't figure it out. My only hope at this point would be to reinstall the entire game! Help

[Ladez]

Unified HUD Project is outdated. We now use an NVSE plugin called UIO for UI mod compatibility.

When installing UI mods, follow this install order:
1. DarNified/MTUI
2. Project Nevada
3. MCM
4. Other UI mods.
5. One HUD

UIO can be installed whenever.

Make sure that archive invalidation is applied when you're done.

You might want to wipe the menus folder in your data folder and install your UI mods from scratch following the above suggestions.

[Rocketpants]

Deleting the menu folder didn't work. Out of frustration I have uninstalled all mods and the game, reinstalled the game and have so far only added an ENB, Project Reality, DarNUI and still MCM won't work! I get the same error message, how is that even possible? And now in another attempt to fix it the game ctd's on startup.

I really don't understand what has happened. I had the game working just fine with a lot of other mods installed until I installed that stupid Unified HUD Project and now it's ♥♥♥♥♥♥ the whole thing up. It shouldn't even be on the Nexus if it causes issues like this.

[Ladez]

Like I said, it's outdated and it says so in the description. It was left up mainly for those running already working installaitons, but it's a while back now and there's no reason to not use UIO instead.

When you uninstalled the game did you also remove everything from the installation folder? Steam only removes files that it put there itself, so you may have left over files added by mods. If not, try it again and make sure to delete everything. Also delete any files left in your documents for good measure.

Did you make sure to follow the steps I provided above when you installed your mods? MCM -must- be installed after Project Nevada (which is what I assume you mean by Project Reality,) and DarNUI should always be installed first. Also double check your archive invalidation.

There's two mod-related things that can crash the game at startup, borked menu files or a load order issue, usually missing master file. You can troubleshoot the first by disabling archive invalidation, which will make the game ignore the modded assets. If that fixes it, wipe your UI mods and try again. You can troubleshoot the second by loading your plugins with FNVEdit, which simulates how they're loaded by the game and will throw an error if a file is missing.

[Rocketpants]

It's possible it's ArchiveInvalidation actually. This is my first time modding NV - when I modded FO3 I used NMM to manage it and the auto-archiveinvalide worked. I think NV is more tricky because of the way Steam makes certain .ini files read-only and will overwrite changed ones, I don't think the archiveinvalidate works correctly in NMM because it doesn't have the right permissions. So I need to change Fallout_default.ini which is the main file and not read-only.

I'm also uninstalling the game again and will delete every last trace of the game. I didn't delete my test save files but I'll literally start from scratch this time.

[capodelsur14]

its old but maybe someone needs help with this. if you have this problem "The Mod Configuration Menu cannot access its menu files..." or the MCM "has detected multiple..etc" this might help you .
you need FOMM and NMM

1- uninstall MCM-Unified HUD- I HUD- UIO (any HUD mod that you have installed) also uninstall Project Nevada (if you have P.Nevada installed and any compatibilty patch for PN)

2-now open NMM (nexus mod manager) (if you dont have NMM download it)

3- deatctivate archive invalidation via NMM (tools-uncheck archive inavalidation)

4-open FOMM and install Project Nevada and any compatibilty patch for PN via FOMM

5- Open again or maximize NMM and install IN THE FOLLOWING ORDER:

first: MCM
then: MCM BugFix 2 (if you dont have it download it from nexus MCM web page)
then: I-HUD (be sure to install I-HUD version 3_4!!. The nexus authors web page says its no longer supported but dont mind that, download it and install it)
last: Unified HUD

6- reactivate archive invalidation via NMM (tools- check archive invalidation)

7- Fixed ! open Fallout New vegas and play

[†]

Ladez I followed all of your instructions and the MCM doesn't show up.

[capodelsur14]

Originally posted by SubCriticalPocket:

Ladez I followed all of your instructions and the MCM doesn't show up.

did you installed MCM via NMM or FOMM?

[Vorsky]

Originally posted by -FL- capodelsur14:

Originally posted by SubCriticalPocket:

Ladez I followed all of your instructions and the MCM doesn't show up.

did you installed MCM via NMM or FOMM?

I'm kinda confused here, do I have to install it via NMM or FOMM?

[talgaby]

Right now, FOMM or NMM legacy. Normal NMM has issues with FOMOD files.

[Vorsky]

Got it, thanks.

[Shadax]

I had the same error today. And after trying several things (like the read-only box, or set the exe to run as admin), I just restarted MO2 as admin. And that solved the issue.