Well, after an evening on ATAG I quite like it. Edges are nice and the terrain is much more like it should be. It definitely gives a smoother finish overall although the info windows lettering is a bit blurred. The instruments letterings are hardly affected.

The distant terrain is filled in instead of looking like a slice through puff pastry and it also seems to have improved the appearance of distant water. I don't seem to have lost distant dots although of course they are now slightly blurred.

Regarding NVCP settings, when FXAA is enabled it disabled the normal AA selection although that can be selected before FXAA is selected. Does FXAA ignore any normal AA settings or does it operate on the selected AA output?

Acorrding to driver information, FXAA works on the overall rendered frame, so it does not override the other AA setings, it is applied on top of them.

Same here with a 460 GTX with no significant loss of Framerate. Really an improvement.. Horrido, Allons!

Thanks :)

I just set AA to 16xCSAA. Looks nice.

Mine is set to 32xCSAA and still no impact on FPS for me.
580GPU.

I thought that AA, even when forced on NVCP, didn't work. Maybe you are looking only at the FXAA effect. :confused:

I'm using the settings recommended by kendo...these drivers are beautiful in game, but the screenshots don't capture that beauty

kendo settings


http://i51.photobucket.com/albums/f3...all/kendo1.jpg


http://i51.photobucket.com/albums/f3...all/kendo2.jpg

http://i51.photobucket.com/albums/f3...416_095524.jpg

Ive just checked and i think your right. Its the FXAA and not the CSAA.

Could be, it is hard to tell with the FXAA overlaid. It was nice anyway with just FXAA on. Maybe CSAAx16 was just a placebo effect :)

Actually, displaying my ignorance, I had always thought the card AA settings did the job independently of the game but we all know they don't in CoD, we can't even set AAx4. I guess its something to do with the way the graphics are/aren't coded.

I can only change my Screen Resolution using windows control panel with this beta driver, I can normally do it in the Nvidea CP.

Is this a bug in the beta driver?