Stephen, Where do you set "Application controlled" vs none? Using the Inspector or the nVidia control panel? aren;t we supposed to do all the settings via the Inspector?

 

Manny

 

Sorry Manny,

 

I was thinking of something else. When I put in the new driver, my AA was gone too. After opening NI I saw that the only change was Behaviour flags needed to be reset to "None" but everything else was still set right. Upon correction all is well. I did restart after installing the new driver, and retarted FSX a number of times to have it take properly. Good luck!

 

Kind regards,

Sorry Manny,

 

I was thinking of something else. When I put in the new driver, my AA was gone too. After opening NI I saw that the only change was Behaviour flags needed to be reset to "None" but everything else was still set right. Upon correction all is well. I did restart after installing the new driver, and retarted FSX a number of times to have it take properly. Good luck!

 

Kind regards,

 

Yeah..within NI, after I imported my profile.. I made one change. AntiAliasing mode to override any application settings in NI. and it now looks good.

 

Manny

Thats right, when installing a new driver, i ALWAYS have one or two changes in my FSX NvidiaInspector settings.

 

So i ALWAYS compare the settings to the exact settings Word Not Allowed recommands, they are perfect.

 

And those here are essential for Antialiasing :

 

Antialiasing - Mode : Override any application Setting (NOT Application controlled ! )

Antialiasing - Setting : 8 x S

Antialiasing - Transparancy Supersampling : 2x Sparse Grid Supersampling

anyone notice a difference in their colors with this driver? They appear to be much softer and closer to gray than black than my old driver set. Wondering if that is just me...

Thats right, when installing a new driver, i ALWAYS have one or two changes in my FSX NvidiaInspector settings.

 

So i ALWAYS compare the settings to the exact settings Word Not Allowed recommands, they are perfect.

 

And those here are essential for Antialiasing :

 

Antialiasing - Mode : Override any application Setting (NOT Application controlled ! )

Antialiasing - Setting : 8 x S

Antialiasing - Transparancy Supersampling : 2x Sparse Grid Supersampling

 

I am not sure if this necessary

 

Antialiasing - Transparancy Supersampling : 2x Sparse Grid Supersampling

 

 

 

Manny

I am running these drivers without any issues so far. Mainly I got them because Assassin's Creed 3 performance is supposed to be better, but FSX runs just fine with them as well. Personally I use 16xS AA and no SGSS.

Tried a few different combos and I like 16xs and SuperSamling enabled... No SGSS.

Tried a few different combos and I like 16xs and SuperSamling enabled... No SGSS.

 

For my GTX580 I use 8xS (don't see much improvement for the fps cost at 8xSQ), 2xSGSS, 16x AF.

 

If I don't use at least 2xSGSS AA Transparency Supersampling with the NGX I get:

 

* wavies on the lines separating various wing components

* wavies on the right-seat panel viewed from the left-seat, and visa-versa (when your head is in motion)

* wavies on the OH panel, especially during pushback, and sometimes in-flight if passing beneath clouds

 

2xSGSS pretty much eliminates these. 4x is better, but I don't want to sacrifice frames.

For my GTX580 I use 8xS (don't see much improvement for the fps cost at 8xSQ), 2xSGSS, 16x AF.

 

If I don't use at least 2xSGSS AA Transparency Supersampling with the NGX I get:

 

* wavies on the lines separating various wing components

* wavies on the right-seat panel viewed from the left-seat, and visa-versa (when your head is in motion)

* wavies on the OH panel, especially during pushback, and sometimes in-flight if passing beneath clouds

 

2xSGSS pretty much eliminates these. 4x is better, but I don't want to sacrifice frames.

But wouldn't using SS be a higher level of AA than SGSS? Also, if you use 2xSGSS aren't you supposed to set MS to Match? so 2xSGSS should also have 2xMS set and 4xSGSS should have 4xMS set etc...

I always run a sweeper. To much crap is left behind by old drivers.

 

I think--just an opinion--this is a legacy concern from many years ago, maybe even a decade or more ago. Do you imagine nVidia programmers haven't figured out and eliminated components installed that somehow confuse the operating system into accessing lines of code that interfere w/ the newly installed driver components' ability to handle the tasks involved? I would think the absolute worst case scenario in this regard is in leaving some registry entries that no longer apply, and yet the registry and OS are laden w/ entries that no longer apply, or are waiting to apply when a new device is installed that can access them. So taking the time/cost/effort to run cleaners arguably is a step that is unnecessary from a practical point of view.

i use application managed settings for fsx nvidia dispaly, all AA etc set in FSX

 

Got better frames with the current official release 206, so reverted back from beta 210

I think--just an opinion--this is a legacy concern from many years ago, maybe even a decade or more ago. Do you imagine nVidia programmers haven't figured out and eliminated components installed that somehow confuse the operating system into accessing lines of code that interfere w/ the newly installed driver components' ability to handle the tasks involved? I would think the absolute worst case scenario in this regard is in leaving some registry entries that no longer apply, and yet the registry and OS are laden w/ entries that no longer apply, or are waiting to apply when a new device is installed that can access them. So taking the time/cost/effort to run cleaners arguably is a step that is unnecessary from a practical point of view.

 

You are absolutly right, there is no need to use CC cleaner or program like that anymore (with Nvidia), Nvidia figured it out already, they update the old components.