Jump to content
  • 0
Sign in to follow this  
UnknownK

Oblivion CTD when opening through Mod Organizer (Solved)

Question

Hey, long time modder, first time poster here.

 

I was having issues running Oblivion and Mod Organizer for a while and while testing was able to solve my issue. I own a retail copy of Oblivion and I've been trying to figure out how to run the two together after a clean install. I had a previous installation of oblivion I was trying to run through Mod Organizer, but because of problems with that I just decided to try and install everything fresh and see if I could get Mod Organizer to work. I saw some people report similar issues that didn't sound completely resolved on the OBSE thread so thought it might be useful sharing my experience. This report might be useful to someone suffering from similar issues so I figured I'd post it, just in-case someone sees it and it saves them the headache that I've been going through.

 

 

Clean install of Oblivion with patch 1.2.416 and OBSE v0021 installed. Mod Organizer 1.3.11 is installed. Hook.dll is not installed.

  • Standalone Oblivion.exe functions fine and game runs fine
  • Standalone obse_loader.exe functions fine and game runs fine (Proves that basic setup of Oblivion and OBSE is correct, OBSE status tested by checking for both .ess and .obse save file)

 

After previous tests, executables for Oblivion.exe and obse_loader.exe have been setup in Mod Organizer. Steam App ID left blank (Retail version). Load Mechanism is set to Mod Organizer.

  • Mod Organizer Oblivion.exe crashes to desktop within 2 seconds of startup (Reaches Bethesda splash screen then crashes)
  • Mod Organizer obse_loader.exe crashes to desktop within 2 seconds of startup
  • Standalone Oblivion.exe functions fine and game runs fine
  • Standalone obse_loader.exe functions fine and game runs fine

After previous tests, Load Mechanism is set to Script Extender. Hook.dll generated in OBSE Plugins folder.

  • Mod Organizer Oblivion.exe crashes to desktop within 2 seconds of startup
  • Mod Organizer obse_loader.exe crashes to desktop within 2 seconds of startup
  • Standalone Oblivion.exe functions fine and game runs fine
  • Standalone obse_loader.exe crashes to desktop within 2 seconds of startup

Deleting Hook.dll allows the standalone OBSE launcher to function properly again. The last thing I did was copy over my oblivion.ini file from the Documents\My Games\Oblivion folder and paste it in in the Mod Organizer profile. This seemed to solve the issue.

  • Mod Organizer Oblivion.exe functions fine and a test mod  installed in Mod Organizer worked fine
  • Mod Organizer obse_loader.exe functions fine and a test mod  installed in Mod Organizer worked fine
  • Standalone Oblivion.exe functions fine and game runs fine
  • Standalone obse_loader.exe functions fine and a test mod  installed in Mod Organizer worked fine

So if anyone is having issues similar to those described in this post, try generating a fresh oblivion.ini and copying that into the Mod Organizer profile.

Share this post


Link to post
Share on other sites

1 answer to this question

Recommended Posts

  • 0

If you have the retail version, ie. non-Steam version, you should not set the Load Mechanism to 'Script Extender', that is a workaround to get the OBSE to function with the Steam code.

ALL games need to be run at least once to generate a default set of INIs and upon running MO these are used for each new profile, there should be no need to manually move these to the current profile.

Deleting "hook.dll" is effectively removing the functionality of MO from that installation. That file is an integral part of the mechanism MO uses to manage each game it is used on.

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 Ghalium
      Title pretty much sums it up. I accidentally closed the MO2 application while running Oblivion. I hastily closed Oblivion once I realized what I had done, but after running Oblivion Launcher through MO2 again and starting the game up it crashes shortly after the Bethesda logo begins to appear.
      Still very new to modding and not entirely sure what is causing the crash but am aware that Mod Organizer must be open for the virtual file system to work properly. I do have my game stored in Program Files and understand it is advised not to be there, but the guide I followed in modding mentioned this should not be a problem and I personally did not experience any errors before mistakenly closing it today. TY in advance.
    • By Hal900x
      Hello there,
      First, just a quick note: forum link in the readme doesn't work, appears to direct to a non-existent page. Ok, now the questions: the ultra preset auto-selects vsync, is this intended? Second, the "recommended tweaks" button doesn't stay checked if you relaunch. I'm assuming this is not a problem, maybe that check box is a one-time thing, but it never hurts to check! I see other settings like actor fade are persistent, so I'm thinking everything is ok.
    • By Hal900x
      Hello all,
      I hope it's ok for a newbie to post here. It was the most relevant search result, so here I am. 
      I am following the guide at https://www.nexusmods.com/oblivion/mods/49898?tab=description and finding that the guide is anything but basic. Enough with the humorous asides.
      After installing OSR, I installed Bev's INI tweaks which modifies the former. However, I failed to delete the folders that weren't related to OSR before installing. I therefore uninstalled Bev's in Wyre Bash, deleted the extraneous folders, and reinstalled. I got a popup which, intending to read, I somehow dismissed accidentally. Looking through my Oblivion folder structure, it looks like it was just a backup of the ini settings I removed, hopefully. Then I reinstalled Bevs in Wrye Bash. At that point, OSR turned yellow. According to the Wrye Bash general readme, this means there is an underride. OK, that makes sense..must be as a result of my messing about. I'll anneal OSR. Still yellow. Refreshed all the data, just in case...still yellow. This concerns me, as I'm discovering that a single misstep when you're not knowledgeable can lead to much suffering. What did I do wrong, and how might it be fixed?
  • 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.