Another New Anti-Aliasing Mode: Enhanced Quality AA

With the 6800 series AMD introduced Morphological Anti-Aliasing (MLAA), a low-complexity post-processing anti-aliasing filter. As a post-processing filter it worked with a wide variety of games and APIs, and in most cases the performance overhead was not very severe. However it’s not the only new anti-aliasing mode that AMD has been working on.

New with the 6900 series is a mode AMD is calling Enhanced Quality Anti-Aliasing. If you recall NVIDIA’s Coverage Sample Anti-Aliasing (CSAA) introduced with the GeForce 8800GTX, then all of this should sound quite familiar – in fact it’s basically the same thing.

Under traditional MSAA, for a pixel covered by 2 or more triangles/fragments, 2, 4, or 8 subpixel samples are taken to determine what the final pixel should be. In the process the color of the triangle and the Z/depth of the triangle are both sampled and stored, and at the end of the process the results are blended together to determine the final pixel value. This process works well for resolving aliasing along polygon edges at a fraction of the cost of true super sampling, but it’s still expensive. Collecting and storing the Z and color values requires extra memory to store the values and extra memory bandwidth to work with the values. Ultimately while we need enough samples to determine colors of the involved triangles, we do not always need a great deal of them. With a few color/Z samples we have all of the color data we need in most cases, however the “hard” part of anti-aliasing becomes what the proper blending of color values should be.


1 Pixel Covred by 2 Triangles/Fragments

Thus we have EQAA, a compromise on the idea. Color/Z samples are expensive, but just checking if a triangle covers part of a subpixel is very cheap. If we have enough color/Z samples to get the necessary color information, then just doing additional simple subpixel coverage checks would allow us better determine what percentage of a pixel is covered by a given polygon, which we can then use to blend colors in a more accurate fashion. For example with 4x MSAA we can only determine if a pixel is 0/25/50/75/100 percent covered by a triangle, but with 4x EQAA where we take 4 color samples and then 4 additional coverage-only samples, we can determine blending values down to 0/12/25/37/50/62/75/87/100 percent coverage, the same amount of accuracy as using 8x MSAA. Thus in the right situation we can have quality similar to 8x MSAA for only a little over 4x MSAA’s cost.


MSAA & EQAA Sample Patterns

In reality of course this doesn’t always work out as well. The best case scenario is that the additional coverage samples are almost as good as having additional color/Z samples, while the worst case scenario is that additional coverage samples are practically worthless. This depends on a game-by-game, if not pixel-by-pixel basis. In practice additional coverage samples are a way to slightly improve MSAA quality for a very, very low cost.

While NVIDIA has had the ability to take separate coverage samples since G80, AMD has not had this ability until now. With the 6900 hardware their ROPs finally gain this ability.

Beyond that, AMD and NVIDIA’s implementations are nearly identical except for the naming convention. Both can take a number of coverage samples independent of the color/Z samples based on the setting used; the only notable difference we’re aware of is that like AMD’s other AA modes, their EQAA mode can be programmed to use a custom sample pattern.

As is the case with NVIDIA’s CSAA, AMD’s EQAA mode is available to DirectX applications or can be forced through the drivers. DirectX applications can set it through the Multisample Quality attribute, which is usually abstracted to list the vendor’s name for the mode in a game’s UI. Otherwise it can be forced via the Catalyst Control Center, either by forcing an AA mode, or as is the case with NVIDIA, enhancing the AA mode by letting the game set the AA mode while the driver overrides the game and specifies different Multisample Quality attribute. Thus the “enhance application settings” AA mode is new to AMD with the 6900 series.

To be honest we’re a bit ruffled by the naming choice. True, NVIDIA did go and have to pick daft names for their CSAA modes (when is 8x not 8 sample MSAA?), but ultimately CSAA and EQAA are virtually identical. NVIDIA has a 4 year lead on AMD here, and we’d just as well use NVIDIA’s naming conventions for consistency. Instead we have the following.

Coverage Sampling Modes: CSAA vs EQAA
NVIDIA Mode
(Color + Coverage)
AMD
2x 2+0 2x
N/A 2+2 2xEQ
4x 4+0 4x
8x 4+4 4xEQ
16x 4+12 N/A
8xQ 8+0 8x
16xQ 8+8 8xEQ
32x 8+24 N/A

AMD ends up having 1 mode NVIDIA doesn’t, 2xEQ, which is 2x MSAA + 2x cover samples; meanwhile NVIDIA has 16x (4x MSAA + 12 cover samples) and 32x (8x MSAA + 24 cover samples). Finally, as we’ll see, just as is the case for NVIDIA additional coverage samples are equally cheap for AMD.

Tweaking PowerTune Meet the 6970 & 6950
Comments Locked

168 Comments

View All Comments

  • Ryan Smith - Wednesday, December 15, 2010 - link

    AMD rarely has Linux drivers ready for the press ahead of a launch. This is one such occasion.
  • MeanBruce - Wednesday, December 15, 2010 - link

    Great job on the review Ryan, hope you will cover the upcoming Nvidia 560 and 550 when they arrive. Peace Brother!
  • gescom - Wednesday, December 15, 2010 - link

    Please Anand make an update with a new 10.12 driver. Great review btw.
  • knowom - Wednesday, December 15, 2010 - link

    Until you keep into consideration

    1) Driver support
    2) Cuda
    3) PhysX

    I also prefer the lower idle noise, but higher load noise than the reverse for Ati because when your gaming usually you have your sound turned up a lot it's when you aren't gaming is when noise is more of the issue for seeking a quieter system.

    It's a better trade off in my view, but they are both pretty even in terms of noise for idle and load regardless and a far cry from quite compared to other solutions from both vendors if that's what your worried about not to mention non reference cooler designs effect that situation by leaps and bounds..
  • Acanthus - Wednesday, December 15, 2010 - link

    AMD has been updating drivers more aggressively than Nvidia lately. (the last year)
    Anecdotally, my GTX285 has had a lot more game issues than my 4890. Specifically in NWN2 and Civ5.

    Cuda is irrelevant unless you are doing heavy 1. photoshop, 2. video encoding.

    PhysX is still a crappy gimmick at this point and needs to offer real visual improvements without a 40%+ performance hit.
  • smookyolo - Wednesday, December 15, 2010 - link

    PhysX may be a gimmick in games, but it's one of the better ones.

    Also, guess what... it's being used all over the 3D animation industry.

    And guess where the real money comes from? The industry.
  • fausto412 - Wednesday, December 15, 2010 - link

    physx is a gimmick that has been around for some time and will never take hold. when physx came around it set a new standard but since then developers have adopted havok more commonly since it doesn't require extra hardware.

    it's all marketing and not a worthy decision point when buying a new card
  • jackstar7 - Wednesday, December 15, 2010 - link

    Alternately, my triple-monitor setup makes AMD the obvious choice.
  • beepboy - Wednesday, December 15, 2010 - link

    Agreed on triple-monitor setup. You can make the argument that 2x 460s are cheaper and nets better performance but at the end of the day 2x 460s will be louder, use more power, more heat, etc over a single 69xx. I just want my triple monitor setup, damn it.
  • codedivine - Wednesday, December 15, 2010 - link

    Any info on cache sizes and register files?

Log in

Don't have an account? Sign up now