Follow Us!

Serious Statistics Review

OpenGL – Dunes:

Remember that under OpenGL the lighting was incorrect on Dunes, which does cast a shadow on the data (I couldn’t help it. I’m running out of things to write as it is) but it can still be interesting to look at.

These graphs do not look all that dissimilar from the Hatsheput graphs, with the data falling closer to 16.667 ms.

Average

Frame Time (ms)

Framerate (FPS)

Run 1

7.48602

133.5809

Run 2

7.414307

134.8707

Run 3

7.414333

134.873

These averages do not look all that bad, but what do the percentiles tell us?

Percentiles

0.1%

1%

99%

99.9%

Run 1

4.754 ms (210.34 FPS)

5.094 ms (196.29 FPS)

12.537 ms (79.76 FPS)

19.252 ms (51.94 FPS)

Run 2

4.886 ms (204.65 FPS)

5.172 ms (193.33 FPS)

12.371 ms (80.83 FPS)

18.462 ms (54.16 FPS)

Run 3

4.595 ms (217.63 FPS)

4.913 ms (203.56 FPS)

12.064 ms (82.89 FPS)

17.900 ms (55.87 FPS)

Most of the time the game was above 60 FPS, but all of the 99.9% values here were below that threshold. Now for the percentiles for specific framerates.

16.667 ms / 60 FPS

20.000 ms / 50 FPS

33.333 ms / 30 FPS

Run 1

0.189644417%

0.072364317%

0.019962570%

Run 2

0.16568574%

0.02967506%

--

Run 3

0.15076992%

0.03460293%

--

The second and third run never dropped to 33.333 ms / 30 FPS, which is why I left those cells empty instead of putting in 0%, though that would be the correct value to present. Time for the QQ plots.

Taking a look at the difference data we see it is greater than it was with Vulkan, but I do not think it is at a noticeable threshold yet.