Follow Us!

Serious Statistics Review

DirectX 11 – Dunes:

Back in Dunes again and here are the course graphs, which do not show any scale-expanding outliers!

Turning to the averages, here is what we get:

Average

Frame Time (ms)

Framerate (FPS)

Run 1

5.47773

182.5569

Run 2

5.530337

180.819

Run 3

5.596548

178.6791

If you pop back to the Vulkan page for Dunes you will see these two APIs are practically tied here. Time to see if the percentiles are also so near to each other.

Percentiles

0.1%

1%

99%

99.9%

Run 1

3.863 ms (258.87 FPS)

4.076 ms (245.34 FPS)

7.985 ms (125.23 FPS)

9.949 ms (100.51 FPS)

Run 2

3.931 ms (254.39 FPS)

4.128 ms (242.25 FPS)

8.093 ms (123.56 FPS)

10.051 ms (99.49 FPS)

Run 3

3.859 ms (259.13 FPS)

4.086 ms (244.74 FPS)

8.393 ms (119.14 FPS)

10.524 ms (95.02 FPS)

These numbers are interesting as we can see DirectX 11 directly trading blows with Vulkan. Vulkan was winning in Hatsheput, which speaks to the importance of running these tests in different maps that provide different experiences.

Looking at where 60 FPS occurs in the data we find encouraging results for DirectX 11.

16.667 ms / 60 FPS

20.000 ms / 50 FPS

33.333 ms / 30 FPS

Run 1

0.001826217%

--

--

Run 2

0.005531585%

--

--

Run 3

0.003731622%

0.001865811%

--

Only on the third run were frame times recorded that got to 50 FPS, which is pretty nice to see. Of course this is all outliers, but now I am in the habit of showing more than I need to for these tables.

Everything is looking good so far, and the difference data is likely to agree.