MO 1.3.8 does not hook OBSE Plugins at all

[adelinadragonborn]

Good day.

 

Today I finally installed MO for Oblivion, but encountered a problem with *.dll plugins not loaded by MO. All the rest of the mods are loaded fine, except OBSE plugins.

 

I have latest non-steam version of the game (GOTY), latest OBSE (0.0.21.4) and MO (1.3.8), tried to switch Load Mechanism to Script Extender, but nothing helps. I was forced to move Plugins folder directly to Oblivion Data folder to make it work. It is not a neat solution in this case.

 

Although, MO shows all the plugins properly (in the right panel).

 

Edited August 10, 2015 by adelinadragonborn

[hishutup]

I think OBSE .dlls have to be installed out side of mo regardless.

[adelinadragonborn]

I think OBSE .dlls have to be installed out side of mo regardless.

I see. Is it possible to be fixed in future? What prevents .dlls from loading with MO?

[hishutup]

What prevents it, is the way OBSE is injected.

 

I would figure that it could be fixed one way or another but I know that there are other more important matters in terms of dev work for MO.

One of the other MO guys will probably have more accurate info.

[GrantSP]

Yes there may be a way for the Oblivion game engine, and OBSE plugins, to be hooked but that will require a complete re-write of the code-base for the Oblivion plugin. This isn't something high on the list of priorities for the author of MO.

 

All the code is available for others to see and change if they desire, but I wouldn't hold my breath.

 

For non-Steam users the methods used currently work very well. As @hishutup mentions though there are other issues that afflict the Steam version.

[adelinadragonborn]

What prevents it, is the way OBSE is injected.

 

I would figure that it could be fixed one way or another but I know that there are other more important matters in terms of dev work for MO.

One of the other MO guys will probably have more accurate info.

 

Yes there may be a way for the Oblivion game engine, and OBSE plugins, to be hooked but that will require a complete re-write of the code-base for the Oblivion plugin. This isn't something high on the list of priorities for the author of MO.

 

All the code is available for others to see and change if they desire, but I wouldn't hold my breath.

 

For non-Steam users the methods used currently work very well. As @hishutup mentions though there are other issues that afflict the Steam version.

Thanks, guys. 

[GSDFan]

You say you have the non steam , retail, version of Oblivion. do the following, I don"t have this version so I can't test it:

 

1. Copy obse_1_2_416.dll, obse_editor_1_2.dll, obse_loader.exe and the Data folder to your Oblivion directory. This is usually in your Program Files folder, and should contain files called "Oblivion.exe" and "OblivionLauncher.exe".

2. MO Should be set to run as Mod Organizer as the load mechanism.
3. Run oblivion by running obse_loader.exe from the Oblivion directory as a shortcut in MO run section.

[DoubleYou]

You say you have the non steam , retail, version of Oblivion. do the following, I don"t have this version so I can't test it:

 

1. Copy obse_1_2_416.dll, obse_editor_1_2.dll, obse_loader.exe and the Data folder to your Oblivion directory. This is usually in your Program Files folder, and should contain files called "Oblivion.exe" and "OblivionLauncher.exe".

2. MO Should be set to run as Mod Organizer as the load mechanism.

3. Run oblivion by running obse_loader.exe from the Oblivion directory as a shortcut in MO run section.

I have disc version. This will not work. You MUST use Script Extender to as the load mechanism in Oblivion.

[GSDFan]

OK good to know. With the non-Steam version how do you launch the game then? From MO with obse_loader.exe shortcut or clicking the exe in the directory?

 

I ask because I am trying to figure out if there is a circular hook going on if launched from MO. MO launching obse_loader.exe then obse_loader.exe launching stuff down the line then MO again via script extender setting. That may explain the double launcher problem.

[DoubleYou]

The double launcher problem is caused by the fact that MO currently inserts the wrong App ID. That is why you must change it to 22330. If it doesn't possess the correct App ID, MO will attempt to launch Oblivion with the wrong App ID, fail, and Steam will automatically relaunch it with the correct App ID, but MO will not hook it then, causing the issue with no mods loaded.

 

Disc users launch OBSE loader. That's its purpose.

 

Technically disc users might not need to use the Script Extender workaround, but OBSE plugins still won't work unless you place them in data. We advise all Oblivion users to use Script Extender workaround because it appears to be necessary for Steam users, which works by launch Oblivion through Steam and not MO, and it causes the least confusion.

 

 

The big limitation of MO for Oblivion is not being able to manage OBSE plugins. Perhaps this will be fixed with the hook update that is rumored.

[psychotopia]

https://github.com/ModOrganizer2/modorganizer/wiki/Running-Oblivion-OBSE-with-MO2
Mod organizer 2 can now run obse plugins as of 2019 posting becuase i found this thread before i found the more uptodate info