GSDFan

Alpha 2 shared mode Change instance switch is in settings, general tab at the bottom.

Do not use the MO 2 alphaX builds for Skyrim at this time. The 32bit executable portion is not functioning properly.

Once you get below the limit it should load those. As long as the ESPs you remove don't cause a problem that is.

How many ESPs and ESMs do you have in the right pane that are activated?

You may have removed a mod and did not realize it. Click on the saves tab and hover over the top save. A message will pop up telling you what ESp or ESM is missing.

I would add to set it to always ask so you get a dialog to make a selection when the download with manager button is pressed.

They will not be in the games data folder. The mod is stored by default in the Mod Organizer mods folder under the mods name, unless you have changed that location. MO will present the activated mods to the game when the game is run from MO.

Going by the posted picture there is only two instances of MO, one for Skyrim and one for FO4. The OP was trying to use NMM for FO4 after trying MO. So that is why I posted the steps to use only Skyrim nxmhandler only.

That should have worked. The only other thing I can think of is the actual file association in Windows was changed to Mod Organizer. Go to Control Panel, Programs, Default Programs and click on "Associate a file type or protocol with a program". That should get you to the Set Associations function. Scroll down to “.nxm†and see if Nexus mod Manager is the default handler. If it is associated with MO change it to Nexus Mod Manager. This is the way it is set up on my system. When MO asks to associate the nxm protocol it does not change in the set file associations area. I hope this works as I am out of ideas.

What happened when you did this, did NMM open?

A couple of things you can try. But before that which internet browser do you use? Do not run nxmhandler.exe from the fallout4 version of MO. Shut down both MO and NMM. Run NMM as an administrator, select the fallout4 game and when it opens go to the settings tab and uncheck the option to associate NXM URLs. Click OK to close the dialog, but do not close NMM yet. Go back into settings and put a check back into the box and OK and close NMM. This will associate the NXM links with NMM. You will be able to use the Download with manager button. Try it now to see if it works. Do not start MO or run the NXM handler at this time. This will tell us if there is something else going on with your system, Steam or NMM. If all is good run your Skyrin version of MO. It will ask to associate with the NXM links. Select yes and close MO. Run the nxmhandler.exe from the Sykrim version of MO that you are using. When it opens make sure the primary handler is for the skyrim version of MO. Ckick register active if it is not. I am assuming that your entries will be the same as the picture, just make sure your fallout4 is pointing to NexusClient.exe. Close the nxmhandler.exe. Depending on which browser you use, you may or may not get a dialog asking which application to launch. If you do select nxm. The one I attached is from firefox.

Hi 1. Wallpapers are from my personal photos, my dog mostly and I don't care for avatars. Old person here. 2. 27in GSync monitor TN plus two other 24in on main computer. 3. see 2 4. Old person, not much to care about. 5. Old person, can't remember them. 6. I don't drink soda that much. 7. Norton AV has served me well over the years.

Has anyone had any luck with FO4Edit? It locks up on me saying, [random plugin] start processing, and I have to close FO4Edit, which then crashes MO.

The window geometry is stored in ModOrganizer.ini in the same folder as the MO executable. You may have a corrupt ModOrganizer.ini or Windows UAC may be preventing the ini from updating. Close MO and try renaming ModOrganizer.ini and restart MO, MO will create a new file. You will have to re-do executables and some settings in the configuration area.

Just and FYi / observation. Alpha3 has two selections on a clean install. The user will be asked to select from two options, portable or Regular. Portable will put everything in one directory and one allow one game. Regular puts data in a separate directory and allows multiple games. The alpha 3 regular selection appears to use Users\username\AppData\Local\ModOrganizer to store the configuration files, ModOrganizer.ini, and the downloads, logs, mods, overwrite, profiles and webcache folders. These can be changed once the UI is up from settings. This will also reset your current install alpha3, if you have multiple installs of MO, if you run the UI from another place to just test new features like new instances. I originally copied a3 over a2 and then ran a3 from another location. When I went back my original was changed. There were no mods, downloads or profiles. ModOrganizer.ini will be absent from the main ModOrganizer2 folder when regular is selected.

Mo 2.0.3a is up on github.

As mentioned earlier, not everything is working in alpha2. It might help to copy plugins.txt from your active profile to C:\Users\username\AppData\Local\Fallout4. Also restarting MO will force an update to the game folder structure. I have seen changes made not take until a restart has been done.

There is still a lot not working in the alpha at the moment, that is why we are kicking the tires so to speak. There is a workaround for this though. The following was compiled from LOOT shows missing master when ran through MO2 only on the issue tracker for MO. Mod Organizers redirect or magic update is not fully working at the moment. LOOT and many other programs use plugins.txt in %LOCALAPPDATA%\<game name>\. There is a missing master warning in LOOT 64 bit when run from MO and the sort will not show up in MO. Short term use of LOOT in MO 2.0.2a. This must be done in order for the sort to show in MO. Go to the LOOT - Load Order Optimisation page and click on the files tab. In the Old Versions section download the last file, LOOT v0.8.1-38-g7c4fe9f - Snapshot (64 bit test version), to your computer. Once downloaded extract it to a LOOT64 folder in the Fallout 4 directory or any directory I imagine. In MO set up the executable as usual. To properly use LOOT in MO 2.0.2a press the LOOT executable from MO. MO will lock as the executable is run. When LOOT opens up fully switch to MO again and press the unlock button on the small dialog window. Switch back to LOOT and make your custom edits to file order or sort. When finished exit LOOT and either use the refresh from the drop down next to the profile selector or switch from the plugins tab to another tab and back for the sort to show up in MO.

Not sure if "wisdom suppository" is a complement or not.

The key word here is "Configurator". Ctrl-F won't work there, only in the ini editor.

I believe Tannin has said in the past that the query info has a finite number in what it reads, so it is possible that the name is just outside of what is returned.

Just an FYI, the STEP forum is a repository of information and the general rule of thumb here is to not delete posts, unless it is spam, no matter how insignificant the information is. Also it would be nice if the poster did not delete the text in a post so that others arriving after the edit can determine what is going on. Use an "EDIT:" after the original post and maybe strike through text if you solved your problem.

Shut down MO and use Windows file explorer to go into the ModOrganizer\webcache folder and delete the files and folders there. Restart MO and you should now be able to log in with the new info.

Go to the MO page on the Nexus,click on the donate button.

It looks right. Be aware that you may have to restart MO a2 after you enable or disable graphic mods as noted in the bug tracker 409. The auto refresh seems to be broken as I can reproduce this. Also note that MO will rewrite the sResourceDataDirsFinal line when the game is launched. So any modifications to that line will be overwritten.