Jump to content
  • 0
Sign in to follow this  
malum

Cannot get OBSE to work with MO2, even following guides...

Question

Greetings, here is my situation/setup:

 

- Fresh Steam install of Oblivion (Only the 3 Unofficial Patches have been installed). 

- Both my Steam library and MO2 are installed on a dedicated gaming drive (F:) 

- Using only Mod Organizer 2 (No other mod management tool is installed at the moment).

- Installed OBSE v21 as per the Readme instructions.

- Oblivion starts up normally from Oblivion.exe and OblivionLauncher.exe without issue.

 

When attempting to start Oblivion from MO2 (either the oblivion.exe or oblivionlauncher.exe) I get a CTD after the starting logos play. The error is a generic Windows error message "Something has caused this program to stop working. Please close the program."

 

To try and resolve this I found these 2 guides online:

 

https://github.com/ModOrganizer2/modorganizer/wiki/Running-Oblivion-OBSE-with-MO2

 

and 

 

https://github.com/ModOrganizer2/modorganizer/wiki/Executables-window

 

They seem to overlap but in either case when I get to the part in the first link that says,

 

"Select Oblivion.exe, Check the Force Load Libraries and click on the Configure Libraries button. Check the checkbox on the line that says Oblivion.exe and obse_1_2_416.dll."

 
That simply wasn't possible for me, as the box with those options was entirely blank. There was no "Oblivion.exe" or "obse_1_2_416.dll" for me to select. So, I manually added both of those files using the "Add Line" option then made sure to check the checkbox next to the lines with the file names and ensured "Force load libraries" is checked as well. The results are the same CTD message upon startup. 
 
I tried shutting down and restarting MO2, no change.
 
I re-verified that I installed OBSE according to the Readme for the Steam edition of Oblivion, I did.
 
I tried deleting my Oblivion startup folder under /Documents and launching the game (bypassing MO2) to recreate the folder and oblivion.ini file, no change.
 
I tried rebooting my PC, no change.
 
I'm at a total loss for what I can do to move forward.  ::(:
Edited by malum

Share this post


Link to post
Share on other sites

3 answers to this question

Recommended Posts

  • 0

Sorry, I have not used Oblivion in a while, But I will try to help.

 

 

I have attached a short PDF for the process to follow. it is quick throw together so pardon the roughness of it.

 

I wanted to stop by and say thank you for trying to assist me. While the guide did not result in success, it did give me another venue to try and I learned a bit from the experience.

 

In the end I purchased a second copy of Oblivion from GOG.com which never had the same problem as the Steam version did.

 

I believe the Steam DRM layer may have been the root cause, although I cannot be sure.

Share this post


Link to post
Share on other sites
  • 0

Sorry, I have not used Oblivion in a while, But I will try to help.

 

 

 

"Select Oblivion.exe, Check the Force Load Libraries and click on the Configure Libraries button. Check the checkbox on the line that says Oblivion.exe and obse_1_2_416.dll."

 
That simply wasn't possible for me, as the box with those options was entirely blank. There was no "Oblivion.exe" or "obse_1_2_416.dll" for me to select. So, I manually added both of those files using the "Add Line" option then made sure to check the checkbox next to the lines with the file names and ensured "Force load libraries" is checked as well. The results are the same CTD message upon startup. 

 

I have attached a short PDF for the process to follow. it is quick throw together so pardon the roughness of it.

2020-03-21 Force load libraries.pdf

Share this post


Link to post
Share on other sites
  • 0

Thanks for getting back with that, come to think about it I have the GOG version also.

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 Mopotter
      1. I've been using MO 2 for years for 3 of my games, Skyrim, Skyrim SE and FA4.  No problems and yesterday  I know I did something wrong because the top line of items is missing and Skyrim SE is the only game I can access.  But I don't know what I did or how to fix it.  I've  uninstalled and reinstalled with no change.   Hoping someone has done this and can explain how to fix it.  

    • By Ayohaych
      Hey all.
      Sorry if this has been asked but I couldn't find anything.
      I got a Steam Deck recently and was in the process of setting Skyrim SE up with mods.
      Right now it actually works, however I can't seem to figure out how to launch Skyrim SE Launcher? I need to change settings so it runs better.
      When I open Skyrim from Steam, or use bottles to run Skyrim SE Launcher, it launches MO2. From there I have to select SKSE and hit run and it launches.
      If I click the drop down and select Skyrim Special Edition Launcher, it says an instance of mod organizer is already running.
      Any ideas on how I can get around this to launch the launcher so I can change my settings?
      It seems there is _SkrimLauncher.exe file that must of been automatically created by MO2, however when I run that with Bottles, and make changes, it doesn't seem to have the changes when I run SKSE.
      Thanks for any help!
    • By koopastroopas
      I have always used Wrye with MO but now on a fresh install of everything(Skyrim SE) when I try to rebuild the Bashed Patch I get an error saying "file not found, it may have been moved, edited or deleted. I have no idea what that means since it doesn't even tell me what file is supposedly missing. Any ideas as to whats going on here?
  • 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.