Showing posts with label vertical sync. Show all posts
Showing posts with label vertical sync. Show all posts

Saturday, October 15, 2011

Anti Aliasing, GPU Murder, Justified, or No?

Anti-Aliasing, multi-sampling, 8x, 16x? Analytical? FSAA? What the hell is this shit, why can't I max it, and what am I looking for that makes it worth turning my GPU into an EZ-Bake oven? It can be kind of annoying when you're beating your framerate into the floor for something that's pretty hard to spot specifically unless you know what to look for.

Lucky for you, you don't need to look any further to find at least some of the answers. Simply put, AA is designed to make angled line on square pixels not look like a staircase. Since each pixel can only have one RGB value at any given time, you can't just have it be half and half with two different colors. The way Anti-aliasing fixes this, roughly, is to take raw texture data for some or all of the pixels involved, and kind of blend the colors in a way that lends itself to both sides of the line, making the transition appear smooth.

One of the reasons this is difficult to spot for a lot of people is pixel density. Most displays have fairly high density, which basically just refers to how much area the pixels are packed into. 22" 1920x1080 has the same number of pixels to play with as 30" 1920x1080. That means that the bigger your display, the larger the pixel, which can exaggerate the staircase shape on angled lines.

The fun thing here, is that the better your pixel density, the less you need AA. You might need 4x or so at 22" 1080p, but at 32", you should be trying to max it for lines that look similarly smooth. The different varieties and multiples involved, like 8xMSAA, or 4xSSAA are just different methods that can be used to determine what the resulting pixel data will be.

0xAA
4xaa
8xAA 




















These three images were originally taken in 1080p from Dragon Age 2, DX11, Highest quality everything, with the only thing changing in each shot being the level of Anti-Aliasing, as seen in the captions.

Now that I've explained anti-aliasing, spotting it should be easy, right?

 I'm guessing a lot of you out there actually have to work really hard to spot it, right? Like I said, the smaller the pixel, the smaller the square shape, the smoother the line, even without anti-aliasing.

On my 32" TV, I can barely see the difference between 4x and 8x at desk viewing distance.


 So, now that we've gone over exactly how big of a difference it makes, you can see that trying to max this may not really matter for your overall gaming experience. Given the massive GPU horsepower needed for high AA with decent quality textures, it can be an expensive prospect to truly max every game that comes out.

But, if you can live without something you can't see or can barely see, you can generally get by with a lot less power. The exact difference will vary a good bit from game to game, but frequently, if you're getting slightly jerky FPS at 8xAA, dropping to 4xAA will get you fairly smooth, in my experience. That's a big performance difference for a barely visible change.

Now obviously, this is one of those things where everyone needs to draw their own conclusions. I'll keep using insane PCs, because getting performance out of them is half the fun. But for people wanting performance on a budget, check the AA used in benchmarks, and you might just find that you'll be ok with a card that doesn't look quite as pretty if all you see is how long the bars are.

Thursday, September 15, 2011

Max FPS Makes My Head Hertz

We've all seen the argument, "How many Frames per second can the human eye see?". The trouble is, while everybody seems to have a theory, nobody seems to be able to show concrete evidence to back it up. Instead of trying to convince you to agree with me based on no information, instead I'm going to discuss hardware limitations, and why they render the argument moot for most people.

If you know much about displays, you know they have a refresh rate, listed in Hertz(Hz). Hertz means cycles per second, so a 60Hz refresh rate means your display refreshes 60 times per second. In other words, no matter how many frames per second your GPU draws, only 60 can be shown on your screen. 60Hz is by far the most common refresh rate currently, although 3d capable displays and some others are capable of a 120Hz refresh rate.

Current video card drivers let you set video output rate, usually limiting you to a maximum of your display's refresh rate, but you can also lower it, which has some advantages for certain video enthusiasts. This is kind of outside the point, however. What's much more important is this: Your refresh rate is a hardware limitation on frame rate. There is no physical way to properly display a larger number of FPS. You can, however improperly display them.

Improper display will show itself in screen tearing. Essentially, your display is trying to show parts of two different frames at the same time, because it's receiving too many frames per second. This is where Vertical Sync comes into play. Vertical sync (also known as Vsync) lets you limit your rendered FPS to a fraction of your displays refresh rate. In other words, the most FPS you can get with Vsync enabled on a 60Hz display is 60 FPS.

You may be wondering, perhaps, exactly why I'm blathering on about vertical sync and refresh rates. Well, it becomes much more useful when you consider that no matter what actual frame rates the human eye is capable of differentiating, the human eye absolutely does notice sudden change. The human eye detects movement, and it is quite capable of noticing if the displayed frame rate suddenly drops from 60 to 45, which can happen quite easily with Vsync, if your rendered FPS drops below 60.

Since we don't want rendered FPS to drop below 60, some overhead in average frame rate is needed, to keep 60 as the minimum, if we're going to use Vsync. This is where excessive graphics power comes in on a display capped at 60Hz. In other words, while being able to get 90 FPS average may not make the game look any better than when it runs at 60 FPS, it does make the game look better by virtue of keeping it from making a sudden sharp dip. This is a hardware limitation. That means that any added perceived smoothness is purely a placebo effect. Your mind is playing tricks on you, plain and simple.

Oh, and if you want to know my thoughts on perceived framerate? It depends on the game, your PC, and you. If your PC has low input lag, and doesn't stutter, a fairly low framerate can look good in most cases. However, depending on the perception of speed being rendered, a higher framerate may be needed to make fast "motion" appear smooth, unless motion blur is rendered by the game.