New Games, FCAT, & The Test

For the launch of the GTX Titan we refreshed our benchmark suite and swapped out several of our games for newer titles. At the time we opted to start with 8 games so that we would have the space to add more, as Titan was launching just ahead of the spring launch window for several major AAA titles. With the launch of the 7990 we’re finally rounding out the 2013 benchmark suite at 10 games with the addition of two more games: Bioshock Infinite and Crysis 3.

Bioshock Infinite is Irrational Games’ latest entry in the Bioshock franchise. Though it’s based on Unreal Engine 3 – making it our obligatory UE3 game – Irrational had added a number of effects that make the game rather GPU-intensive on its highest settings. As an added bonus it includes a built-in benchmark composed of several scenes, a rarity for UE3 engine games, so we can easily get a good representation of what Bioshock’s performance is like.

Our other addition to the benchmark suite needs no introduction. With Crysis 3, Crytek has gone back to trying to kill computers, taking back the “most punishing game” title in our benchmark suite. Only in a handful of setups can we even run Crysis 3 at its highest (Very High) settings, and that’s still without AA. For the purpose of our benchmark we’re playing a short game of follow the leader with Psycho in the game’s introductory level, Post-Human. The storm-battered scenario ends up being one of the most GPU-intensive scenes in the game, while simultaneously being relatively light when it comes to CPU usage.

FCAT

First revealed last month, the Frame Capture and Analysis tool (FCAT) has significantly altered how we go about measuring the smoothness of video game rendering. By marking frames with a color strip and then analyzing recordings of the resulting output, we can tell just how far apart frames are when being displayed, and how much of a frame has been displayed.

Our goal with FCAT was to run an in-depth article about it shortly before the launch of the 7990 as a preparatory article for today’s launch. However like most ambitious goals, that hasn’t panned out. AMD of course is dropping new drivers for the 7990 – Catalyst 13.5b2 – but NVIDIA also dropped their new 320.00 drivers at the end of last week. As a result we’ve effectively had to rebuild our benchmark results in the last week, and throw out much of the old FCAT data we had already collected. Coupled with driver problems and a later problem with FCAT capture (which has since been resolved), and we’ve been left with plenty to do and not enough time to do it.

The end result is that we’re not going to have FCAT data for today’s launch, as there simply hasn’t been enough time to put it together. FCAT was specifically designed for multi-GPU testing so this is an ideal use case for it and we’d otherwise like to have it, but without complete results it’s not very useful. Sorry guys.

The good news is that this means we have (and will be compiling) FCAT results for our cards based on the very latest drivers. So we’ll get to the bottom of frame pacing on the 7990, GTX 690, and more with an FCAT article later this week or early next week. So please stay tuned for that.

On a side note, AMD is also sampling a very early preview of their new frame pacing optimized driver to the press for this launch. It’s based off of an older branch of the Catalyst driver set and AMD still has quite a bit of work to go until it’s in shipping condition. But for anyone wondering if AMD can put together a good frame pacing solution, things are looking good right now. We’ll have more on this, including some early results, in our upcoming FCAT article.

The Test

For the launch of the 7990, AMD is sampling the press with Catalyst 13.5b2. This is the driver from the next branch of the software, so it includes performance improvements for several games. We’ve seen improvements in DiRT: Showdown, Sleeping Dogs, and Hitman: Absolution, though until AMD publically publishes the driver and its associated release notes we don’t have a complete list of what games are impacted.

Meanwhile as previously mentioned, NVIDIA just released the first beta of their next branch too, R319. The 320.00 betas were released yesterday, and include performance improvements in DiRT: Showdown, Sleeping Dogs, Crysis 3, and several other games as listed in NVIDIA’s notes. Unfortunately these drivers have also turned up an issue in Battlefield 3 and SLI; terrain rendering isn’t working correctly, at least on our testbed. We’re still working with NVIDIA on this one as it looks to be a rare issue (no one else has reproduced it thus far), so for the moment we’re sticking with our 314.22 BF3 results.

On a final note, with our site design complete, GPU Bench 2013 is finally live. As always, you can find our latest GPU performance results in there and use those results compare the various cards we’ve benchmarked thus far.

CPU: Intel Core i7-3960X @ 4.3GHz
Motherboard: EVGA X79 SLI
Power Supply: Antec True Power Quattro 1200
Hard Disk: Samsung 470 (256GB)
Memory: G.Skill Ripjaws DDR3-1867 4 x 4GB (8-10-9-26)
Case: Thermaltake Spedo Advance
Monitor: Samsung 305T
Video Cards:

AMD Radeon HD 6990
AMD Radeon HD 7970
AMD Radeon HD 7970 GHz Edition
AMD Radeon HD 7990
PowerColor Radeon HD 7990 Devil13
NVIDIA GeForce GTX 680
NVIDIA GeForce GTX 690
NVIDIA GeForce GTX Titan

Video Drivers: NVIDIA ForceWare 320.00
AMD Catalyst 13.5 Beta 2
OS: Windows 8 Pro

 

Meet The Radeon HD 7990 DiRT: Showdown
Comments Locked

91 Comments

View All Comments

  • Ryan Smith - Wednesday, April 24, 2013 - link

    One of our goals this year is to get a 4K monitor. But if so it will be a bit more mundane; something cheaper and more accessible, and something that can do 4K off of 1 DP 1.2 connection and present itself as one monitor.
  • mayankleoboy1 - Wednesday, April 24, 2013 - link

    How do you use SSAA in Crysis:Warhead ?
  • Ryan Smith - Wednesday, April 24, 2013 - link

    You can force it through the drivers on both AMD and NVIDIA cards.
  • Veteranv2 - Wednesday, April 24, 2013 - link

    One giant massive pro for the 7990 is compute performance. Nvidia clearly misses the ball there.
  • StealthGhost - Wednesday, April 24, 2013 - link

    Massive...for the 5% of people who buy cards like this and don't game
  • Veteranv2 - Wednesday, April 24, 2013 - link

    Not all graphic cards are bought for gaming....
    And certainly in the future, compute for GPU will be more and more important.
    Have you looked at the graphs? AMD has a GIANT leap over Nvidia.
  • Ktracho - Wednesday, April 24, 2013 - link

    I think the compute benchmarking may be flawed. How many people who buy the Titan for compute will use OpenCL? I suspect almost all would be using CUDA. Since CUDA isn't available on AMD cards, I think a better benchmark would be HPL, which is a common benchmark in the HPC world. This would allow each manufacturer to show how much sustained performance a given card is capable of achieving, without being limited by the constraint of having to use OpenCL or DirectCompute, or whatever. Without such benchmark results, all that can be concluded without reservation is that if you must use OpenCL, then you really should limit yourself to AMD (at least for now).
  • BrightCandle - Wednesday, April 24, 2013 - link

    Lets be clear, you went live without FCAT results, which are singularly the most important aspect of reviewing this card as every other site has shown. Instead you chose to go with single FPS numbers, again.

    Pages upon pages of useless numbers, because the card doesn't actually display those frames. Using an older driver would have been better than using a prototype driver users aren't expecting to use for at least another month.
  • MartinT - Wednesday, April 24, 2013 - link

    I agree, the data set in this review is of very limited import, especially for a CF-on-a-stick solution.

    You probably should have devoted more time to getting frame times into your workflow, and less time benchmarking so many games using less than relevant methodology.

    Looking forward to your write up of the frame time data, but this article is a serious waste of time on your part, I'm afraid.
  • Ryan Smith - Wednesday, April 24, 2013 - link

    Obviously we planned to have full FCAT data for this, but fate wasn't so agreeable. In any case FCAT is meant to augment our FPS data, not replace it. So we needed to have the FPS numbers before we could dig into FCAT for the full breakdown.

    And as a point of clarification, we aren't using the prototype driver for these results. We're using Catalyst 13.5b2, which should see a public release in the very near future. The prototype driver is another driver entirely, which we aren't using for these tests.

Log in

Don't have an account? Sign up now