PDA

View Full Version : Temporal AA in ATI cards issue


ahmad
03-11-2006, 12:42 AM
I noticed something was weird, but I wasn't sure. Then I did further testing and now I think I sort of understand whats happening here with this feature.

My setup:

Sapphire x1900XTX
Opteron 170
OCZ 2x1GB

Using the same clocks, I used these driver settings:

2x Anti-Aliasing
16x Ansiotropic Filtering + HQ
Full Adaptive Anti-Aliasing enabled
Midmap detail: High Quality
Vertical Sync: Off
AI Catalyst: Standard

Now, I tested this in a few games, but I only did benchies with FRAPS and NFSMW:

http://www.ahmadh.net/images/test2.JPG

Maximum quality settings in game and 1280x1024 resolution. I only tested the take off part of a challange. Notice the framerate is quite high:

Min: 52FPS
Max: 73FPS
Average: 62.132FPS

This is quite awesome considering the settings used as well as the fact that this is during take off.

Now keep the same settings, I turn on Temporal AA:

http://www.ahmadh.net/images/test1.JPG

Min: 29FPS
Max: 63FPS
Avg: 49.833FPS

Wow look at that graph. Very choppy (even though its a very short time frame, both tests were pretty much the same path on the same track during the start). And it seems like if it hits below 60FPS, it drops quickly to 30FPS, then stays there for no reason, then jumps back up to 60FPS.

Is temporal AA really that aggressive? Or what is this exactly?

I noticed this "capped" framerate in other games too, even when Vsync was disabled once Temporal AA was enabled, it would stay at 60 or 75 (depending on resolution used) as well as these sudden drops.

Obviously nothing serious because most people don't use this feature, but it would be nice if we know if this is a game or a driver issue. And if it is a driver issue, please fix it ati :)

IvanAndreevich
03-11-2006, 08:59 AM
I think temporal AA requires VSYNC (even if you turn it off), but I may be wrong.

ahmad
03-11-2006, 10:08 AM
I think temporal AA requires VSYNC (even if you turn it off), but I may be wrong.

Yeah thats what I am thinking too. But that still doesn't explain how it manages to drag performance down to 30FPS, when I never even see these numbers without it.