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.
|1. BIF - $340||2. chasp_0 - $251||3. mbutrovich - $250|
|4. Ryu Connor - $250||5. YetAnotherGeek2 - $200||6. aeassa - $175|
|7. dashbarron - $150||8. Lucky Jack Aubrey - $100||9. Captain Ned - $100|
|10. Anonymous Gerbil - $100|
|Cortex-A73 CPU and Mali-G71 GPU power up next-gen phones||10|
|Toshiba's OCZ RD400 512GB SSD reviewed||21|
|Gigabyte shows off its thin Aero laptops and Aorus RGB Fusion Keyboard||20|
|Deals of the week: 25% off Das Keyboard 4 and more||5|
|Everyone and their gran announces non-reference GTX 1080s||50|
|AMD FirePro S7100X is ready to virtualize blade-server graphics||5|
|Thermaltake Pacific water coolers gain hard tube option||10|
|Rumor: Google shames partners into updating Android||42|