EDITORS NOTE: Our performance evaluation was done entirely post-patch that was issued after we had access to the game for several days resulting in retesting most of our cards. When viewing performance issues with this game it’s important to know whether the evaluation was made on the original build of the game or the patched version that matches what will be released when the game goes live.
Hot on the heels of Death Stranding we PC Gamers get access to another hot exclusive to the Playstation 4 world, Horizon Zero Dawn Complete Edition. Horizon Zero Dawn has been out since February of 2017, so it’s not like it’s a new game, but it’s a very welcome addition to the PC universe. If you’re looking for a review of the game itself may I direct you to our review of the original release by Chris Wray because the Horizon Zero Dawn PC release is essentially the same game therefore the original review of the game itself still holds up. But, this is all about the technical side of things.
Horizon Zero Dawn for PC is still powered by the Decima engine, just like Death Stranding, but it comes with fewer bells and whistles, most notably is the absence of DLSS 2.0, and unfortunately no FidelityFX as well. But, unlike early reporting, I’m happy to say that ultrawide support is present as well as a FOV slider, these were originally said that they were not going to be included in order to ‘preserve the original experience of the game’, but I’m very happy to see them included. As you’ll see down the way, Ultrawide is a bit more stressful than usual in this open-world adventure. The biggest benefit of this game on PC (outside of increased resolution and framerate) is the ability to crank way beyond the original release in draw distance as well as the excellently enhanced ambient occlusion implementation that really makes the world pop.
Testing Methodology
First, I want to make a request to Sony and Guerrilla, GET RID OF THE 10 MINUTE OPTIMIZATION WINDOW for when you update your driver or change any hardware. Okay, got that out of my system. I want to drop a good tip on this game when you launch it, alt+enter to take it out of full-screen and then alt+enter back in, there is a weird bug that ‘should’ be addressed where the game is rendered at the set resolution but is downscaled then upscaled back and it just looks odd.
Horizon Zero Dawn comes to us with several arrays of presets; Favor Performance, Original, Favor Quality, and Ultimate Quality. But, that being said, there seems to be a change in presets across GPU configurations resulting in the Ambient Occlusion settings being variable, so for our testing, we used the Ultimate Quality settings but changed the Ambient Occlusion setting to ‘Original’ for consistency. Horizon Zero Dawn also included a very solid and representative (from my experience post-patch) built-in benchmarking utility. We used that for our testing and took the results from the 176-second run.
Once we had the results from 3 runs, after discarding an initial burner run for loading purposes, we took the average of average frame rates as well as the 1% Percentile results from the run. We report our performance metrics as average frames per second and have moved away from the 1% and .1% reporting and are now using the 1% Percentile. For those uncertain of what the 1% Percentile is, representing is easily explained as showing only 1 frame out of 100 is slower than this frame rate. Put another way, 99% of the frames will achieve at least this frame rate.
*at the time of our review a known issue with the game is that Anisotropic Filtering is not functioning, but in previous games we found this setting to be superfluous in affecting overall performance.
Test System
| Components | Z370 |
|---|---|
| CPU | Intel Core i9-9900k @ 5GHz |
| Memory | 32GB Mushkin Redline DDR4 3600 |
| Motherboard | EVGA Z370 Classified K |
| Storage | Kingston KC2000 1TB NVMe SSD |
| PSU | Cooler Master V1200 Platinum |
| Windows Version | Latest verion of windows at the time of testing |
| Hardware-Accelerated GPU Scheduling | On if supported by GPU and driver. |
Graphics Cards Tested
| GPU | Architecture | Core Count | Clock Speed | Memory Capacity | Memory Speed |
|---|---|---|---|---|---|
| NVIDIA RTX 2080ti FE | Turing | 4352 | 1350/1635 | 11GB GDDR6 | 14Gbps |
| NVIDIA RTX 2080 SUPER FE | Turing | 3072 | 1650/1815 | 8GB GDDR6 | 15.5Gbps |
| NVIDIA RTX 2070 SUPER FE | Turing | 2560 | 1605/1770 | 8GB GDDR6 | 14Gbps |
| NVIDIA RTX 2060 SUPER | Turing | 2176 | 1470/1650 | 8GB GDDR6 | 14Gbps |
| NVIDIA RTX 2060 FE | Turing | 1904 | 1365/168 | 6GB GDDR6 | 14Gbps |
| ZOTAC Gaming GTX 1660 | Turing | 1408 | 1530/1785 | 6GB GDDR5 | 8Gbps |
| ZOTAC GTX 1650 SUPER | Turing | 1280 | 1530/1725 | 4GB GDDR6 | 12Gbps |
| NVIDIA GTX 1080 FE | Pascal | 2560 | 1607/1733 | 8GB GDDR5X | 10Gbps |
| NVIDIA GTX 1070 FE | Pascal | 1920 | 1506/1683 | 8GB GDDR5 | 8Gbps |
| NVIDIA GTX 1060 FE 6GB | Pascal | 1280 | 1506/1708 | 6GB GDDR5 | 8Gbps |
| AMD Radeon RX 5700XT | Navi 10 | 2560 | 1605/1755/1905 | 8GB GDDR6 | 14Gbps |
| AMD Radeon RX 5700 | Navi 10 | 2304 | 1465/1625/1725 | 8GB GDDR6 | 14Gbps |
| Sapphire RX 5600 XT | Navi 10 | 2304 | 1130/1660/1750 | 6GB GDDR6 | 14Gbps |
| AMD RX Vega 64 | Vega 10 | 4096 | 1247/1546 | 8GB HBM2 | 945Mbps |
| AMD RX Vega 56 | Vega 10 | 3584 | 1156/1471 | 8GB HBM2 | 800Mbs |
| Sapphire RX 5500 XT 4GB | Navi 14 | 1408 | 1737/1845 | 4GB GDDR6 | 14Gbps |
| MSI RX 580 Armor 8GB | Polaris 20 | 2304 | 1366 | 8GB GDDR5 | 8Gbps |
| Sapphire Nitro+ RX 570 4GB | Polaris 20 | 2048 | 1340 | 4GB GDDR5 | 7Gbps |
Drivers Used
| Drivers | |
|---|---|
| Radeon Settings | 20.8.1 |
| GeForce | 451.67 |
Preset Scaling At 4K
Testing presets at 4K gives us a couple of quick metrics before diving into the game too deeply. First off, it shows us how the game looks at various presets as well as how performance scales with those settings. Horizon Zero Dawn scales quite well in visuals with the Favoring Performance setting still looking decent enough to not feel like you’re missing out on much, but the detail draw distance on the Ultimate Quality is worth the sacrifice if you can muster over the 45 FPS mark, yes 60+ is preferred but the pacing of the game, and especially if you’re using a controller, is quite comfortably played.
But, clawing back performance is not that difficult, moving to Original quality can gain you nearly 50% performance increase but I would wager you might be better off using the in-game slider and moving to around the 80% resolution mark and applying either the GeForce Sharpening filter or the Radeon Image Sharpening feature to gain back some of that sharpness. This game could have certainly benefited from either DLSS 2.0 or FidelityFX, both of which could be ported into the game with FidelityFX likely being the easier implementation. We’ve seen both at work in the engine with Death Stranding and it would be wonderful to see it here as well.
<!—->
<!—->
Intel Core Scaling Performance
While this test won’t tell just how many cores and threads the game can and will use, it does show how the game performs as you move up in cores and threads available. These were tested at the 1080p settings that we tested the rest of the results while pairing the CPU with the RTX 2080 Ti Founders Edition. While this does not take into account the cache difference you would see with Intel CPUs as you move through their offering stack it does give us a better idea of how the game benefits and behaves from more cores and threads.
Scaling in Horizon Zero Dawn isn’t that exciting to look at when viewed at 1080p, it shows performance hitting its side at six cores, but maintaining decent at quad-core arrangements. If you’re rocking a dual-core with quad threads on this one you’re likely to see issues, but without multi-threading, you’ll be left out in the cold on a dual-core. The game will launch on a dual-core, at least the menus as the game never loaded into a playable scene. The most interesting note is that on six and eight-core arrangements the inclusion of multi-threading doesn’t seem to help and at the high end, actually hurts performance slightly. One thing is clear, this game is exceptionally GPU heavy and is relatively unaffected at even 1080p with the RTX 2080Ti when reducing core and thread count.
<!—->
Graphics Card Results
1080p
<!—->
Ultrawide 1080p
<!—->
1440p
<!—->
Ultrawide 1440p
<!—->
UHD 4K
<!—->
Conclusion
Overall the PC performance of Horizon Zero Dawn would have been pretty shoddy if we had gone off the original build of the game so we’re glad they’ve cleaned things up in time for the launch. This gives us hope that issues like the nonworking Anisotropic Filtering adjustment will be fixed, but this isn’t giving the game a pass for that being missed. The other oddity you’ll find pretty apparent here is going to be the 30 fps facial animations, that really cause cutscenes to feel odd, especially when, at times, the eyes are moving at full speed.
BUT, performance is not quite as good as I hoped for and really shows that something like DLSS 2.0 or FidelityFX would make an excellent addition here to claw back some performance on some cards at higher resolutions. Ultrawide resolutions are unusually difficult to run at levels they do in other games, there seems to be a bigger hit than usual. Neither GPU vendor has any major issues with the launch of the game, so any problems to be uncovered will likely be with the game itself and could, hopefully, be patched in the future
The Navi cards did spectacular here delivering better than anticipated performance numbers when putting up against their direct competitors. Showing greater than a 10% performance advantage in with the recent GPUs. Their Vega lineup and Polaris do okay against the Pascal counterparts. One of the more interesting points is how utilizing Hardware Accelerated GPU Scheduling really pushes the GeForce GTX 1650 to parity with the RX 5500XT and kisses the GTX 1660 despite it being the more powerful card with more VRAM.
Something of note in the results in where cards register a Zero number. What I found was a few cards in the Radeon lineup seem to fall victim to assets not loading. I recorded them as Zero because it’s essentially unplayable because all that will load in are characters, the skybox, and land formations. This is an unfortunate effect that only seems to affect the Radeon cards, the GeForce cards handle the game perfectly fine across the board. Something to consider is it is only happening at resolutions above and beyond what those cards are designed for.
Before the patch there were stability issues abound, sometimes the game would stutter at a strange interval no matter what was going on, and often would simply not launch properly. I’m glad I waited until after the patch dropped to start recording data and found the game to be in a much more attractive state. I can’t defend the odd 30 FPS facial animations but it is a game you’ll probably want to cap at around 60 FPS anyway to smooth the fluctuations out. The issue with the Anisotropic Filtering bug should be alleviated by the time the game goes live. But, for now, I’ll be back in and exploring the world with Aloy.
