- #Mod configuration menu cannot access menu files install
- #Mod configuration menu cannot access menu files mod
- #Mod configuration menu cannot access menu files archive
- #Mod configuration menu cannot access menu files mods
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. Its old but maybe someone needs help with this. 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.
#Mod configuration menu cannot access menu files mods
If that fixes it, wipe your UI mods and try again.
#Mod configuration menu cannot access menu files archive
You can troubleshoot the first by disabling archive invalidation, which will make the game ignore the modded assets. 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. Also double check your archive invalidation. Also delete any files left in your documents for good measure.ĭid 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.
If not, try it again and make sure to delete everything. 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. 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. If anybody else has made any progress with this issue, I would love to know any workarounds because I'm on the verge of giving up on MO2 and just going back to NMM.Like I said, it's outdated and it says so in the description. I am still having some trouble with some MCM interfaces even after doing the fix, so it's more of a band-aid on a gunshot wound until someone decides to actually fix the issue. So, no, Mod Organizer 2 still hasn't fixed the MCM issue and you would still have to follow the methods the OP posted. This is not the case, however, as the only things that show up in the MCM menu is " MCM Settings" and "Hotkey Manager".
#Mod configuration menu cannot access menu files install
If you wanted to test this out, simply get a clean install of Fallout 4 - install F4SE and MCM using Mod Organizer 2 (latest version from github), then install a mod that utilizes MCM (such as Extended Dialogue Interface or FallSouls) and it should show up in the MCM menu when in game. He isn't having a problem installing and running F4SE or MCM, rather he's having trouble with mods that utilize MCM showing up in the actual MCM menu. I think you're misinterpreting what psychotrip is trying to accomplish. Please add an appropriately named ini file inside the Settings folder for us MO2 users." This is what is stopping settings being saved once people get the mods recognized by MCM. " The trouble with Mod Organizer 2 is that it stops mods generating new files. This post has been stickied on their nexus page for a while: Is MO supposed to work fine with MCM? Because according to this thread and many others, and even MCM's own instructions, MO2 doesn't work with MCM unless you manually move files around. I'm still not sure what exactly is going on. Please add an appropriately named ini file inside the Settings folder for us MO2 users.Ĭan you delete all the current logs and then run FO4 and then post the logs here in spoiler tags please.Įnsure you set the logging to debug in your settings first, you can reset it after so it doesn't thrash. You can leave it there or move it to the appropriate location inside Fallout 4\ Data\ MCM\Settings. This is where the keybindings are stored.
The mod will now appear in the MCM menu and settings will be persistent.Īlso of note, a file called "Keybinds.json" may appear inside some folders in your Overwrite folder in Mod Organizer 2. Rename file to the name of the ESP file and change file extension to "ini" e.g. Inside the Settings folder right click and make a new txt file. Go to Fallout 4\ Data\ MCM and generate a folder labeled "Settings" if needed. Move the MCM folder from ModOrg 2\Fallout 4\Mods\Ĭopy the name of the mods ESP file e.g. The trouble with Mod Organizer 2 is that it stops mods generating new files.
0 kommentar(er)
