LOD flicker issue

[slinkyinmotion]

Bumping for interest, I am having the exact same problem. I am using an ATI 5780 HD card with all the settings left to default and defined by the game.

[Tomlong54210]

Bumping for interest, I am having the exact same problem. I am using an ATI 5780 HD card with all the settings left to default and defined by the game.

Have you tried upgrading your video card drivers? Do you have OBGE installed?

 

 

--Tomlong54210

[MotoSxorpio]

If you have more than one OBGE version in the Oblivion\Data\obse\plugins folder, remove all but one. OBGE is necessary for ScreenEffects, and you can use OBGEv2 by renaming it to OBGE without problems. However: OBGE is HDR only and can use AA, whereas OBGEv2 and up are not limited, but don't support AA. If you have more than ScreenEffects.fx shaders in the Oblivion\Data\Shaders folder, move them and leave ScreenEffects.

 

You can replace the shaders one at a time to find the culprit. I might guess it being a Depth of Field type shader, if shaders galore are there (from an OBGEv2 or v3 install).

 

In my opinion, with just Screen Effects, Ambient Dungeons and Enhanced Seasons: OBGE packed with ScreenEffects does the best job as there was major code changes between OBGE and OBGEv2...not to mention how much changes in OBGEv3 (recommend not using for Screen Effects-I couldn't get it to work with OBGEv3). These are only suggestions without knowing your OBGE setup. Hope you get it fixed, I would go nuts with that lowering and raising of water. o_O

Edited July 10, 2011 by MOTOSXORPIO

[Tomlong54210]

You don't need to rename the OBGEv2.dll OBGE.dll, and I don't recommend it, since that would make keeping track of the updates of the newer one more confusing. You certainly don't need to do that for ScreenEffects. Some mods, such as Realistic Health, apparently have OMOD scripts that depend on the naming of the file, but you can simply snip that error out of the script. The name of a DLL file is otherwise meaningless. Mods have no awareness of the naming of the file.

 

In fact, the quickest way to prevent ScreenEffect and mods that depended on the old version from installing it is to add the line "DontInstall OBSE\\Plugins\\OBGE.dll" at the top of the OMOD script, or just install it with BAIN, and say no when asked to install "OBGE.dll".

 

 

--Tomlong54210

[Datashocker]

Hey, look, my old thread is back. I still haven't found a fix for this, sadly, and have it extremely badly in Fallout: New Vegas. It's not quite as bad in Fallout 3.

Anyways, a temporary workaround is to open up your INI file, and search for the line "fneardistance". By default it's set to 10, however some mods, most notably Deadly Reflex, recommend that you set it to 0. I've noticed that the more this value is decreased, the more extreme the flickering becomes.

Note that this only works well for Oblivion. In Fallout 3 and New Vegas, the default value is 5, and changing it to anything higher makes the guns clip with the camera in iron sights mode.

[SomeWelshGuy]

It's a long way and it will take a while, but type "tfc" in the console and free-camera fly towards the area that's flickering. Does it stop flickering after a certain time or does it stay flickering even when near?

[FaR2sToNeD]

I have this exact problem, this was the closest thing to an answer google could find.

 

:(

 

EDIT: Setting fneardistance to 10 does minimise the flickering, higher values stop it but mods like DR6 set it to 0 for a good reason, now my arms and legs fly out infront of me when I attack (with no body attached).

 

So it's a choice, no DR6, dodgy water or dodgy combat moves. Sods law.

Edited November 1, 2011 by BingoMorris