If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

Shame on nvidia for fixing an application bug in their drivers. Shame on them. Troll fail = Qaridarium.

Hi Everybody,
What is being experienced is not an “Antialiasing cheat” but rather a HawX bug that is fixed by our driver using an application specific profile.
In a nutshell, the HawX application requests the highest possible AA “sample quality” at a particular AA level from our driver. Without our driver fix, the game would be running 16xCSAA instead of standard 4xAA when you select 4xAA in-game. It runs the proper 4xAA with the driver fix. You defeat the fix by changing the .exe name, causing it to run at 16xCSAA.
You may remember that Geforce 8800 introduced Coverage Sampling AA (CSAA) technology, which added higher quality AA using little extra storage. Prior to 8800 GTX and CSAA, there was only one “sample quality level” for each AA level, so if an application requested four AA samples, the hardware performed standard 4xAA. However, with 8800 GTX GPUs onwards, our drivers expose additional sample quality levels for various standard AA levels which correspond to our CSAA modes at a given standard AA level.
The “sample quality level” feature was the outcome of discussions with Microsoft and game developers. It allowed CSAA to be exposed in the current DirectX framework without major changes. Game developers would be able to take advantage of CSAA with minor tweaks in their code.
Unfortunately, HawX requests the highest quality level for 4xAA, but does not give the user the explicit ability to set CSAA levels in their control panel. Without the driver profile fix, 16xCSAA is applied instead of standard 4xAA. Recall that 16xCSAA uses 4 color/Z samples like 4xAA, but also adds 12 coverage samples. (You can read more about CSAA in our GeForce 8800 Tech Briefs on our Website).
When you rename the HawX.exe to something else, the driver profile bits are ignored, and 16xCSAA is used. Thus the modest performance slowdown and higher quality AA as shown in the images.
To use “standard” 4xAA in a renamed HawX executable, you should select any level of anti-aliasing in the game, then go into the NVIDIA Control Panel and set 4xAA for “Antialiasing Setting” and turn on “Enhance the application setting” for the “Antialiasing mode”.
Nick Stam, NVIDIA

"16xCSAA" if an app wana have 16xCSAA then the only true solution is give them the 16xCSAA !

and this is a "nvidia it means to played" game means nvidia payes for that bug !

they only wana be sure amd cards run on "16xCSAA" and nvidia cards run on 4xaa

its just not an bugfix force 4X by driver!

its a cheat nothing more.

LMFAO, you really have no clue. The apps 4x setting requests the highest available instead of the true 4x AA mode. That's not a cheat. It would be the same if the the app says 1920x1200 but instead of requesting 1920x1200 it requests the highest resolution of the monitor which could be 2560x1600. The driver bug fix is there to just give what the app is requesting. That's not cheating, that's proper development.

LMFAO, you really have no clue. The apps 4x setting requests the highest available instead of the true 4x AA mode. That's not a cheat. It would be the same if the the app says 1920x1200 but instead of requesting 1920x1200 it requests the highest resolution of the monitor which could be 2560x1600. The driver bug fix is there to just give what the app is requesting. That's not cheating, that's proper development.

LMFAO, the menu setting says 4x AA, not the highest, the drivers are simply giving what the menu says. In other words, they are giving EXACTLY what is requested by the user instead of going off and doing it's own thing. Again that isn't cheating at all.

LMFAO, the menu setting says 4x AA, not the highest, the drivers are simply giving what the menu says. In other words, they are giving EXACTLY what is requested by the user instead of going off and doing it's own thing. Again that isn't cheating at all.

the dev of the app define what kind of aa they wana have and not the 'menu'

means if the dev write 4xaa in the menu and write force highest AA in the sourcecode then the highest AA count and not the writing in the menu.

nvidia just cheat thats because the dev wana have highest AA and not 4X