Part of our daily activities include extensive graphics benchmarking of various video cards and games, often including configuration, OC, and performance tweaks. As part of these benchmarks, we publish tables comparing FPS for the most popular graphics cards, ultimately assisting in determining what the true requirements are for gaming at a high FPS.
Although our test methodology includes extra steps to ensure an isolated, clean operating environment for benchmarking, the basics of testing can be executed on everyday gaming systems. This article explains how to benchmark your graphics card, framerate (FPS), and video games to determine whether your PC can play a game. Note that we've simplified our methodology for implementation outside of a more professional environment.
As a part of our new website design – pending completion before CES – we've set forth on a mission to define several aspects of GPU technology with greater specificity than we've done previously. One of these aspects is texture fill-rate (or filter rate) and the role of the TMU, or Texture Mapping Units.
When listing GPU specifications, we often enumerate the clockrate and TMU count, among other specs. These two items are directly related to one another, each used to extrapolate the “texture filter rate” of the GPU. The terms “Texture Fill-Rate” and “Texture Filter Rate” can be used interchangeably. For demonstration purposes, here is a specifications table for the GTX 980 (just because it's recent):
We're currently in the process of GPU benchmarking Lords of the Fallen, a game that our own Nick Pinkerton previewed back at PAX Prime 2013. The game hosts impressive graphics technology in partial thanks to partnership with nVidia, who offer their GameWorks graphics SDK freely to game developers.
Developers CI Games and Deck13 utilized GameWorks (detailed here) to introduce physics-responsive particle effects, soft body (cloth, fabric) physical effects, volumetric lighting that responds to transparency and surface opacity / reflectivity, and destructible environment effects.
There's been a lot of discussion about Titanfall's performance lately. Our most recent Titanfall GPU performance benchmark showed that the game still exhibits serious issues on certain devices; nVidia cards showed severe stuttering, SLI has micro-stuttering and works better disabled, and the game is simply needlessly large. All these taken into account, the performance issues feel almost unjustified for the visuals -- the game looks fine, sure, but it's not melt-your-GPU level of graphics and certainly isn't spectacular to look at. It's another Source Engine game with adequate graphics. And I'm not saying that's a bad thing, so please don't get me wrong -- just that the performance isn't perfectly-tuned, at least, not yet. More drivers and patches will smooth that out.
I don't want to come off as too harsh, though. The mechanics are enjoyable for certain types of players and the game overall seems 'good,' it's just experiencing some (now-standard) launch issues with PC optimization. All is survivable, though.
In a recent blog post by nVidia's Tony Tamasi and video blog by Assassin's Creed 4 Associate Producer Sylvain Trottier, we've been given deeper technical insight into AC4's driving technologies. From a hardware enthusiast perspective, such videos help us understand and visualize the many acronyms that plague PC graphics, "putting a face to the names," as it were.
In this detailed post, we'll explore the actual real-world meaning of Volumetric FX (fog, smoke), horizon-based ambient occlusion (HBAO), Percentage-Closer Soft Shadows (PCSS), new dynamic lighting FX, and graphics tech in AC4. First, let's start with the new AC4 video that showcases these technologies in action: