Battlefield 3

Its popularity aside, Battlefield 3 may be the most interesting game in our benchmark suite for a single reason: it’s the first AAA DX10+ game. It’s been 5 years since the launch of the first DX10 GPUs, and 3 whole process node shrinks later we’re finally to the point where games are using DX10’s functionality as a baseline rather than an addition. Not surprisingly BF3 is one of the best looking games in our suite, but as with past Battlefield games that beauty comes with a high performance cost

Battlefield 3

Battlefield 3

Battlefield 3

Battlefield 3

How to benchmark BF3 is a point of great contention. Our preference is to always stick to the scientific method, which means our tests need to be perfectly repeatable or very, very close. For that reason we’re using an on-rails section of the single player game, Thunder Run, to do our testing. This isn’t the most strenuous part of Battlefield 3 – multiplayer can get much worse – but it’s the most consistent part of the game. In general we’ve found that minimum framerates in multiplayer are about half of the average framerate in Thunder Run, so it’s important to frame your expectations accordingly.

With that out of the way, Battlefield 3 ends up being one of the worst games for the 7970 from a competitive standpoint. It always maintains a lead over the GTX 580, but the greatest lead is only 13% at 2560 without any MSAA, and everywhere else it’s 3-5%. Of course it goes without saying that realistically BF3 is only playable at 1920 (no MSAA) and below on any of the single-GPU cards in this lineup, so unfortunately for AMD it’s the 5% number that’s the most relevant.

Meanwhile compared to the 6970, the 7970’s performance gains are also a bit below average. 2560 and 1920 with MSAA are quite good at 30% and 34% respectively, but at 1920 without MSAA that’s only a 25% gain, which is one of the smaller gaps between the two cards throughout our entire test suite.

The big question of course is why are we only seeing such a limited lead from the 7970 here? BF3 implements a wide array of technologies so it’s hard to say for sure, but there is one thing we know they implement in the engine that only NVIDIA can use: Driver Command Lists, the same “secret sauce” that boosted NVIDIA’s Civilization V performance by so much last year. So it may be that NVIDIA’s DCL support is helping their performance here in BF3, much like it was in Civ V.

But in any case, this is probably the only benchmark that’s really under delivered for the 7970. 5% is still a performance improvement (and we’ll take it any day of the week), but this silences any reasonable hope of being able to use 1920 at Ultra settings with MSAA on a single-GPU card for the time being.

Portal 2 Starcraft II
Comments Locked

292 Comments

View All Comments

  • Scali - Saturday, December 24, 2011 - link

    I have never heard Jen-Hsun call the mock-up a working board.
    They DID however have working boards on which they demonstrated the tech-demos.
    Stop trying to make something out of nothing.
  • Scali - Saturday, December 24, 2011 - link

    Actually, since Crysis 2 does not 'tessellate the crap' out of things (unless your definition of that is: "Doesn't run on underperforming tessellation hardware"), the 7970 is actually the fastest card in Crysis 2.
    Did you even bother to read some other reviews? Many of them tested Crysis 2, you know. Tomshardware for example.
    If you try to make smart fanboy remarks, at least make sure they're smart first.
  • Scali - Saturday, December 24, 2011 - link

    But I know... being a fanboy must be really hard these days..
    One moment you have to spread nonsense about how Crysis 2's tessellation is totally over-the-top...
    The next moment, AMD comes out with a card that has enough of a boost in performance that it comes out on top in Crysis 2 again... So you have to get all up to date with the latest nonsense again.
    Now you know what the AMD PR department feels like... they went from "Tessellation good" to "Tessellation bad" as well, and have to move back again now...
    That is, they would, if they weren't all fired by the new management.
  • formulav8 - Tuesday, February 21, 2012 - link

    Your worse than anything he said. Grow up
  • CeriseCogburn - Sunday, March 11, 2012 - link

    He's exactly correct. I quite understand for amd fanboys that's forbidden, one must tow the stupid crybaby line and never deviate to the truth.
  • crazzyeddie - Sunday, December 25, 2011 - link

    Page 4:

    " Traditionally the ROPs, L2 cache, and memory controllers have all been tightly integrated as ROP operations are extremely bandwidth intensive, making this a very design for AMD to use. "
  • Scali - Monday, December 26, 2011 - link

    Ofcourse it isn't. More polygons is better. Pixar subdivides everything on screen to sub-pixel level.
    That's where games are headed as well, that's progress.

    Only fanboys like you cry about it.... even after AMD starts winning the benchmarks (which would prove that Crysis is not doing THAT much tessellation, both nVidia and new AMD hardware can deal with it adequately).
  • Wierdo - Monday, January 2, 2012 - link

    http://techreport.com/articles.x/21404

    "Crytek's decision to deploy gratuitous amounts of tessellation in places where it doesn't make sense is frustrating, because they're essentially wasting GPU power—and they're doing so in a high-profile game that we'd hoped would be a killer showcase for the benefits of DirectX 11
    ...
    But the strange inefficiencies create problems. Why are largely flat surfaces, such as that Jersey barrier, subdivided into so many thousands of polygons, with no apparent visual benefit? Why does tessellated water roil constantly beneath the dry streets of the city, invisible to all?
    ...
    One potential answer is developer laziness or lack of time
    ...
    so they can understand why Crysis 2 may not be the most reliable indicator of comparative GPU performance"

    I'll take the word of professional reviewers.
  • CeriseCogburn - Sunday, March 11, 2012 - link

    Give them a month or two to adjust their amd epic fail whining blame shift.
    When it occurs to them that amd is actually delivering some dx11 performance for the 1st time, they'll shift to something else they whine about and blame on nvidia.
    The big green MAN is always keeping them down.
  • Scali - Monday, December 26, 2011 - link

    Wrong, they showed plenty of demos at the introduction. Else the introduction would just be Jen-Hsun holding up the mock card, and nothing else... which was clearly not the case.
    They demo'ed Endless City, among other things. Which could not have run on anything other than real Fermi chips.
    And yea, I'm really going to go to SemiAccurate to get reliable information!

Log in

Don't have an account? Sign up now