DiRT: Showdown

Racing to the front of our benchmark suite is our racing benchmark, DiRT: Showdown. DiRT: Showdown is based on the latest iteration of Codemasters’ EGO engine, which has continually evolved over the years to add more advanced rendering features. It was one of the first games to implement tessellation, and also one of the first games to implement a DirectCompute based forward-rendering compatible lighting system. At the same time as Codemasters is by far the most prevalent PC racing developers, it’s also a good proxy for some of the other racing games on the market like F1 and GRID.

DiRT: Showdown - 5760x1200 - Ultra Quality + 4x MSAA + Adv. Lighting

DiRT: Showdown - 2560x1440 - Ultra Quality + 4x MSAA + Adv. Lighting

DiRT: Showdown - 1920x1080 - Ultra Quality + 4x MSAA + Adv. Lighting

DiRT: Showdown is something of a divisive game for benchmarking. The game’s advanced lighting system, while not developed by AMD, does implement a lot of the key concepts they popularized with their Leo forward lighting tech demo. As a result performance with that lighting system turned on has been known to greatly favor AMD cards, which is exactly what’s going on here. But since we’re looking at high-end cards there’s little reason not to be testing with it turned on since even a lone GTX 680 can push 30fps with 5760 with these advanced effects turned on.

In any case, 7990 completely clobbers everything else here short of the 7970GE CF. As heavy as the load is from turning these advanced effects on, the 7990 is still more than fast enough to crack 60fps even at 5760.

New Games, FCAT, & The Test Total War: Shogun 2
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