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.

I think so, I'm using version 2.1.3 Mine is installed in Z://ModOrganizer/ Just tried, still not working as intended :(

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

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] closeI 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?