Batman: Arkham City
Now that we've established our evil methods, we can deploy them against Batman. Again, we tested in 90-second sessions, this time while grappling and gliding across the rooftops of Gotham in a bit of Bat-parkour. Again, we're using pretty decent image quality settings at two megapixels; we're just avoiding this game's rather pokey DirectX 11 mode.
These plots are much spikier than what we saw in Skyrim, and they're consistent with what we've seen from this game in the past, in GPU testing. The severity of those spikes looks to be somewhat CPU-dependent, which could prove interesting.
Once again, nearly all of the solutions average over 60 FPS. The Intel chips score higher, but not by as wide a margin as in Skyrim.
The latency picture is pretty remarkable. The Intel chips fare better across the entire curve, including our stopping point at the 99th percentile. Once again, there's little difference between them. The AMD CPUs simply require more time to render frames.
As we saw in Skyrim, the Core i7-3770K fares best of all the processors when dealing with the worst-case scenarios. Regardless of where we put our thresholds—at the equivalent of 20, 30, or 60 FPS—the Intel processors fare better. In spite of averaging over 60 FPS, the FX-8150 and Phenom II X6 burn quite a few cycles on long-latency frames. Having a faster CPU doesn't mean that this game's frequent latency spikes are eliminated, but it means their durations are reduced to much less consequential levels.
|In the lab: FLIR's One thermal camera||41|
|Black Friday deals: Dell's U3415 curved monitor for $650 and more||32|
|Abu Dhabi government fund may be shopping GlobalFoundries||63|
|Asus goes for the gold with its 20th Anniversary GTX 980 Ti||8|
|MSI's Eco motherboards let owners fine-tune power consumption||10|
|Gigabyte's Z170X-Gaming G1 motherboard reviewed||18|
|Star Wars Battlefront video review||40|
|Club 3D active adapters convert DisplayPort 1.2 to HDMI 2.0||23|
|Phanteks' Power Splitter lets two systems run on one PSU||45|
|This is the answer to SSK's question on the Firefox news post.||+38|