User blog:Master1337cheeZ/Framerate

So, I recently saw a blog post (http://callofduty.wikia.com/wiki/User_blog:N7/60FPS_gives_Modern_Warfare_3_a_%22Competitive_edge%22) on here regarding the advantage of running a game engine at 60 fps (that's frames per second, frame being a single photo you could take). For whatever reason, I was unable to comment on that specific post, so I decided this would be good. Many people were commenting, saying that the difference between 60 fps and 30 fps is non-existent. The difference is most certainly there, and while arguing something different, this website (http://www.boallen.com/fps-compare.html) will show the difference.

Slowly move your focus from the 15 fps to the 30, and 60. Everything looks fine as you move up, getting better even.

Now stay on the 60 for a while without looking at the 30 or 15. Now move to the others.

They look choppy, like something isn't loading properly (if it doesn't, you didn't watch long enough).

This is what happens when a game can't run consistently at a higher framerate. Sounds aren't synced up with what you see on screen, and things run (even in a single-player game) like you're playing with a horrible host. Except the problem comes from the game, not the internet. And with a good engine, the worst you hit is 50 fps, as anything below 50 fps would be an anomaly.

Console gamers never play with such horrible framerate issues because of the specifications of the console being able to play the games on medium quality settings (no, you can't change them on consoles). They used to be able to be able to run on high, but high is now medium. If the games were attempted to run on higher settings, you'd run into these problems because the hardware can't handle it.

Play on a PC, with custom hardware, and your views might change.

I can breathe in 30 fps, but I can plant a tree in 60.

Welcome to the PC gaming world. Haha, just kidding, you still play consoles.