Bet you've never seen anything like this. 1:04 video included.

[Scourched]

So, I am not going to bore you all with a wall of text going on about nothing. Here is the issue: the WEIRDEST graphical glitch I've seen. I have no idea how to fix it, I've never seen it before, googling answers turned up nothing. I honestly don't even know how to describe it. What I can say is it at actually looks directional. Meaning the glitch shows up when moving in a certain direction when looking at the flora of the world.

 

What I've done and what I narrowed it down to: I did a full uninstall, started the game fresh with no mods, and no problems. One by one I turned my mods on until they all were on, and, no problems. Then I go and put my ENB in and that's when it happened. Before the uninstall, I had this issue. Taking all the ENB files OUT still did not fix it, except I'm almost certain I did not take out the d3d9.dll.

 

So now, after an uninstall and all mods in WITHOUT this issue, I throw in my ENB files including d3d9.dll and this happens. I think the problem is specific to to that d3d9.dll file, but I could be wrong.

 

Yes my GPU drivers are up to date

Yes Direct X is up to date

 

So without further yammering, here it is: ( Most noticeable at the :45 mark. Look at the grass. I start off with it but it goes away as I rotate, and it returns when I come around to where I started)

PLEASE watch in 1080p and if full screen if you can, otherwise it is hard to see the problem.

 

http://www.youtube.com/watch?v=dRVJvo-Y4Ss

[slayerpaul]

It happened to me to. It was related to a specific ENB configuration, but sadly I don't remember which one.

 

After removing it the glitches disappeared.

[Scourched]

It happened to me to. It was related to a specific ENB configuration, but sadly I don't remember which one.

 

After removing it the glitches disappeared.

 

As in something within one of the ENB files? Any tips, clues, ideas on what it might be if you can remember? Or at least to get me on the path?

[MShoap13]

I actually get this quite often, and usually it's for more drastic than what you've recorded. It's almost like certain post processing stages of lighting get burnt in to the image. I'm on old ENB v0096 (it's just a bug-fix and doesn't actually alter the graphics). Unfortunately, the game crashes far more frequently, without ENB, than the post processing getting messed up, with ENB. So, I've just dealt with it. If you, or anyone comes up with something I'd be very pleased though.

 

I can say for certain that it doesn't matter what card you're telling ENB you have as I've had this issue with the "DeviceID" setting on 0000, 1040, 1041, 1080, etc. etc...

 

Edit: The only settings I even have turned on are:

[PROXY]
EnableProxyLibrary=true
InitProxyFunctions=true
ProxyLibrary=d3d9PPI.dll
[FIX]
IgnoreThreadManagement=true
IgnoreThreadPriority=true
FixGraphics=true
DeviceId=00001040
VendorId=000010de

 

Everything else is turned off. So, if it is setting related I'd suggest you start there.

 

ALso, that .dll I have proxied is a version of FXAA PPI. Probably an out of date version now as I've been generally pleased with the looks/performance of my game for some time.

Edited April 27, 2012 by MShoap13

[Scourched]

MShoap, thanks for posting that. I'm a little lost, though I think I followed most of what you said. Where exactly do you suggest I start in the settings? And Slayerpaul, does anything from what MShoap posted ring any bells?

[vertex23]

I have this happen as well. It's extremely annoying and just looks god awful. Interestingly enough though, it only occurs in with the red grasses in the plains outside Whiterun...

I assuming it was one of the textures I was using, I never thought it would be my enb that was doing it :(. Hopefully someone can find a fix for it soon.

[MShoap13]

First off, do you have a second .dll proxied through ENB? If so, start there. If not, we can definitively say that this isn't the cause. (If you do have one proxied, I'd appreciate if you post back and let us know what it is).

 

Beyond that, it's got to be one of the three other functions I have enabled under the [FIX] heading of my config.

 

I've already ruled out VendorID and Device ID when I was testing these settings for maximum performance. (I have a GTX 560 TI though telling ENB it's a 550 TI grants me a very slight bump to FPS. Telling ENB nothing (0000), or any of the following cards resulted in no performance gain or loss (450,460,465,480,560 TI,570,580). Telling ENB it was any of the following cards resulted in a noticeable decrease to performance (485,550,560,590,580x2). These are just off the top of my head, but I know I didn't try any mobile/ultra low end card IDs. I had to Google the DeviceIDs... Individually...