...I had been using Nick's nHancer settings of Trilinear and no A.A. within FSX but with the 197.45 drivers, I tried using nHancer AND setting Anisotropic with A.A. within FSX.This setting hand's down gives the most incredible and clear image quality that I have ever seen FSX to date!Use Nick's standard settings within nHancer...BUT... use Anisotropic and A.A. within FSX. You will love what happens, oh yeah!It seems that nHancer and the in-game Aniso and A.A. compliment each other for an enhanced output. You can clearly see an added umbrella visual quality over in-game settings of: Tri and no A.A. as per Nick's standard setting suggestions.This will be the keeper on my FSX setup....

Did you use the recommended setup on the previous drivers?

I personally think it is the new driver. My jaw hit the floor when I loaded FSX and could not get over how great the colors are and the detail. Smoother FPS also(I'm locked to 45). Best Driver to date for my GTX285 Classified. http://www.nvidia.com/object/win7_winvista...97.45_whql.html

I personally think it is the new driver. My jaw hit the floor when I loaded FSX and could not get over how great the colors are and the detail. Smoother FPS also(I'm locked to 45). Best Driver to date for my GTX285 Classified. http://www.nvidia.com/object/win7_winvista...97.45_whql.html

Yes, I posted in another thread about these new drivers (your results may vary (disclaimer)), and I have noticed a huge difference in IQ and my ability to up the AG and still remail fluid.I had always dropped back and used the 182.50's, as the previous 197's were terrible. Not sure what nvidia did, but the improvement is very noticeable.I too am using the GTX285 oc'd 1GB.Bob G

Yes, I posted in another thread about these new drivers (your results may vary (disclaimer)), and I have noticed a huge difference in IQ and my ability to up the AG and still remail fluid.I had always dropped back and used the 182.50's, as the previous 197's were terrible. Not sure what nvidia did, but the improvement is very noticeable.I too am using the GTX285 oc'd 1GB.Bob G

I never follow the driver hype but I must agree the 197.45 driver is working great for me aswell, infact this is the first time I have not immediately gone back to my trusty old 182.50. :(

I must co-sign and say that these new drivers are great so far! IQ looks a bit better and its a bit more fluid. Nice job NVIDIA.

...I had been using Nick's nHancer settings of Trilinear and no A.A. within FSX but with the 197.45 drivers, I tried using nHancer AND setting Anisotropic with A.A. within FSX.This setting hand's down gives the most incredible and clear image quality that I have ever seen FSX to date!Use Nick's standard settings within nHancer...BUT... use Anisotropic and A.A. within FSX. You will love what happens, oh yeah!It seems that nHancer and the in-game Aniso and A.A. compliment each other for an enhanced output. You can clearly see an added umbrella visual quality over in-game settings of: Tri and no A.A. as per Nick's standard setting suggestions.This will be the keeper on my FSX setup....

I am just wondering about those settings. If you set aa and anisio in game, but you use Nicks settings, it would seem that the nHancer settings would override at least the AA. There is an option for AA to enhance application settings, so not sure what actually is happening overall. I am not arguing that you see a difference, only that it seems the settings would conflict, and I dont have the knowledge to understand what is actually happening at the driver level.Bob

I am just wondering about those settings. If you set aa and anisio in game, but you use Nicks settings, it would seem that the nHancer settings would override at least the AA. There is an option for AA to enhance application settings, so not sure what actually is happening overall. I am not arguing that you see a difference, only that it seems the settings would conflict, and I dont have the knowledge to understand what is actually happening at the driver level.Bob

I agree on that. No need to use nHancer if you don't force a higher AA setting onto FSX. I stopped using nHancer after installing the 197.13 drivers. I'm now on 197.45 and the IQ is good in FSX.

...I had been using Nick's nHancer settings of Trilinear and no A.A. within FSX but with the 197.45 drivers, I tried using nHancer AND setting Anisotropic with A.A. within FSX.This setting hand's down gives the most incredible and clear image quality that I have ever seen FSX to date!

Sorry to disagree... the new drivers and in-game AA makes the little placard under the compass in my Scout swim uncontrollably... :( Maybe there is a setting I have missed, but back to the 182.50s and 8XS AA, using nHancer gives me a rock solid picture.

If you don't use Nhancer, do you just leave the settings in the Nvidia control panel as application controlled?

Did you use the recommended setup on the previous drivers?

You bet! The only thing that I had never done to date, was to use the different settings directly in FSX in conjunction with nHancer. nHancer with what was stated in the O.P. clearly gives ultimate I.Q. I'm kicking myself that I didn't try that earlier on....

Sorry to disagree... the new drivers and in-game AA makes the little placard under the compass in my Scout swim uncontrollably... :( Maybe there is a setting I have missed, but back to the 182.50s and 8XS AA, using nHancer gives me a rock solid picture.

------------------------------------------------Bert, you misunderstand. I meant for the reader to USE nHancer WITH Anisotropic and A.A. also set within FSX. Use the same 'Nick' settings in nHancer, but swap out the Trilinear and no A.A. inside FSX for what I posted. It clearly gives superior output...that is amazing in its visual quality.

I am just wondering about those settings. If you set aa and anisio in game, but you use Nicks settings, it would seem that the nHancer settings would override at least the AA. There is an option for AA to enhance application settings, so not sure what actually is happening overall. I am not arguing that you see a difference, only that it seems the settings would conflict, and I dont have the knowledge to understand what is actually happening at the driver level.Bob

Hi Bob, Actually Bob, do the A/B test for yourself. Run the new driver, but keep everything as it was...you know, Trilinear and no A.A. as per Nick's nHancer setup post. Take a flight with your favorite start-up. Then just before you shut down, switch out Tri for Aniso and click on the in-game A.A. Shut down, wait a few seconds and then fire back up FSX. Take that same flight and just check out the superior quality...over your previous just flown view. It's like you just applied polish to that wash job.....What I am saying that even with running the 197.45's, you get a BETTER I.Q. with them, when the Trilinear and no A.A. in game is swapped out. Certainly a keeper for myself.Mitch

I agree on that. No need to use nHancer if you don't force a higher AA setting onto FSX. I stopped using nHancer after installing the 197.13 drivers. I'm now on 197.45 and the IQ is good in FSX.

I was wondering this morning if perhaps you don't need to run the nHancer hack anymore with this new driver set, but in viewing the actual nVidia driver control, and then nHancers vast number of specific tweaks, you have less control to fine tune the driver if you do NOT use nHancer. I think that by using BOTH nHancer and setting the in-game filter to Anisotropic and A.A., you get the best usage of driver output. It doesn't hurt the slightest in FPS output to still have nHancer tweaked in the background. Like I said, you should reuse nHancer and give the swap out in FSX a try. See what you think. If I.Q. is better than even what you have with NO involvement of nHancer, then you gain. Now, I must say for the record, that I haven't REMOVED nHancer and then just have run with the 197.45's and with ANISO and A.A. checked off in FSX, so I can't say that there is an absolute A/B difference with, or without. My O.P. was to truly state that with having changed the FSX setting, was there a marked I.Q. improvement over my 'having not changed a thing' setting. My nHancer settings and usage were/was always in play.

I was wondering this morning if perhaps you don't need to run the nHancer hack anymore with this new driver set, but in viewing the actual nVidia driver control, and then nHancers vast number of specific tweaks, you have less control to fine tune the driver if you do NOT use nHancer. I think that by using BOTH nHancer and setting the in-game filter to Anisotropic and A.A., you get the best usage of driver output. It doesn't hurt the slightest in FPS output to still have nHancer tweaked in the background. Like I said, you should reuse nHancer and give the swap out in FSX a try. See what you think. If I.Q. is better than even what you have with NO involvement of nHancer, then you gain. Now, I must say for the recored, that I haven't REMOVED nHancer and then just have run with the 197.45's and with ANISO and A.A. checked off in FSX, so I can't say that there is an absolute A/B difference with, or without. My O.P. was to truly state that with having changed the FSX setting, was there a marked I.Q. improvement over my 'having not changed a thing' setting. My nHancer settings and usage were/was always in play.

Again, I think this will fall into (your experience may vary), but I will give it a try. There is a noticeable difference when using Hhancer with the combined=4s checked. This is something that I found to be very helpful. With the nvidia driver, the combined option is not available, forcing you to use the standard 2x,4x etc. When I bypass Nhnacer and used the standard AA options, it seems to put more of a load on the throughput in order to attain the same AA effect. So for me, Hhancer has been a blessing, but I have not yet tried using this driver without NHancer, but I will give it a shot and see what happens. On a side note here, I am finding that the external frame lock utility that I run does not appear to be working or not as effeciently as it was before I installed these new drivers. I have it locked at 26 and at times I am running between 31-35 now. With other drivers, I never went over 28. I need to check into this a little more. Hmmm maybe I can increase my lock :( Bob G

Again, I think this will fall into (your experience may vary), but I will give it a try. There is a noticeable difference when using Hhancer with the combined=4s checked. This is something that I found to be very helpful. With the nvidia driver, the combined option is not available, forcing you to use the standard 2x,4x etc. When I bypass Nhnacer and used the standard AA options, it seems to put more of a load on the throughput in order to attain the same AA effect. So for me, Hhancer has been a blessing, but I have not yet tried using this driver without NHancer, but I will give it a shot and see what happens. On a side note here, I am finding that the external frame lock utility that I run does not appear to be working or not as effeciently as it was before I installed these new drivers. I have it locked at 26 and at times I am running between 31-35 now. With other drivers, I never went over 28. I need to check into this a little more. Hmmm maybe I can increase my lock :( Bob G

Bob, I get the FPS limiter 'setting overrun' as well. Perhaps it is explained that our systems are running at prime...and our systems want to 'bust out' of the software restriction? Who knows? It hasn't affected anything though as per FPS and smooth delivery performance. I run it, all Bojote tweaks, and BP=500000/1000000. I'm still honing in on what I will stay with of those two BP settings. I am leaning though towards keeping it at BP-500000 (five zeroes). To gauge both 5 and 10 (add zeroes, lol), I am running over different topography, and check for micro-stutter, if any, and over what did it generate. BP=500000 is looking really good though for the final 'glue it into place and forget'.