Many choose c:Oblivion, or c:GamesOblivion, as their alternate install location. If you are running Windows Vista or later, make sure to install Oblivion OUTSIDE of the Program Files directory.
Step 1: Install Oblivion and any expansions and official mod packs you have for it. Meanwhile, just improvise with the instructions here. I'll add a second guide specifically for Skyrim once there are more mods and utilities out for it. This guide was written for Oblivion, but also mostly works for Skyrim. If you already have the game installed, re-installing clean is optional I have simply found this method to be the best way to prevent problems in the future.
If you are brand-new to Oblivion mods or just looking for a clean start, use this guide to learn how to set up Oblivion for mod use. They must have just added it locally, compiled, and threw it on their site. Interestingly, I don't see GOG's version on there. So, if there's a new release you have your hands on in 30 years and the devs have fallen off the face of the earth, you can still have your Oblivion and OBSE if you take a copy of that, modify, and compile it :) Specifically the /obse/loader_common/EXEChecksum.cpp file. Basically it seems they only care that you're running the right patch version. However, looking at the source code, it seems to have a pretty extensive checksum list of versions/'releases' of the executable. They *aren't* DRM police, but they *do* have OBSE not load if it doesn't recognize the exe. Marmormurmel: And why exactly did OBSE act as a DRM Police? Your response made me look back into this, as I had checked into it years ago as I'm big into future-proofing things (as everyone here is I'm sure). Pbnjoe: Yep, since it doesn't have DRM in it it's different to all the prior releases, and OBSE hashes Oblivion.exe and checks it against a list of hashes baked into itself. The latest version is for both Oblivion and Shivering Isles įor errors, we generated in the Oblivion folder a file named obse_loader.log where error reports are entered by OBSE. You have to careful that you download the correct language version. You must compile the game on the latest patch was patched, as Shivering Isles, if installed. When the Steam version of OBSE is higegen automatically during normal start of the game started. Next you must run the file obse_loader.exe. If you have the download version of Oblivion, it is not generally OBSE. This is Standartmauig C: Program Files Valve Steam steamapps common oblivion
If you have a Steam version, you must file the obse_1_2_416.dll, obse_editor_1_0.dll, obse_editor_1_2.dll and copy obse_steam_loader.dll into the game directory. You must obse_1_2_416.dll the files, obse_editor_1_0.dll, obse_editor_1_2.dll, and there obse_loader.exe copy, where the oblivion.exe is. I'm assuming that you have a normal retail version, so no steam or Dircet2drive download version. In the Read Me is not that I have this mark or I've overlooked that. I'm missing but the addon (Shivering Isle). Ware Perhaps worth mentioning that I am not particularly versed in English and my translator only offer some non-representational gibberish. There is a folder in the Installer heiut, but since a OBSE.NSI is file inside and I can not open. I learn from the Read Me not find the other files must go. But this problem I've only been on it is obse. It looks like that when I start the game as normal. Like I said, the current versions do not have a setup file.
Incorrect driver installations or too weak graphics cards may be the cause of Darfur, or incorrectly installed mods. I've heard from Lila Verfarnungen, but in another context. Is this weird coloring every time you start OBSE?Ĭan you describe your system from her performance.