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_nbody14% slower
hdr_2160p2% slower
oit_linked_lists1% faster
pipeline_barriers_2160p4% slower
subpasses_2160p5% slower
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 2 scenes (pipeline_barriers: 1357 of 2304 cells, pipeline_barriers_2160p: 1567 of 2304 cells). The picture matches overall, so this is a local rendering fault, not a different scene.
Not on equal terms: the GPU clock differed during 1 of these scenes (for example compute_nbody: stock at 92% of the device's maximum, custom at 81%). Part of the frame-time difference comes from the clock the device chose, not from the driver.
Every feature check ends the same way on both drivers.
Speed test scenes (benchmark)
The two drivers were not measured on the same set of device models. Frame times from different devices do not compare drivers, so read these numbers with that in mind.
Scene
Stock ms
Qualcomm Technologies Inc. Adreno Vulkan Driver ms
Difference
Starts
GPU clock, MHz
Picture vs stock
compute_nbody
7.17 typical 7.06
8.32 typical 7.98
14% slower
3 of 3 vs 3 of 3
626 vs 550 not comparable
no large difference0.0no small differenceworst 0.064x36
compute_nbody_2x
20.34 typical 20.35
n/a
only one side
3 of 3 vs ?
680 vs ? clock unknown
not checked
hdr_2160p
21.44 typical 21.40
21.98 typical 21.87
2% slower
3 of 3 vs 3 of 3
680 vs 680
no large difference0.0no small differenceworst 0.064x36
oit_linked_lists
25.48 typical 25.43
25.25 typical 25.22
1% faster
3 of 3 vs 3 of 3
680 vs 680
no large difference0.0no small differenceworst 0.064x36
pipeline_barriers
3.23 typical 2.76
5.42 typical 3.90
too light, see pipeline_barriers_2160p
3 of 3 vs 3 of 3
626 vs 413 not comparable
no large difference7.6differs in 1357 small areasworst 57.064x36
pipeline_barriers_2160p
8.08 typical 8.10
8.44 typical 8.46
4% slower
3 of 3 vs 3 of 3
680 vs 680
no large difference8.9differs in 1567 small areasworst 48.764x36
subpasses
4.13 typical 3.87
5.54 typical 4.08
too light, see subpasses_2160p
3 of 3 vs 3 of 3
680 vs 572 not comparable
not checked
subpasses_2160p
13.72 typical 13.72
14.40 typical 14.46
5% slower
3 of 3 vs 3 of 3
680 vs 680
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 Qualcomm Technologies Inc. Adreno Vulkan Driver against Qualcomm Technologies Inc. Adreno Vulkan Driver. "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 Qualcomm Technologies Inc. Adreno Vulkan Driver (0)
None
Extensions only in Qualcomm Technologies Inc. Adreno Vulkan Driver (0)
None
Core features that differ (0)
None
Limits that differ (0)
Limit
Stock
Qualcomm Technologies Inc. Adreno Vulkan Driver
Formats supported by only one driver (0 gained, 0 lost)
Only in Qualcomm Technologies Inc. Adreno Vulkan Driver:
None
Only in Qualcomm Technologies Inc. Adreno Vulkan Driver: