Christopher_C

On the Nexus your second URL for "Support Forums" is a broken URL. User get the following; WOOPS, BAD LINK ... Sorry for the inconvenience, but the link that brought you here is invalid and needs to be updated. Feel free to contact us to get this fixed. — STEP

[Fixed] I did not find my answer on any forum. I found that a fresh MO 2.0.7 profile was able to launch with F4SE 6.0 + no issues with F4Edit as it found whatever ini files it needed. Create new profile (do not copy the corrupted one) Copy over from the old profile your load order and plugin files; lockedorder.txt, modlist.txt, hide_plugins.txt, loadorder.txt, plugins.txt Depending on where you place your saves local or in the profile you will need to move them.End game is I am up and running again without having to do much work. This one really sucked for lack of info on the web. Which is why I post how it got fixed. Don't be that guy that say "got it" and never spills the beans on his fix. Hope his helps some other Mod Organizer user until Vortex get done.

I am still digging on this... Interesting I also get an error in FO4Edit when launched in MO2 with "could not find ini". Then in the msg "Fatal: Could not determine my documents folder." Again both F4SE and FO4Edit launch outside of MO 2.0.7

Hmmm this looks to have been a better fit in the Mod Organizer 2 forum. my bad.

Hello, I have been doing my due diligence in searching Google for a RCA for this issue. I can launch F4SE_Launcher.exe and Fallout 4 comes up without an issue. It's just that I am a LONG time gamer with mods and MO 2.0.7 is my tool of choice. After the last update when I launch it from within MO right after is loads up the "Preparing VFS" the f4se_loader.exe cmd screen pops up with an error; (hover mouse to view error) I have ensured that all of my mods that utilize F4SE are up to date. It has been a month since the CC patching and still not finding a resolution. I am tech guy that has been modding games going back to NWN and I have dug my way out of most of my issues. This one is slamming the door in my face before I even get into the game. It works outside of Mod Organizer and no launching within MO?!? Even if I strip out all the Mods and just try to launch a base game from MO with no mods in place. I have removed all prior installs of F4SE and done the verify cache with Steam... No good. I was trying to recover the older Fallout4.exe through the Steam console process without success Any bones you can throw my way? This error has come up in the past for others so thinking it might just be simple I overlooked something. Don't bother posting crap like rebuild my Windows 10 and install every damn file over again. I have been building my own machines and working real IT helpdesks back when Daggerfall was cutting edge. Something with Mod Organizer is not playing nice with F4SE on my machine and it was looking fine even after the 1st CC patch came out. Thank you for you time.

At this stage in my modding experience I will use NMM for Morrowind and Dragon Age... I use MO due to the ease in use of tools and virtual break up of my mods. I run my games on 200+ mods at minimum and merge many of the small ones. My issues started when I broke out the use of MO2 with Fallout 4 and the older version with Oblivion, Skyrim and FNV (Tale of two Wastelands). At this point I uninstalled NMM and am trying to work out my conflicts with the four versions of MO on my machine. I am nearly onto a stable build of Fallout 4 while I wait for the next S.T.E.P release and then tackle Skyrim again. You guys are awesome here!! Big fan :)

I am eager to see how this plays out. I also have multiple games that are managed by Mod Managers. I use versions 1.3.11 for Skyrim and Fallout NV. Then use 2.07 for Fallout 4 and I run into the same error when I use the Skyrim or FNV versions. I can do work with nxmhandler.exe to get one of them working but it breaks the others. I have read several posts here to swap between them but it is a lot of overhead to update my mods. I have Mod Manager installed in each of the game directories so 3x separate versions.

Huzzah!! You are correct Sir! Path: \Mod Organizer\webcache\ *delete all* This resolved my issue. The Nexus is now reflecting any downloads and dates correctly. Sorry for the delay in reply but real life kept me away from my hobby. Much appreciated GrantSP!

I primarily use Chrome for all of my browsing and I cleared cookies and cache. This issue has been going on for sometime on my system when I look at my Nexus File Tracking history. I check the Nexus 2-3 times a week for updates and so I am not personally concerned that I am missing anything. Cleared Cookies & Cache in Chrome & IE11 Updated Nexus MOD Manager (had not used in six months) re-established priority as default and downloaded a few mods. They updates last update download on Nexus correctly. Launched MOD Organizer and took the default back to and downloaded a few Mods again to see if any updates occur on the Nexus. No changes to the dates when Nexus sends a Mod to Mod Organizer it does not acknowledge that I have downloaded it. Changed MOs versions of NMM in settings to no avail. :confused:

Hello, I have been using MO for about a year and have been very, very happy with the application and it's advanced tools for Mods. I recently noticed that my downloads from the Nexus are not registering? Last download could be broken but as I no longer use Nexus Mod Manager wondered if downloads directed to MO are not properly being tracked. I noted that my manual download of DynDOLOD shows correctly. What version of Nexus MM are people reporting in MO at this time? What would be best practice and could perhaps fix my issue? Thank you