This guide has been updated for Oct. 2020, my login details were lost in Dec. 2019, so I apologize for my absence. The redistributable files have been updated as well.
If anyone is having issues, I am now available to check into the comment section here and there to assist people.
If anyone else is having trouble finding the uVideoDeviceIdentifier in your INI, its because you need to search for uVideoDeviceIdentifierPart1 and fill all of the other parts.
These are all good recommendations still in 2024, only with some exceptions! Read carefully!
Do not use: NAVC, OneTweak, Oblivion Stutter Remover and compatibility mode.
Instead, install OblivionDisplayTweaks and optionally dxvk (only the dll from the latest release download required in Oblivion's game folder - no mod manager). These fix all kind of issues which other tools would do before, while rather causing issues in today's Windows 10 and 11 versions. The reason for these is, that Win10 after some specific large updates which came later than this guide, created issues not possible to consider yet at the time this guide was written.
Also, use QuickAutoClean for cleaning mods, not the manual approach. Because, cleaning with other mods active, is not cleaning, as also would require to be done more than once for some mods, while QuickAutoClean takes care of all kind of possible issues and works even better in latest TESEdit versions.
Would this help the type of crash to desktop that happens upon trying to access a certain area... and crashing over and over again in same area? Essentially area off limits? Yet you can turn the other way and play just fine
nope, what you describe is overwhelming likely to be either and instance of corruption in the saveline, a corrupted asset file or object, or an installation error. not a game bug.. Start by looking up or saerching for fixes to "corrupted spawn point" if no success there, try disabling .esps one at a time and testing the crash.
I quite enjoyed this guide. I couldn't use the affinity registry because I launch Oblivion from MO2 and not from Steam.
However, I did have the same problem as: DeathComesSilently
I turned on compatibility mode for Windows XP SP3 for Oblivion exe, OblivionLauncher exe and the obse_loader exe. The game wouldn't launch at all. It kept crashing on boot up. Wouldn't even show the first video that shows Bethesda Softworks A ZeniMax Media company logo.
As soon as I turned off compatibility for all 3 exe files. My game launched as if nothing happened.
Just thought I'd share this if anyone else has the same problem.
Great guide overall; only problem I had was that setting compatibility mode to Windows XP Service Pack 3 for my .exe's would cause instant crash on game launch until I turned it off. Thought I borked my game for a moment until I retraced my steps to figure it out.
Regarding section 8...is there a way to set obse_loader to automatically execute that context menu option without needing to right-click and select it? Because I run the program through a mod manager, which obviously doesn't allow for right-clicking to use context menu options.
129 comments
If anyone is having issues, I am now available to check into the comment section here and there to assist people.
"HDR cannot be enabled with AA on, and vice versa. "
But doesn't Bethini do just that?
Do not use: NAVC, OneTweak, Oblivion Stutter Remover and compatibility mode.
Instead, install OblivionDisplayTweaks and optionally dxvk (only the dll from the latest release download required in Oblivion's game folder - no mod manager). These fix all kind of issues which other tools would do before, while rather causing issues in today's Windows 10 and 11 versions. The reason for these is, that Win10 after some specific large updates which came later than this guide, created issues not possible to consider yet at the time this guide was written.
Also, use QuickAutoClean for cleaning mods, not the manual approach. Because, cleaning with other mods active, is not cleaning, as also would require to be done more than once for some mods, while QuickAutoClean takes care of all kind of possible issues and works even better in latest TESEdit versions.
Start by looking up or saerching for fixes to "corrupted spawn point"
if no success there, try disabling .esps one at a time and testing the crash.
However, I did have the same problem as: DeathComesSilently
I turned on compatibility mode for Windows XP SP3 for Oblivion exe, OblivionLauncher exe and the obse_loader exe.
The game wouldn't launch at all. It kept crashing on boot up. Wouldn't even show the first video that shows Bethesda Softworks A ZeniMax Media company logo.
As soon as I turned off compatibility for all 3 exe files. My game launched as if nothing happened.
Just thought I'd share this if anyone else has the same problem.
EDIT: when I run Oblivion from Steam I get UAC every time! That has never happened before. Maybe that's why it doesn't load OBSE?
edit again: now I can run the game from obse loader, but I still get UAC