Problem when launching Oblivion via OBSE

[Streix]

For some reason I can't play the game whenever I load the game up with OBSE. I get the regular Bethesda logo loading but when I press Esc to evade all the logos from loading it seems to freeze for a few seconds and I never see the usual red loading bar you see when you start the game. And I've tried having all the logos show up and pressed nothing, still the same problem.
Instead it jumps straight to the menu and the "intro movie" where you have the background showing up as the worldmap. And this is where nothing happens. I can't even see the "New Game", "Load Game" buttons. It's just the map scrolling in the background.
Starting the game w/o OBSE works fine and the only mod I have that requires it to start is OBGEv2 so I'm guessing it has something to do with that.
Looking at the "obse.txt" it creates I can't see anything suggestion something would be wrong. Then again I'm a noob and have no idea how mods or anything works.

This is what the txt file tells me.

Spoiler:

OBSE: initialize (version = 20.4 010201A0)
oblivion root = C:\Program Files (x86)\Bethesda Softworks\Oblivion\
plugin directory = C:\Program Files (x86)\Bethesda Softworks\Oblivion\Data\OBSE\Plugins\
checking plugin C:\Program Files (x86)\Bethesda Softworks\Oblivion\Data\OBSE\Plugins\\OBGEv2.dll
SetOpcodeBase 00002100
RegisterCommand GetAvailableGraphicsMemory (2100)
RegisterCommand GetScreenWidth (2101)
RegisterCommand GetScreenHeight (2102)
RegisterCommand LoadShader (2103)
RegisterCommand ApplyFullscreenShader (2104)
RegisterCommand RemoveFullscreenShader (2105)
RegisterCommand SetShaderInt (2106)
RegisterCommand SetShaderFloat (2107)
RegisterCommand SetShaderVector (2108)
RegisterCommand SetShaderTexture (2109)
RegisterCommand ForceGraphicsReset (210A)
RegisterCommand LoadTexture (210B)
RegisterCommand FreeTexture (210C)
RegisterCommand CreateHUDElement (210D)
RegisterCommand SetHUDElementTexture (210E)
RegisterCommand SetHUDElementColour (210F)
RegisterCommand SetHUDElementPosition (2110)
RegisterCommand SetHUDElementScale (2111)
RegisterCommand SetHUDElementRotation (2112)
RegisterCommand PurgeManagedTextures (2113)
RegisterCommand IsShaderEnabled (2114)
plugin C:\Program Files (x86)\Bethesda Softworks\Oblivion\Data\OBSE\Plugins\\OBGEv2.dll (00000001 OBGEv2 00000002) loaded correctly
patched
OBSE: deinitialize

Hoping someone here can help me.

[Andere]

Please check your version. The latest version of Oblivion is, to my knowledge, 1.2.0416, and you see it down left when the map appears, starting the game. If you have a lower version, check http://wiki.tesnexus.com/index.php/How_ ... th_patches, and install anything missing.

If you're up-to-date, the first thing to try might be the latest OBSE, http://obse.silverlock.org/. I don't know OBGE personally, but there seems to be certain problems...

That's about all I can give right now.

[Streix]

Yep, I do have all the latest versions of everything.
I think I've solved it now though. There seemed to be some conflict with the AA, because I tried turning it of and now it started. So I'm guessing the shaders doesn't approve of the built-in AA Oblivion uses as some of them seems to be using their own AA.

[KrisCrash]

It says v20 of OBSE is for developers, so it's not expected to be stable. Is there a specific reason you chose it over the stable v 19 release?

[Streix]

Nah, I tried v19 first and got the same error, I just switched to 20 to see if it would make any difference what so ever, which it didn't.

Might have been the ESP that made me crash as well because I had to disable both AA and the ESP in order to get the game running.

[KrisCrash]

Oh, I see well, I don't use AA myself so I wouldn't have noticed a conflict. AA doesn't allow HDR or screenshots enabled, so I think I know what I prefer

[BFG]

Personally I'd recommend disabling Oblivion's native AA and instead enabling it through your Nvidia or ATI console (assuming you have a dedicated graphics card!) That will allow you to run HDR and AA at the same time, and it's often a more efficient antialiasing anyway.