The Gamer's Graphics & Display Settings Guide
[Page 5] Graphics Settings - Frames Per Second
The Graphics Settings
Having seen an overview of how your system processes graphics, this section now examines several common, yet very important, graphics and display-related settings which Windows and your games use. On the following pages we look at Frames Per Second, Resolution, Refresh Rate, Response Time, Vertical Synchronization, Triple Buffering, Antialiasing and Anisotropic Filtering. I thought I understood precisely how these settings worked until I started researching for this guide and found that there were still things I hadn't really understood about them.
This guide is designed to cater to a wide range of people, from beginner to advanced, so please bear in mind that often I may state what you consider to be the bleeding obvious. This is purposely done to make sure absolutely everyone is on the same page when it comes to understanding the fundamentals of each setting. However don't fear, I also include more advanced information including things that you may never have seen explained clearly before.
On that point, I have made a special effort to explain each setting in as simple a language as possible, yet in sufficient detail to be actually useful and not just gloss over each setting. This has been a delicate balancing act and in itself is much more difficult than it sounds. Often the underlying reasons behind certain settings working the way they do can be very complex, and there may be a range of technical considerations involved based on different scenarios. I have avoided getting too sidetracked into these issues. For those who want more technical details, I encourage you to delve further into the links provided throughout, especially those in the Further Reading section at the end of this guide. For most people however the information provided here should be more than enough to tell you what is going on for the purposes of gaming and troubleshooting.
Frames Per Second
Frames Per Second, often called Frame rate, or simply FPS, is the most commonly used term in gaming, and yet one of the more complex and often misunderstood ones. Most people generally know that higher FPS is better, but beyond that there are a lot of misconceptions that need to be clarified. Understanding framerate is the key to understanding the rest of the settings in this section, so do not skip it.
A computer image is made up of lots of small dots called Pixels, the number of which at any time depends on your chosen resolution - for more details see the Resolution section of this guide. When viewed from a reasonable distance, your brain can take all these dots, put them together and perceive them as a single image. This single still image is called a Frame, and as we've seen in the Graphics Process section, a 3D game pretty much turns your entire system into a frame factory, with your graphics card constantly producing new frames every second.
However these frames are only still images, like photographs. For a scene to appear fluid and animated on a computer screen, it has to be made up of lots of different still frames shown rapidly one after the other. This happens to be the same way that movies and TV work: a rapid slideshow of still images, each one slightly different than the last, to achieve the appearance of natural motion. The only reason this method works is that your eyes have a property called Persistence of Vision - they retain an image for a tiny fraction of a second even after it has disappeared. This mechanism is absolutely critical to the way in which TV, movies and computer displays work.
This is where we reach our first misconception: FPS and Refresh Rate are two separate and independent things. It is possible to have 20FPS on a screen with an 85Hz refresh rate, or have 100FPS on a screen with a 60Hz refresh rate. FPS is the rate at which your graphics card is producing new frames; Refresh Rate is the rate at which your monitor is refreshing whatever is displayed on your screen. We discuss this further in the Refresh Rate and Response Time sections of this guide.
FPS is not something which is easy to judge with the naked eye. Fortunately though, it is quite easy to actually measure how many frames per second your game is running at. Some games have a built-in FPS counter which you can activate, but the easiest method of enabling an FPS counter in any game is to use the free FRAPS utility. This utility does not impact on framerate in any significant way, and is accurate in all games. Install it, launch it and then launch a 3D game - a yellow FPS counter will appear in the corner of your screen indicating how many FPS is currently being produced by your graphics card.
Once people become aware of their actual FPS, the most commonly asked question is: "Is my FPS high enough?", to which you may hear such varied replies as: "Any more than 30FPS is a waste because the human eye can't see any more than that", or "You need at least 30FPS for the game to be playable". These sorts of arbitrary comments show the confusion that abounds regarding FPS, and I'll attempt to clarify them below.
There is definitely a 'minimum' FPS - a point at which, if the FPS in a game becomes low enough, your eyes and brain will begin to notice the fact that an animated image on the screen no longer looks smooth; it becomes quite apparent that it is a series of still images being displayed in sequence, like a slideshow. However the exact minimum number of frames required to keep things smooth in a game is not a set scientific value. It will vary from person to person, and importantly it also varies by game type.
In my experience, the baseline for acceptably smooth graphics is around 25 frames per second, if rendered consistently without stuttering or dipping lower. But this is only a subjective starting point, and not a definitive answer. There are several important factors to consider when talking about minimum acceptable framerate:
The key point to take away from this discussion is that there is no set scientific value for minimum FPS. Your eyes and brain don't have a precise trigger point at which, say 23 FPS appears stuttery but 24 FPS is smooth. It's more complex than that and all the factors above need to be considered. If a game looks and feels smooth to you, you are getting 'enough' FPS as a minimum, but don't expect other people to agree with or experience the exact same thing - it is in large part subjective.
The concept that there is a maximum possible FPS beyond which the human eye can't distinguish any real difference is not entirely accurate. For more details, see this article and this article among the many which refute this claim. In particular the common claim that "The human eye can't see more than 24 (or 25 or 30 or 60) FPS" is completely false, and is partly borne of the misconception that TV or movie FPS is the same as PC game FPS, and partly possibly borne out of a need to justify lower framerates.
It's true that movies and TV only use around 24, 25 or 30 FPS, depending on which part of the world you're in. But there are three important differences between Movies, TV and PC games:
1. Movies and TV use Motion Blur, so that if at any time you freeze a movie scene on your DVD player for example, a large part of the scene may consist of blurred objects. Furthermore, the images in a movie or on TV do not have crisp detailed outlines. In a PC game on the other hand, if you take a screenshot or pause the game at any time, you will notice that everything is usually extremely sharp and distinct regardless of how fast it was moving when the shot was taken. Take a look at the screenshot comparison above: on the left is a fast motion shot of an alien from the movie Alien vs. Predator, on the right a fast motion shot of an alien from the old game Alien vs. Predator 2. Thus 24 often-blurred frames from a movie wind up looking much smoother to the human eye than 24 or even 30 distinct frames from a fast-moving PC game. So why can't games use motion blur? Well indeed most recent games have started incorporating blur effects. This can definitely help to reduce the visible impact of lower framerates, but aside from the fact that not all games have motion blur, the next point addresses why this doesn't always work. Even with motion blur, the graphics in PC games may still have very sharp outlines which only settings like Antialiasing can smooth out, but ironically this usually come at the expense of further lowering FPS.
2. Control responsiveness steps in again to further differentiate between a movie and a game. In a movie or TV show, the viewpoint is not under your control; it is typically a static or smoothly panning camera. In a game however, your control over the viewpoint means that in a rapidly moving gaming at 24 or even 30FPS you will notice the general choppiness due to a lack of responsiveness. The variability of control responsiveness based on variable framerate also helps highlight the next point below.
3. PC games do not have a rock-solid unchanging framerate, while TV and movies do. While some games have a framerate cap of 30 or 60 FPS, very few if any PC games can be locked down to consistently show exactly 24 or 30 FPS - their FPS will vary, sometimes significantly. Movies and TV on the other hand always show exactly the same number of frames per second and do not vary one bit. Therefore the variability in framerate in games also works to exaggerate the impact of lower framerates, making them more noticeable. In Crysis for example, if you walk out of an indoor area which has 60 FPS into a outdoor area with 25 FPS, you will notice the difference, partly due to a change in control responsiveness, and partly because your eyes detect the relative change in framerate.
One way to demonstrate that the human eye can actually detect differences above 30FPS is to use a small program called FPS Compare (11KB) by Andreas Gustafsson (used here with his permission). To use it, simply extract and launch the FPSCompare.exe file. Make sure to read the instructions in the Readme.txt file, and note that this utility is still in beta form. You may need to force VSync to Off in your graphics card's control panel for it to work properly, but if it doesn't work properly for you, you can try the more basic version of it from here: FPS Compare (old) (106KB).
FPS Compare shows the same scene rendered side by side in a split-screen arrangement, but each side is running at a different frame rate. When launching the new FPS Compare program, I recommend pressing F2 to change the scene to one more familiar to gaming. Now by staring at the middle of your screen, you should be able to detect that the portion on the left (at ~60FPS) appears smoother than the portion on the right (at ~30FPS). Even if the difference is not major to your eyes, many people do notice that there is at least some difference - something which refutes the fact that human eyes cannot notice differences in smoothness at an FPS over 30.
As the articles I link to further above discuss, testing has shown that human beings can regularly distinguish differences of one frame in 200 every second. There is no actual theoretical limit on how many frames the eye can distinguish. In the natural world, human eyes don't digest motion in terms of a series of still frames, they take in a constant stream of analog movement data. In particular, we are quick to notice dramatic contrasts, no matter how brief. If there is a gap or brief fluctuation in the flow of visual data, then our eyes and consequently our brain can actually pick this up if it's relevant, even if it's subconscious - it all depends on the context of the data streaming in.
So to come back to the question of how many FPS is enough, in my experience, and for most practical purposes, a framerate of around 60 FPS is completely sufficient as a maximum FPS. Even 25 or 30FPS can be totally sufficient in slow or medium-paced games - particularly if the game has motion blur, softer edges, and does not display significant variability or stuttering. If there's one thing that would be perfect to have in any game, it would be a method of maintaining a fixed framerate. Unfortunately this is not practically possible on many systems because of the different types of hardware used. You can enable VSync to cap the maximum framerate and hence reduce FPS variability, but this may also reduce performance - see the Vertical Synchronization section of this guide.