Jump to content
  • 0
Sign in to follow this  
PrimeNavigator

Script Extender option not appearing under Load Mechanism

Question

I have OBSE installed in the Oblivion directory. In Mod Organizer, when I look under Load Mechanisms Script Extender does not appear. It seems to be working however when I load from MO no esp.s handled by MO are recognized. I've tried reinstalling etc. to no avail. Any thoughts?

 

- Thanks

post-7312-0-41935400-1435615374_thumb.png

Share this post


Link to post
Share on other sites

11 answers to this question

Recommended Posts

  • 0

Oblivion is installed to the Steam directory on the C: drive. Mod Organizer is installed on my desktop. I also tried installing it to the C: Drive program files. Same result.

Share this post


Link to post
Share on other sites
  • 0

I found the problem. There was a duplicate installation of oblivion and MO was tethered to the extra one. Sorry about that. :)

Makes sense. Marked as solved.

Share this post


Link to post
Share on other sites
  • 0

So I thought that was the problem but I was wrong. I have removed both installs of Oblivion and mod organizer. Reinstalled Oblivion to the steam directory and the mod organizer to my desk top. I installed OBSE according to the instructions in the read me and still MO does not notice that it is installed and as such still does not provide the Script Extender option.

 

Edit : I now get the script extender option but when I run Oblivion OBSE does not kick in and I get a CTD as the main menu loads. (FYI, I have used LOOT, and loaded everything in TES4Edit with out incident.)

Edited by PrimeNavigator

Share this post


Link to post
Share on other sites
  • 0

Make sure all your BSAs are ticked in the Archives tab and the ArchiveInvalidation BSA is at the top.

 

I have heard that MO might not work with the Steam version, but I'm not sure.

Share this post


Link to post
Share on other sites
  • 0

It supposedly does but I have been unsuccessful in getting it to function.

Share this post


Link to post
Share on other sites
  • 0

The script extender functions differently in Oblivion. You can't run Oblivion from MO as the script extender will not load. The game need to be run from Steam and then the OBSE will be started. This is why there is a script extender function in the workaround tab.

 

I have been playing with the script extender over the last few days and can say it is spotty the way it works. It was working fine as I was adding mods in Hishys guide. I ended for the day and started the next day and had problems.

 

Make sure that the load mechanism is set to script extender in the workarounds tab and then mod in MO and run the game from Steam. Note that is you change the load mechanism from one setting to another MO will need to be restarted so it can copy or delete some files in the data directory. The Steam in game community needs to be enabled or BOSE will fail to load.

 

I have been testing a Steam launch from MO and it so far has been working for the OBSE plugins, limited testing though. I created a new executable and pointed the binary to Steam.exe. I added steam://rungameid/22330 to the arguments line. You can run the game from MO when setup this way.

 

When run you will get the game launcher. If you look at the data only the files in the vanilla directory will show up, MO has not been started yet. If you change options the current profile ini does not get changed, the one in my games will ge modified.

Share this post


Link to post
Share on other sites
  • 0

I have got it working. All I had to do was reselect the oblivion.esp in the binary field. Though the file path was correct it seemed to  need a refresh for some reason. MO now completely working with Steam GOTY edition.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

  • Similar Content

    • By sheson
      DynDOLOD DLL for Skyrim, Skyrim Special Edition, Skyrim Anniversary Edition and Skyrim VR
      So far all versions of DynDOLOD use the SKSE plugin PapyrusUtil for the optional dynamic LOD in the game. Starting with version 2.45 there is now the alternative DynDOLOD DLL available.
      The current DLL version is 2.45. It works with dynamic LOD generated by DynDOLOD Standalone 2.45 and newer.
      Read the ..DynDOLOD\Docs\DynDOLOD_DLL.html included in DynDOLOD Standalone for an explanation about DynDOLOD DLL, installation instructions (overwrite papyrus scripts of DynDOLOD Resources) and how it works.
      If there are problems with it, check DynDOLOD_DLL.html and the DynDOLOD FAQ first before posting.
      If a DynDOLOD.DLL version is required for a game version that is not listed below, request it in this thread. First, search this thread if it has been requested already, though. The future will tell how long it takes to release updates.
      Typically a new DynDOLOD.DLL is required for each new game version, but not each new SKSE version. For example a DynDOLOD.DLL compiled with SKSE64 2.0.9 also works with SKSE64 2.0.10 for the same game version.
      Nexus Downloads for DynDOLOD 2.45 and higher
      DynDOLOD DLL for Skyrim
      DynDOLOD DLL SE for Skyrim Special Edition
      DynDOLOD DLL VR for Skyrim VR
      Mega Mirrors:
      DynDOLOD.DLL + Scripts for Skyrim 1.9.32 (overwrite the papyrus scripts included in DynDOLOD Resources)
      DynDOLOD Scripts for Skyrim Special Edition and Skyrim VR (overwrite the papyrus scripts included in DynDOLOD Resources SE)
      DynDOLOD.DLL for Skyrim Special Edition 1.5.39
      DynDOLOD.DLL for Skyrim Special Edition 1.5.50
      DynDOLOD.DLL for Skyrim Special Edition 1.5.53
      DynDOLOD.DLL for Skyrim Special Edition 1.5.62
      DynDOLOD.DLL for Skyrim Special Edition 1.5.73
      DynDOLOD.DLL for Skyrim Special Edition 1.5.80
      DynDOLOD.DLL for Skyrim Special Edition 1.5.97
      DynDOLOD.DLL for Skyrim Special Edition 1.6.318
      DynDOLOD.DLL for Skyrim Special Edition 1.6.323
      DynDOLOD.DLL for Skyrim Special Edition 1.6.342
      DynDOLOD.DLL for Skyrim Special Edition 1.6.353
      DynDOLOD.DLL for Skyrim VR 1.4.15
    • By SalemMurders
      My SKSE launches correctly through MO2 but whenever I check to see if my mods are enabled, they're all disabled. None of the files are in an UAC-controlled file. I also made sure MO2 is not installed in Skyrim or Steam's folders. I always run MO2 as administrator as well.
       
      Edit: Some additional info. Both the Steam folder and the MO2 folder are on the same drive. Whenever I open a new profile, SKSE loads all the enabled mods without issue.
    • By dicksuckme
      [info] Attempting to create a game handle with game path "D:/steam/steamapps/common/Skyrim Special Edition" and local path "D:/skyrim/profiles/Default"
      [info] Initialising load order data for game of type 5 at: D:/steam/steamapps/common/Skyrim Special Edition
      [info] Attempting to open Git repository at: C:\Users\cabca\AppData\Local\LOOT\Skyrim Special Edition
      [info] Setting URL for remote origin to https://github.com/loot/skyrimse.git
      [error] A firewall may be blocking LOOT.
      [error] Git operation failed. Details: -1; failed to send request: A connection with the server could not be established\r\n: libgit2 error
      [error] Loot failed. Exit code was: 0x1

  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.