Can't get TES4LODGen to work in Mod Organizer.

[Dahveed]

I've recently decided to do a full re-install of Oblivion, because my /data folder and mods were a giant confused mess and I was having issues.

 

Since I had such an easy time with Mod Organizer for Skyrim, I thought I'd use the same tool for Oblivion. So far everything has worked grand... except now I'm at this one final hurdle. I can't run TES4LODGen.exe to run through MO.

 

It starts up, reads all my plugins, but then says this:

 

"An error occurred while loading modules. Editing is Disabled. Check the message log and correct the error."

 

So I check the log, and it says:

 

"Background Loader: Fatal: <EStreamError: Cannot open D:\SteamLibrary\steamapps\common\Oblivion\Data\Oblivion - Meshes.bsa.The system cannot find the file specified>"

 

This is bologne, as I open up that folder and the Oblivion - Meshes.bsa file is indeed where it ought to be.

 

I've even tried copying the file and making it into a "mod" to put into MO's load order, to no avail.

 

Does anyone have a solution to this?

 

Thanks in advance.

 

EDIT - I just want to add that if I move the .exe file to my /data folder, it will then detect all the .bsa archives correctly, but then of course will not detect any of my mods in MO, defeating the purpose of using the tool to begin with.

Edited April 27, 2015 by Dahveed

[Surilindur]

I have had TES4LODGen 3.1 work just fine with MO 1.3.4, so I can prove it works. Or at least I can claim so, as proving it might be difficult. :)

 

But it is indeed possible to have them work together perfectly. There were some problems previously (lod generation was slow and basically stopped long before 10 000 cells were processed), but at least with MO 1.3.4 and TES4LODGen 3.1 everything seems to work just as well as it did before I found MO, when I used Wrye Bash to install mods. So it might be worth checking which versions you use. Not that it would be the cause behind the TES4LODGen error, though...

 

The issue with .bsa not loading could be caused by the .bsa not being loaded. In the archives 'tab' of MO, I have set MO to manage archives and then ticked all the not already selected archives. That way everything seems to get loaded. MO does not seem to automatically 'tick' any archives... You should also launch everything throuh MO (which, it seems, you are doing), as the script extender hook in 1.3.4 does not work - at least with Oblivion.

 

Hopefully that helps a little.

[Dahveed]

Thanks Philippe for the advice, unfortunately I already have all those checkmarks. I have the latest versions of everything, and I've tried both leaving my .bsa archives in the default /data folder AND having them checked off in MO's managed archives... neither method works.

[Dahveed]

I've solved the problem by simply copy/pasting all active .esps which add structures to Tamriel into the vanilla /data directory, and also copy/pasting all meshes and textures from AEVWD and tes4ll's file structures into oblivion\data.

 

I then made a new .rar archive with the distantLOD folder that tes4lodgen.exe create in oblivion\data and installed it as though it were a mod via MO. Now everything appears in game as it should.

 

I'm posting this in case someone else out there has this problem and needs a workaround. It's sloppy and time-consuming, but it works.

[Surilindur]

You mean having the little box checked, not unchecked, right? The post was not clear to me. But it could have just been me. The little boxes need to be checked so that MO loads the archive. If it is not checked, MO will not load the archive. I think MO might have the normal Oblivion .bsa files unchecked by default, so that they will not be loaded (unless it is the game that is launched, I think). Oops. I read your post again and understood it this time. Sorry. So you have had the .bsa archives checked in MO's archives tab (because that is when it loads them, when the checkboxes are not checked, MO will not load them).

 

Another idea would be to check the archive invalidation checkbox on the profiles menu and the clicking save or modify or whatever it was. Then you could make sure the Oblivion - Invalidation.bsa is also checked in the archives tab - if it is not by default.

 

You could also try running MO as administrator. Not sure if it helps, but at least it will eliminate all permission-related issues.

 

Why does it not work for you? This is odd. That workaround indeed defeats the purpose of using MO pretty efficiently. :smile:

Edited April 28, 2015 by PhilippePetain

[Dahveed]

Indeed if I had to do this for all mods then I wouldn't bother with MO at all. However I simply cannot imagine ever using a different tool ever again now that I have grown so accustomed (and indeed spoiled) by MO's efficiency and cleanliness. This issue seems to be very quirky and unique as I can't find anything about it anywhere else on the net, so it's probably just one random glitch or oversight somewhere... I won't complain because so far everything else has been 100% smooth, kudos to the MO team for making such a great tool.

 

I will gladly suffer this one small annoyance in exchange for a smooth modding experience. And honestly it only took about 15 minutes.

 

Thanks for the suggestions but nothing works... I'm just going to sweep this problem under the rug and hope nobody notices :smile:

 

cheers.

Edited April 28, 2015 by Dahveed