Ashes of the Singularity

Sorely missing from our benchmark suite for quite some time have been RTSes, which don’t enjoy quite the popularity they once did. As a result Ashes holds a special place in our hearts, and that’s before we talk about the technical aspects. Based on developer Oxide Games’ Nitrous Engine, Ashes has been designed from the ground up for low-level APIs like DirectX 12. As a result of all of the games in our benchmark suite, this is the game making the best use of DirectX 12’s various features, from asynchronous compute to multi-threadeded work submission and high batch counts. What we see can’t be extrapolated to all DirectX 12 games, but it gives us a very interesting look at what we might expect in the future.

Ashes of the Singularity - 3840x2160 - Extreme Quality (DX12)

Ashes of the Singularity - 2560x1440 - Extreme Quality (DX12)

Of all of the games in our benchmark suite, Ashes is perhaps the most unusual. Besides being built for low-level APIs like DirectX 12 from the start, its rendering optimizations scale very well with resolution. As a result it takes a lot of rendering power to play Ashes with all the bells & whistles turned on, but once you can reach that point, going to 4K isn’t too much harder.

In any case, the GTX 1080 Ti becomes the first card to crack 60fps at 4K in this game. In doing so it’s 27% faster than the GTX 1080, and 71% faster than the GTX 980 Ti. Performance has actually reached a point that if we drop to 1440p, we start being CPU-limited a not-insignificant percentage of the time. So the GTX 1080 Ti outright needs 4K to really put its best foot forward.

DiRT Rally Battlefield 4
Comments Locked

161 Comments

View All Comments

  • Jon Tseng - Thursday, March 9, 2017 - link

    Launch day Anandtech review?

    My my wonders never cease! :-)
  • Ryan Smith - Thursday, March 9, 2017 - link

    For my next trick, watch me pull a rabbit out of my hat.
  • blanarahul - Thursday, March 9, 2017 - link

    Ooh.
  • YukaKun - Thursday, March 9, 2017 - link

    /claps

    Good article as usual.

    Cheers!
  • Yaldabaoth - Thursday, March 9, 2017 - link

    Rocky: "Again?"
  • Ryan Smith - Thursday, March 9, 2017 - link

    No doubt about it. I gotta get another hat.
  • Anonymous Blowhard - Thursday, March 9, 2017 - link

    And now here's something we hope you'll really like.
  • close - Friday, March 10, 2017 - link

    Quick question: shouldn't the memory clock in the table on the fist page be expressed in Hz instead of bps being a clock and all? Or you could go with throughput but that would be just shy of 500GBps I think...
  • Ryan Smith - Friday, March 10, 2017 - link

    Good question. Because of the various clocks within GDDR5(X)*, memory manufacturers prefer that we list the speed as bandwidth per pin instead of frequency. The end result is that the unit is in bps rather than Hz.

    * http://images.anandtech.com/doci/10325/GDDR5X_Cloc...
  • close - Friday, March 10, 2017 - link

    Probably due to the QDR part that's not obvious from reading a just the frequency. Thanks.

Log in

Don't have an account? Sign up now