Games each driver could run (an estimate from its feature list): green likely, yellow maybe, orange limited, red no
StockDX92002+DX102006+DX112009+DX122015+Switch
CustomDX92002+DX102006+DX112009+DX122015+Switch
compute_nbody0% faster
hdr_2160p1% faster
oit_linked_lists1% faster
pipeline_barriers2% faster
subpasses0% faster
Custom driver against stock, per scene. Bars to the right are faster, to the left slower.
Small areas of the picture differ from the stock driver in 1 scene (pipeline_barriers: 1584 of 2304 cells). The picture matches overall, so this is a local rendering fault, not a different scene.
Every feature check ends the same way on both drivers.
Speed test scenes (benchmark)
Scene
panvk_faux123_rg556_v0.13.0 ms
EXP_panvk_g57_rg556_lab16 ms
Difference
Starts
GPU clock, MHz
Picture vs stock
compute_nbody
30.51 typical 30.26
30.51 typical 30.19
0% faster
3 of 3 vs 3 of 3
? vs ? clock unknown
no large difference0.0no small differenceworst 0.064x36
hdr_2160p
532.18 typical 523.53
527.62 typical 524.25
1% faster
? vs 3 of 3
? vs ? clock unknown
not checked
oit_linked_lists
154.71 typical 153.46
153.08 typical 151.98
1% faster
3 of 3 vs 3 of 3
? vs ? clock unknown
no large difference0.0no small differenceworst 0.064x36
pipeline_barriers
34.75 typical 7.14
34.14 typical 6.84
2% faster
3 of 3 vs 3 of 3
? vs ? clock unknown
no large difference8.8differs in 1584 small areasworst 57.064x36
subpasses
55.25 typical 93.43
55.10 typical 95.42
0% faster
3 of 3 vs 3 of 3
? vs ? clock unknown
not checked
Time to draw one frame, per scene: the average (mean) frame time of the scene's best round, which is how many frames the driver delivered; lower is faster. "Typical" beside it is the median frame, which can sit well under the average when a driver's frames come in two speeds. A pair of reports made before per-round averages were recorded is compared on the median. A scene whose rounds disagree by more than 15% is left out. A scene marked "paced" was held at that mean frame time by the driver or the display queue, together with at least one other scene of the same run; its time says how the frames were spaced, not how fast the driver rendered, so it is not compared. A scene marked "too light" took under 8 ms at the standard size (1920 by 1080) on both drivers, where the screen's frame queue spaces the frames more than the chip does; its heavier run is the one compared: the row ending in _2160p is the scene drawn at 3840 by 2160, and compute_nbody_2x is that scene with twice the particles. "Faster" and "slower" describe EXP_panvk_g57_rg556_lab16 against panvk_faux123_rg556_v0.13.0. "Picture vs stock" compares one fixed frame per scene as a coarse colour grid (0 is identical, above 40 is a different picture); it finds a scene that was not drawn. Where both reports carry the finer 64x36 grid, the second figure is how many of its 2,304 cells differ by more than 4 of 255, and "worst" is the largest single cell; this is what finds a small rendering error in a picture that otherwise matches. A row marked 16x9 comes from a report made before the finer grid existed. "Starts" is how many of a scene's process starts reached a measured round. A GPU clock marked "not comparable" differed by more than 5% of the device's maximum between the two timings.
Technical differences (Vulkan)
Extensions only in EXP_panvk_g57_rg556_lab16 (0)
None
Extensions only in panvk_faux123_rg556_v0.13.0 (0)
None
Core features that differ (0)
None
Limits that differ (0)
Limit
panvk_faux123_rg556_v0.13.0
EXP_panvk_g57_rg556_lab16
Formats supported by only one driver (0 gained, 0 lost)