![]() 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. Furthermore, all the changes are saved in the memory, thereby ensuring that you never lose mod settings. You can use the tool’s steppers, dropdowns, sliders, checkboxes, buttons, and key binds to configure all available mods. 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. Optimized for desktops, Mod Configuration Menu or MCM provides users with several options to configure different mods. 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". 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 Mod Configuration Menu.esp=1 Wait.The trouble with Mod Organizer 2 is that it stops mods generating new files. The Mod Configuration Menu.esp=1 I had that problem once, here is how I fixed it I've actually had it work twice before but for some reason it starts working then. Originally posted by Shakedaddy:I'm having the hardest time getting MCM to work. YUP - NPC Fixes (Base Game + All DLC).esp=1 Have spent hours googling and trying to find answers, can anyone help? I've tried checking and unchecking the archive invalidation thing. I have no anti-virus on my computer whatsoever other than the standard windows thing, but just in case I tried turning off windows anti-virus AND both my firewalls. You may need to reinstall the mod, update your 32-bit visual c++ 2010 redistributale package, or change your firewall/uac settings.' Ether the files are missing, an error has occurred with the nvse plugin, or a firewall/uac is preventing access. If you are having trouble accessing or logging into the Mods menu in game: Check the Bethesda Support Twitter account to see if there are any planned. 'The mod configuration menu cannot access its menu files. Here's what comes up when I hit escape and go to the menu: For nvse issues start fallout new vegas and then press the key and then type the following: getnvseversion. ![]() I'm having the hardest time getting MCM to work.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |