In my never ending struggle to get ENB to be 100% stable in FSX I have been able to eliminate the menu crashing it was causing. But now since I have been able to use it on all flights I notice another issue I almost have resolved as well but not quite. And this is most definitely driver related. When I have the mod activated I can now enjoy hours of simming with this most excellent look but then I get a freeze (long stutter) usually lasting a few seconds and then black screen. The good news is that I can open the task manager and poof I am back in FSX all of a sudden and all works fine except my Ezdok key bindings. So if it happens in the VC which I am in 99.9% of the time no big deal really. By reducing the VC textures and disabling all in the enb.ini except bloom I have been able to achieve this almost stable condition. It has come along way from before when these freezes were unrecoverable now all the time I am able to resume FSX with the task manager.

 

Now in the event viewer the nvlddmkm is the culprit here and NOT d3d9.dll. It stops responding and then recovers. nvlddmkm is part of the driver and I have recently upgraded to 296.10. Is there any recommendations on the best driver to use for ENB? I am almost there, I just need to get rid of this minor annoyance now.

 

Thanks

Have you tried the latest 300 series driver? 301.24 beta driver supports your card. I run it on mine, and while I haven't had a chance to setup ENB yet, it's worth looking into.

I just worry about Beta drivers. Seems like many seem to be doing ok with it though. In the ENB.ini there is a setting ForceDisplayRefreshRate. I set this to enable or =1. I will test tomorrow from SCEL to SEQU. I have this hunch that this has something to do with vsync. Everyone has problems with menu crashes with ENB. But now that I got rid of my menu crashes I am having this weird issue. I also think that they are interconnected with menu crashes though. In other words I think there may be many variants of problems all connected to a root cause in FSX. Graphics load plays a big part in it. I just cant help think this may be something to do with screen refreshes in the driver. If I have the same issue after tomorrow I may try the beta driver.

Yea i went and tried that beta driver and go 6fps with it. Back to 296.10 with 30fps now. I grant the fact that something may have gone wrong with the install but I think I will wait for the certified version.

I am giving up for now. I found these Nvidia monitor settings to work pretty well with a slightly modified "shade default" preset. We could call it "Poor man's ENB method"

 

Brightness:67%

Contrast:75%

Gamma: .80

DigitalVib:47%

 

It is my quest to get the most natural lighting. In a real airplane we see a contrast intensive image. At high altitude especially, the dark is dark and the light is light.

Yea i went and tried that beta driver and go 6fps with it. Back to 296.10 with 30fps now. I grant the fact that something may have gone wrong with the install but I think I will wait for the certified version.

 

Interesting. Did you do a clean driver install? Did you delete and re-build your FSX.cfg file? Those results are definitely abnormal, I get fantastic results with them (in fact even faster than the 301.10 WHQL drivers) on my GTX 680.

I am working to figure out what is going wrong here. I think I had a bad driver install from the 250 driver back in October when I built my computer. The errors carried through from driver to driver due to idiosyncrasies in the new way Nvidia does their installations and operator error on my part. I think the error was subtle and only showing during rare events. ENB brought out this problem more and the very confusing nature of the issue took me a while to figure out. I still need to find if the issue persists and the only way to do that is do another flight. Last night I followed that EVGA guide and learned something new. Allot new actually. I encourage everyone to read it as it is a must. I am now running the 296.10 again. If all is well, I will try the beta driver again.

 

In a nutshell, many of the old ways of doing driver upgrades are a big nono now.

To which EVGA guide do you refer?

I recently gave up on ENB. No permanent way for me to get stable FSX when using it. I almost stopped flying FSX for that reason.

 

No bloom effects now, but I have SUPER stable FSX (not a single CTD since) and clearer textures as a bonus.

 

I somewhat compensated for the lost contrast by using Shade and reducing the monitor gamma to 0.90-0.85 from the Nvidia Control Panel.

 

No more disappointment for CTD in the middle of a flight. Happy camper here...

Techguy,

 

http://www.evga.com/forums/tm.aspx?m=1174372&mpage=1

 

Here is the link to the guide.

 

I am now running 301 w/o enb and happy with the vsynch thing it is much smoother. Everything is going good now EXCEPT...

 

I cannot get the AA to work right. I have switched drivers 3 times, reinstalled Nvidia Inspector, pressed apply, tried all sorts of different stuff but the AA is working but not just how it is supposed to. 8xS used to be almost shimmer free but now especially the runway edges and copilots side displays on the NGX have allot of shimmering. When I select progressively higher levels of AA I only notice a very very small difference. 16xS and 8xSGSS should give me a pristine appearance and an attendant performance hit but no, I hardly notice any change but I do notice a performance hit, just not as much as it was. Something is going on with my card and it just will not respond as it should to AA. The shimmering is driving me nuts.