Mod Organizer 2 not hooking to NVSE process correctly

[LinkedUno]

Hi, I'm writing here because my MO2 is unable to keep the virtualized folder open in order for the game to load the mods correctly.

When I run Loot through MO the application correctly waits for me to close Loot before unlocking the MO executable, but if I run NVSE then MO immediately frees the virtualized folder as soon as the game launcher shows up.

I discovered this thanks to the MO messages section at the bottom: while when launching Loot the last message is

"Waiting for spawned process completion : LOOT.exe"

when launching NVSE the following messages are displayed immediately:

11:37:04 [D] Spawning direct process < "C:/Steam/steamapps/common/Fallout New Vegas/nvse_loader.exe" , "" , "C:/Steam/steamapps/common/Fallout New Vegas" >
11:37:04 [D] Waiting for spawned process completion : nvse_loader.exe (13672)
11:37:04 [D] Waiting for usvfs process completion : FalloutNV.exe (4640)
11:37:05 [D] Waiting for process completion successfull
11:37:05 [D] removing loadorder.txt
11:37:05 [D] close

I might need to specify that my MO2  and mod folder are located on my magnetic drive (Z://Mod Organizer and Z://FNVMods) while the game is located on my ssd in C://Steam/steamapps/common/fallout new vegas.

So, what did I do wrong?

[Majorman]

I'm not a specialist, but why do you even launch nvse_loader.exe? The 4 GB Patcher launches NVSE automatically for you every time you launch the game via FalloutNV.exe.

[LinkedUno]

  On 5/22/2018 at 11:13 AM, Majorman said:

I'm not a specialist, but why do you even launch nvse_loader.exe? The 4 GB Patcher launches NVSE automatically for you every time you launch the game via FalloutNV.exe.

Mmh I figured it wouldn't matter. Anyways, even if I run New Vegas directly the Launcher comes up and MO stops serving the virtual folder

[Greg]

Are you using the latest version of MO2 on Nexus or in #builds on discord? If you have Mod Organizer installed in the Steam or FNV folder, move it somewhere else (like C:\ModOrganizer) outside the Steam and game folders installing ModOrganizer in the Steam or game folder is known to cause issues. Have you also tried to disable your antivirus to ensure it isn't interfering?

[LinkedUno]

  On 5/22/2018 at 9:14 PM, Greg said:

Are you using the latest version of MO2 on Nexus or in #builds on discord?

I think so, I'm using version 2.1.3

  Quote

 

installing ModOrganizer in the Steam or game folder is known to cause issues.

Mine is installed in Z://ModOrganizer/

  Quote

 

Have you also tried to disable your antivirus to ensure it isn't interfering?

Just tried, still not working as intended :(

[Greg]

You might try one of the latest 2.1.4 dev builds in #builds on discord to see if this solves the problem. If this doesn't solve the problem, you can discuss the issue in #issue-reports.

[LinkedUno]

I managed to solve the issue myself by running the game without having steam open. MO2 Launched the steam.exe executable I placed in the game folder and installed the whole steam platform again in my C drive. So, if I run steam from C now I can properly play the game but if I instead run it from Z then I can reproduce the error I had.