Jump to content

TEs4Edit not working when called from Mod Organizer


Rudeman

Recommended Posts

I had been trying to get Mod Organizer to work with the Steam version of Oblivion, but couldn't get it to run OBSE so I installed my GOTY DVD version and Mod Organizer seems to work OK for it except for TES4EDIT. It did work for a while but now when I try to run it from MO, it crashes with a TES4Edir 3.1.2 message box saying "An error occured while loading modules. Editing is disabled. Check the message log and correct the error."

 

Checking the log shows this message:

[00:00] Background Loader: Fatal: <EStreamError: Cannot open C:\Oblivion\Data\Oblivion - Meshes.bsa.The system cannot find the file specified>
[00:02] Background Loader: finished

There is absolutely nothing wrong with the referenced meshes file but I wiped out Oblivion and installed it again. I still get the message. Oblivion works OK when called from MO and OBSE Tester installed from MO reports the correct version (21). Tes4Edit does work OK when not run from MO so I can clean the dirty DLCs that way but I might run into problems with the other mods. Anybody else have any experience with this problem?

 

I have modded Oblivion with Wrye Bash but I WOULD like to run it with MO. One other thing I noticed with MO was that I think it seemed to corrupt the Obse-loader.exe file in the Oblivion folder so I had to set it to read-only.

Link to comment
Share on other sites

Never noticed MO corrupting anything. I also used the DVD version a while back. How can you know it corrupted the executable, excatly?

 

Also, when using the Steam version (I moved the other way... yay), you need to set load mechanism to Script Extender in the worarounds tab, then launch Oblivion from Steam (and have all the OBSE files in the game folder so Steam will load OBSE). OBSE will then load MO's file system via the hook.dll thing that should have appeared in your OBSE plugins folder. So Steam version works with MO, just remember to (I like lists, makes it easy to see which points are done and how many there are in total... :P ):

  • reset .bsa timestamps so replacer mods work (not related to MO, but just to make sure it is not AI when things go wrong)
  • install OBSE
  • change MO load mechanism to script extender
  • let MO handle archive invalidation (open the profiles list, select your profile and tick the box at the bottom, you might need to do this a few times until it sticks)
  • install all OBSE plugins in the actual plugins folder (they do not work via MO)
  • launch Oblivion from Steam (also custom batch files with the -applaunch argument for Steam work, as long as Steam is the one to start Oblivion, so that the Oblivion launcher appears, then click play)

As for that error, have you ticked, in the archives tab of MO (next to saves and plugins tab), the "let MO handle archives" tab? Also, do you use anything else to handle archive stuff (like if you have Archive Invalidation enabled elsewhere, that might conflict)? Someone else also ran into this issue, and I do not remember them solving it. It should work as long as you have MO handle all the archives and such. If you use something like WB and OBMM for installing mods or doing something else (other than WB for Bashed Patch, savegame and load order management), then there might be some conflicts somewhere. And that is where I cannot help. Or if it is related to your operating system, I have Win 10 ready but I still use Win 7 for basically everything.

Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...