Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
In MO go to settings -> workarounds and set the load mechanism to Script Extender.
Start the Modify executables dialog to create a new executable.
Give the executable a title, f.i. Steam.
In the Binary box navigate to where you have Steam installed.
In the arguments box add the following argument -applaunch 22330.
In the selector next to Run select your new executable and press run.
I'm at work right now but I'll try that asap. I don't know how to do any of the steps after set load mechanism to script extender though.
Start the Modify executables dialog to create a new executable. Just next to Run button there is the selector to add custom executables. Here: https://imgur.com/a/9NywpGw
I called mine Steam.
Then press Edit and add Steam.exe, mine is in D:\Games\Steam: https://imgur.com/a/PTGmONP
You can ignore Start in box.
Add the following argument to the argument box as well -applaunch 22330.
After all of that just choose your newly added Steam.exe and run the game through it.
Those are just simple steps, there is nothing to break literally.
May be you guys just should use Wrye Bash or/and OBMM to make it easier.
I would guess that MO is now recognising that you're running the game through Steam, and therefore you don't need a separate launcher option for OBSE. This is because Steam's overlay should be starting OBSE for you.
If that's not happening, then make sure that the Steam overlay is active: you should get a pop-up telling you so ("Access Steam Community blah blah...") shortly after the game starts. If that's not happening, first check your Steam settings, and then have a think about which other programs might be interfering. Security tools such as BitDefender are notorious for blocking the overlay.
Bear with me, I'm sure you've tried at least some of this.
1. Did I install it in the right directory? Are your .dll in the Oblivion directory and do you have an obse folder within the data folder? o.k.
2. Am I certain OBSE is / is not working? There are 2 ways to check this that I know of. First is to check your save games. You should find these in the path User/Documents/My Games/Oblivion/Saves In addition to the normal .ess and .bak files, you should also find .obse files. If you find .obse files there, it is working, otherwise not. Obviously, you need to have installed OBSE and played a bit and then saved for this to work.The second way, if somehow this does not work for you, is with a mod from the Nexus called OBSE test plugin. It's a simple .esp file. Drop it in, check it off, run the game and do what it says.
With that out of the way, the following have caused me issues with obse in the past -
3. Do you have Steam Overlay enabled? It is in the top left menu. Steam>Settings>In Game.
4. The Steam Overlay executable file (GameOverlayUI.exe) in the Steam (not the Oblivion) directory. Try setting that to 'run as an administator'.
5. Windows UAC. Do you have your games in the default C:/Program Files(x86)/... ? Moving programs out of this file structure can help a lot, if you already haven't. For example I have my Steam stuff in C:/Games/Steam/ ... etc.
The steam overlay is definitely active. But when I try to launch the game through steam, none of my mods work. I'm using the alternative start mod just so I can see right away if it's working or not. It's still loading me into the jail cell. The only software I can think of that might cause a problem is my VPN, but I tried disabling it and that didn't help.
To be clear on this: you're having MO tell Steam to launch the game, using the custom launcher command StreamWhenGuy got you to set up?