pistachioman25

UPDATE--SOLVED: Turned out, the issue was the Official DLC High Res Textures. MO couldn't open the .bsa's, and I guess stopped setting any other mods up. When I took those files out, everything worked fine again.

I don't think this is an issue with .NET. I haven't changed my OS, my .NET 3.5 never went inactive, but ever since I've been updating my mods the last couple days, none of my executables have been reading from MO's virtual data folder. So far I've only been testing LOOT and Bodyslide. LOOT reads only the main files and steam DLC Bodyslide only detects the files in its own folder. If I copy files directly into the bodyslide folder, it reads them, but will not read files in the virtual data folder. I have reinstalled the executables, then reinstalled MO completely, but still have the same issue. Is this a bug in v1.3.8? Or does anyone have another suggestion? p.s. Yes, yes, yes, I am running the executables through MO, just like I always have, and they always used to work just fine. (since I know the next post would be suggesting that) UPDATE--SOLVED my issue: Turned out, the issue was the Official DLC High Res Textures. MO couldn't open the .bsa's, and I guess stopped setting any other mods up. When I took those files out, everything worked fine again. Guess it turned out to be unrelated, but I honestly thought it wasn't.

I am having the same issue with any executable I run through MO. So far I've only tested LOOT and Bodyslide, but neither one is reading from MO's virtual drive, and thus not detecting any other mods installed through MO. Is this a bug with the latest update (1.3.8) of MO? I tried completely reinstalling MO and the executables, with no luck. .NET 3.5 is active. I set up the executables properly, through MO.