Ashes of the Singularity: Escalation

Seen as the holy child of DirectX12, Ashes of the Singularity (AoTS, or just Ashes) has been the first title to actively go explore as many of DirectX12s features as it possibly can. Stardock, the developer behind the Nitrous engine which powers the game, has ensured that the real-time strategy title takes advantage of multiple cores and multiple graphics cards, in as many configurations as possible.

As a real-time strategy title, Ashes is all about responsiveness during both wide open shots but also concentrated battles. With DirectX12 at the helm, the ability to implement more draw calls per second allows the engine to work with substantial unit depth and effects that other RTS titles had to rely on combined draw calls to achieve, making some combined unit structures ultimately very rigid.

Stardock clearly understand the importance of an in-game benchmark, ensuring that such a tool was available and capable from day one, especially with all the additional DX12 features used and being able to characterize how they affected the title for the developer was important. The in-game benchmark performs a four minute fixed seed battle environment with a variety of shots, and outputs a vast amount of data to analyze.

For our benchmark, we run a fixed v2.11 version of the game due to some peculiarities of the splash screen added after the merger with the standalone Escalation expansion, and have an automated tool to call the benchmark on the command line. (Prior to v2.11, the benchmark also supported 8K/16K testing, however v2.11 has odd behavior which nukes this.)

At both 1920x1080 and 4K resolutions, we run the same settings. Ashes has dropdown options for MSAA, Light Quality, Object Quality, Shading Samples, Shadow Quality, Textures, and separate options for the terrain. There are several presents, from Very Low to Extreme: we run our benchmarks at Extreme settings, and take the frame-time output for our average, percentile, and time under analysis.

For all our results, we show the average frame rate at 1080p first. Mouse over the other graphs underneath to see 99th percentile frame rates and 'Time Under' graphs, as well as results for other resolutions. All of our benchmark results can also be found in our benchmark engine, Bench.

MSI GTX 1080 Gaming 8G Performance


1080p

4K

ASUS GTX 1060 Strix 6GB Performance


1080p

4K

Sapphire R9 Fury 4GB Performance


1080p

4K

Sapphire RX 480 8GB Performance


1080p

4K

Ashes Conclusion

Pretty much across the board, no matter the GPU or the resolution, Intel gets the win here. This is most noticable in the time under analysis, although AMD seems to do better when the faster cards are running at the lower resolution. That's nothing to brag about though.

Gaming Performance: Civilization 6 (1080p, 4K, 8K, 16K) Gaming Performance: Shadow of Mordor (1080p, 4K)
Comments Locked

176 Comments

View All Comments

  • djayjp - Monday, July 24, 2017 - link

    Ian, why didn't you check if the OC was being thermally throttled? Easy enough to check this. And easy enough to see if it's the temperature of the cores or not. Surprising you wouldn't include temperature or power consumption data with the OC (though I understand this hasn't typically been a focus of AT). Another site demonstrated throttling at ~95+ C.
  • mapesdhs - Monday, July 24, 2017 - link

    Is that the same site which showed that the TIM Intel is using is just not allowing the heat to get from the die to the cap? Die temp shoots up, cap temp doesn't, even with a chiller cooler.
  • melgross - Monday, July 24, 2017 - link

    This article gives a good reason why huge numbers of core are a waste of money for most users.

    http://www.computerworld.com/article/3209724/compu...
  • Old_Fogie_Late_Bloomer - Monday, July 24, 2017 - link

    Yeah, don't bother starting the article unless you're willing to create yet another useless online identity. Shame, since it seemed moderately interesting, but...
  • alpha754293 - Monday, July 24, 2017 - link

    re: overclocking
    That works well for the occasional heavy workload, but if you are going to be constantly running at peak load (like I did for engineering analysis), overclocking of any kind, from my experience, isn't worth the dead core or entire CPU.

    I've already fried a core on the 3930K once before taking it up from 3.2 GHz stock, 3.5 GHz max TurboBoost to 4.5 GHz.
  • mapesdhs - Monday, July 24, 2017 - link

    Alas this stuff does vary according to the invidual CPU, mbd, RAM, etc. What cooling did you use? Could also be the vcore was too high - a lot of SB-E users employed a high vcore, not realising that using a lower PLL would often make such a high vcore unnecessary. It's even more complicated if one fills all 8 RAM slots on a typical X79 mbd.
  • alpha754293 - Tuesday, July 25, 2017 - link

    The cooling that I was using was Corsair H80i v2.

    The temps were fine and were consistently fine.

    RAM was 8x 8 GB Cruical Ballistix Sport I think DDR3-1600? Something like that. Nothing special, but nothing super crappy either. I actually had the entire set of RAM (all eight DIMMs RMA'd once) so I know that I got a whole new set back when that happened about oh...maybe a-year-and-a-half ago now? Something like that.

    Motherboard was Asus X79 Sabertooth.

    Yeah, I had all 8 DIMM slots populated because it was a cheaper option compared to 4x 16 GB. Besides, using all 8 DIMMs also was able to make use of the quad-channel memory whereas going with 4x 16 GB - you can't/won't (since the memory needed to be installed in paired DIMM slots).

    That CPU is now "castrated" down to 4 cores (out of 6) because 1 of the cores died (e.g. will consistently throw BSODs, but if I disable it, no problems). Makes for a decent job scheduler (or at least that's the proposed task/life for it).
  • Dr. Swag - Monday, July 24, 2017 - link

    Hey Ian, on the first page you listed the turbo of the 7700k as 4.4, whereas it's actually 4.5
  • Yuriman - Monday, July 24, 2017 - link

    Shouldn't the 7700K read "4.2-4.5ghz" rather than 4.2-4.4?
  • Dug - Monday, July 24, 2017 - link

    On RoTR-1-Valley 1080p it shows i5 7600k at 141fps and the i7 7700k at 103fps. Have a feeling these might be transposed.

Log in

Don't have an account? Sign up now