Howdy, all. I know you've not seen many articles coming out of Damage Labs lately, but I assure you I am hard at work. In fact, I probably shouldn't be stopping to write this post, but I couldn't resist sharing a little tweak I've been considering making to our game performance analysis.
You may know that we've changed the way we test games in order to better focus on frame latencies rather than FPS averages. One of the struggles we've had in this process is finding the best way to convey a sense of frame latency to the reader. We've made the case for looking at the 99th percentile frame latency—that is, the point at which 99% of all frames in the test run were rendered—and we think that's a helpful metric. However, that number is only a snapshot at a single point. I've been wanting to capture the overall latency picture more fully. Here's my latest attempt. See what you think:
I think it tells the story of frame latencies a little more completely, hopefully without information overload. (And yes, obviously, the GTX 560 Ti has a problem here: it's running out of video RAM capacity at the resolution and settings we tested.)
This is one of several new ideas I'm cooking up. We should have them all implemented in a tasty new review soon.
|The TR Podcast 175: the Zen of chipmaking and ARM's Cortex-A72 revealed||4|
|Elon Musk lays out vision for a battery-powered future||118|
|Inside ARM's Cortex-A72 microarchitecture||34|
|Asus' 144Hz MG279Q monitor may top out at 90Hz with FreeSync||58|
|Deal of the week: A Bay Trail netbook for $161, free case fans, and more||18|
|DirectX 12 Multiadapter shares work between discrete, integrated GPUs||98|
|Gigabyte's 9-series motherboards are Broadwell-ready||46|
|The TR Podcast will be live on Twitch shortly!||3|
|AMD delays FreeSync support for multi-GPU systems||41|