One of the longest running gaming franchises around, the Civilization series goes all the way back to my high school years. There have been many changes along the way, but the core gameplay has remained. Civilization is a turn-based strategy game where you guide your fledgling empire from the early stages of a single settlement up through global endgame battles for domination. The games have all been digital crack as far as I'm concerned, and I know at least a few people that failed – or very nearly failed – out of college thanks to time spent playing various incarnations of Civilization. The latest update, as the name implies, takes the series outside the confines of Earth once more – a place Civilization hasn't really been since Alpha Centauri back in 1999. If you happen to enjoy turn-based strategy like Ryan or me, say goodbye to your loved ones and prepare for a trip down the rabbit hole of Civilization once more….

One of the interesting aspects with Civilization: Beyond Earth is that the developers, Firaxis, have opted to include support for AMD's Mantle API. We've been over this subject quite a few times, but the core idea is that Mantle provides low level access to the graphics hardware, potentially allowing for improved performance or other improvements. We've seen other games use Mantle (Battlefield 4, Thief, Plants vs. Zombies: Garden Warfare, and Sniper Elite 3), but this is the first game to really do something more with Mantle than reducing the cost of draw calls. That's still a benefit that Civilization: Beyond Earth enjoys, but Firaxis has gone a step further for owners of CrossFire setups and has enabled a custom Split-Frame Rendering (SFR) approach for multiple GPUs instead of the typical Alternate-Frame Rendering (AFR) that most games use with CrossFire and SLI.

I like the idea of SFR, as it means adding multiple GPUs won't increase input latency, and in fact from a theoretical perspective SFR could actually reduce latency. Consider one GPU that takes 20ms to render a frame, and if you have two GPUs each taking 20ms you can get a new frame every 10ms, but buffering means you're still seeing latency of around 20ms (and in worst-case scenarios up to 40ms). With SFR, the two GPUs could potentially work together to render a single frame in 10ms, cutting input latency in half. That's the potential upside, but of course it can be far more complex to implement SFR (which is why most games choose to go with AFR).

I don't have multiple NVIDIA GPUs to test SLI performance, and normally I wouldn't worry too much about CrossFire, but the Mantle SFR support does make for a potentially interesting outcome so I'll at least test the two CrossFire configurations I have on hand (R9 290X and R9 280). I should note that the preview release of Civilization: Beyond Earth that we're testing does have a specific limitation that prevents it from using more than two GPUs; in fact, if you have more than two GPUs, you apparently need to disable the extra GPUs in the device manager or the game won't launch, though a 0-day patch is in the works to address this. Anyway, we'll look at CrossFire performance with and without Mantle later on.

Test Settings

As our testing environments at AnandTech tend to vary a bit by editor, let me again reiterate that I'm not using the same setup as Ryan uses for our GPU reviews; for gaming benchmarks like this, I have the following hardware:

Gaming Benchmarks Test Systems
CPU Intel Core i7-4770K (4x 3.5-3.9GHz, 8MB L3)
Overclocked to 4.1GHz
Motherboard Gigabyte G1.Sniper M5 Z87
Memory 2x8GB Corsair Vengeance Pro DDR3-1866 CL9
GPUs Sapphire Radeon R9 280
Sapphire Radeon R9 280X
Gigabyte Radeon R9 290X
EVGA GeForce GTX 770
EVGA GeForce GTX 780
Zotac GeForce GTX 970
Reference GeForce GTX 980

GeForce GTX 980M (MSI GT72 Dominator Pro)
GeForce GTX 880M (MSI GT70 Dominator Pro)
GeForce GTX 870M (MSI GS60 Ghost 3K Pro)
GeForce GTX 860M (MSI GE60 Apache Pro)
Storage Corsair Neutron GTX 480GB
Power Supply Rosewill Capstone 1000M
Case Corsair Obsidian 350D
Operating System Windows 7 64-bit

Basically, my hardware is more of a "mainstream" gaming setup rather than an extreme configuration (e.g. LGA2011), though I did overclock the CPU to 4.1GHz to remove as much of the CPU bottleneck as possible. For anyone running a single GPU – and in most cases even with two GPUs – this sort of build is more than fast enough to keep the GPUs happy. I've also upgraded to a 4K display, Acer's XB280HK G-SYNC panel, which will help tax the faster GPUs. And it's a good thing too, as Civilization: Beyond Earth can hit the CPU pretty hard, with ultra-high resolutions being one of the few things that will help differentiate between the various high-end GPUs.

For testing Civilization: Beyond Earth, I've selected four settings: 3840x2160, 2560x1440, and 1920x1080 with Ultra quality and 4xMSAA, and then as a slightly less strenuous setting I've also tested 1920x1080 High without any anti-aliasing. I'm using the latest AMD 14.9 Beta 2 Catalyst drivers, which should be publicly available by the time you read this; for NVIDIA GPUs I've updated to the recently released 344.48 WHQL driver that's "Game Ready" for Civilization: Beyond Earth. Of course this is an AMD Gaming Evolved title, and with Mantle support I've also tested the AMD GPUs using both the DX11 rendering path as well as the Mantle rendering path. There doesn't appear to be any difference in terms of image quality, so Mantle is being used purely as an option to increase performance.

One final item to note is that the built-in benchmark basically represents something of a worst-case scenario for performance. Civilization: Beyond Earth has a grid of hexes over the terrain, and early on there aren't too many units on screen. Near the end of a game however, it's not unusual to have most hexes occupied – or at least a lot of them – and that can cause performance to tank. As you can see in the above screenshot taken from the benchmark, Civilization: Beyond Earth really can't get much worse than what we're showing here; very nearly every hex on the map is occupied. And with that said, let's see how things play out….

Civilization: Beyond Earth Performance


View All Comments

  • Parrdacc - Thursday, October 23, 2014 - link

    Well, have a Happy Birthday!! Reply
  • przemo_li - Thursday, October 23, 2014 - link

    I think that You make good point about $$ on CPU vs $$ on GPU... for now.

    Cause if Mantle can let us spent $$$ less on CPU then, why not?

    (That ofc. would require more widespread support in games.... Or DX12 Or OpenGL AZDO)
  • nevertell - Thursday, October 23, 2014 - link

    Not necessarily. Civilization V was a cpu limited game for the most part. Reply
  • LemmingOverlord - Friday, October 24, 2014 - link

    indeed, Civ V was a great CPU benchmark (akin to Supreme Commander), and the performance scaled quite well with added cores... Reply
  • SuperVeloce - Friday, October 24, 2014 - link

    Civ V scaled well with up to 4 cores if my memory serves me right. Not much more with 6+ cores. Reply
  • just4U - Friday, October 24, 2014 - link

    I was playing civ5 this past week while waiting for the new game... and you know... even on my 4790K it bogs down on big maps. Reply
  • jaredjeya - Friday, October 24, 2014 - link

    Especially as turn time and not FPS becomes the limiting factor late into the game. Anything above 20fps is decent, but if turns take a minute then it's intolerable. Reply
  • doronnac - Thursday, October 23, 2014 - link

    Min. FPS should be tested as it's more important than average when almost all cards demonstrate more than playable performance even at 4K. Reply
  • Mikemk - Thursday, October 23, 2014 - link

    "the built-in benchmark basically represents something of a worst-case scenario for performance"
    Page 1
  • JarredWalton - Thursday, October 23, 2014 - link

    I have logs including minimum FPS, but time constraints kept me from spending too much effort analyzing them. What I can say is that when the game zooms all the way out during the benchmark sequence, that's when the minimum occurs and it's usually around 2/3 of the average FPS. GPUs with less VRAM may also be hit harder though. Let me see if I can add some charts for minimums, now that I've managed to get some sleep. :-) Reply

Log in

Don't have an account? Sign up now