It said that windows was unable to save all the data for the files \MO2\logs\usvfs-_06-15-18.log, \MO2\plugins\data\OMODFramework.log, and \MO2\ModOrganizer.ini all lost data.After that I recieved the same message about plugin_python.dll failing to load from the last time it was started which i decided to skip.
I ignored it and carried on as usual until eventually when I tried to open mo2 I got back to back notifications from google about a delayed write failed that happened multiple times for several files. After a week or two of playing nv with the mods from the guid and installing several others with it, I got a notification from windows saying "mod organizer failed to load the plugin 'plugin_python.dll' last time it was started". One of those guides was viva new vegas which I was able to follow along easily.
ENDERAL LAUNCHER CANT FIND TESV MOD
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.Īs background info, A few months ago I got into modding for fallout new vegas and while doing so i searched up several guides on the topic. When launching NVSE the following messages are displayed immediately:ġ1:37:04 Waiting for spawned process completion : nvse_loader.exe (13672)ġ1:37:04 Waiting for usvfs process completion : FalloutNV.exe (4640)ġ1:37:05 Waiting for process completion successfull "Waiting for spawned process completion : LOOT.exe" I discovered this thanks to the MO messages section at the bottom: while when launching Loot the last message is 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. 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.
0 kommentar(er)
