Battlefield: Bad Company 2

Now approaching a year old, Bad Company 2 remains as one of the cornerstone DX11 games in our benchmark suite. Based on the Frostbite 1.5 engine, it will be replaced in complexity by the DX10+ only Frostbite 2 engine (and Battlefield 3) later this year.  As BC2 doesn’t have a built-in benchmark or recording mode, here we take a FRAPS run of the jeep chase in the first act, which as an on-rails portion of the game provides very consistent results and a spectacle of explosions, trees, and more.

With Bad Company 2, AMD and NVIDIA are once again on much more equal footing, and we have much more interesting results.

Compared to AMD’s lineup the GTX 560 Mid falls behind the 6870, but it’s very close with a difference under 2fps. Our higher clocked GTX 560 configurations can’t quite catch up to the 6970 however, with the latter taking a small but notable lead.

As for NVIDIA’s lineup, the relative performance is roughly the same as in most of our other games. The GTX 560 Mid has 21% on the GTX 460 1GB, while trailing the GTX 560 Ti by 8%. Amusingly, at the same time as all of this the GTX 560 Mid manages to beat the GTX 470, thanks to the massive difference in clockspeed between the two, leading to the GTX 560 Mid nullifying the latter’s functional unit count advantage.

Civilization V STALKER: Call of Pripyat
Comments Locked

66 Comments

View All Comments

  • TheJian - Wednesday, May 18, 2011 - link

    See my other posts. Nvidia finally got multithreaded rendering finished in their drivers (which should affect many games now, it's not GAME specific). Expect AMD to get theirs done soon. This isn't Civ5 or Anandtech favoring NV, it's just the beat AMD to the punch in getting drivers finished. If AMD takes another year to get their drivers done, I'm glad they report this. I hope AMD gets them done soon, or the next set of cards that get benched might show quite a few games with AMD bunched at the bottom of the list.

    NOTE: this is a DRIVER issue, not game issue. Both sides have been working on getting this in their drivers for a while. It's about time :) The game had this in it all the time (many other too, get ready for speedups if you own NV and running 2.75 drivers (whatever is latest from NV). Unfortunately my 5850 has to wait for AMD. :(
  • JarredWalton - Tuesday, May 24, 2011 - link

    You know what the best part is about Civ5? AMD is the one that gave out copies of the game to reviewers. Yup -- that and F1 2010.
  • L. - Thursday, May 19, 2011 - link

    Errr/ metacritic lol ?

    We're talking benchmarking here, not playing the game.

    AMD being poor is their problem, we shouldn't care ;)

    Besides, the way people rate on metacritic or any critic source for anything is at most a relative indicator of how people who take the time to vote feel about stuff... doesn't help that much does it ?

    Crysis 2 is NOT in the same series as Crysis 1. If you don't know why, read some more about it.
  • L. - Thursday, May 19, 2011 - link

    Two words for you mate, Bench and Mark
    The purpose of benchmarking is to get a relative idea of the performance of a component, not to test every little game out there, because of that reviewers attempt to have a most relevant panel of games/ benchmarks to test the gfx cards.

    Crysis 2 is not (yet) a relevant benchmark. Maybe when they're done writing the engine for PC's it will be, but now it's just a worthless console port.

    IF you think they're lazy, just post a list of the games you would use to benchmark and ask people how useful they find those.
  • Spoelie - Wednesday, May 18, 2011 - link

    Metro 2033 is a game that requires the force scaling flag I believe. It ignores the scaling settings in AMD's drivers on windows 7 at least..

    Coloring is wrong on the Civ5 graph (last one)
  • GeorgeH - Wednesday, May 18, 2011 - link

    Taken out of the noise of the other comment stream:

    "RE: Time to change the tests by Ryan Smith on Tuesday, May 17, 2011
    The test suite is due for a refresh, and will either be updated at the end of this month or next month once we build our new SNB testbed."

    Weren't you waiting for SNB-E? Isn't that a Q4 release? Or by "SNB" do you mean "Bulldozer" and know something that we don't?

    You've got me all curious and maybe excited and more curious and now I-don't-know-what-to-think.

Log in

Don't have an account? Sign up now