Graphics system version (Vulkan)1.4.359 to 1.4.359
Optional features (extensions)174 to 174+0-0
Features that pass their check (validated)49 to 66turnip_faux123_v1.2.0: sent from a device this site could not confirm (unverified)17 pass only on turnip_faux123_v1.2.00 pass only on Turnip_v26.3.0-R5
Speed test scenes (benchmark)4 faster0 slower59% faster overall (geometric mean)
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
hdr_2160p191% faster
oit_linked_lists18% faster
pipeline_barriers_2160p50% faster
subpasses26% 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: 1482 of 2304 cells). The picture matches overall, so this is a local rendering fault, not a different scene.
Did not start every time: compute_nbody (stock 0 of 3, custom 3 of 3).
Unverified turnip_faux123_v1.2.0: The results below were sent from a device this site could not confirm. A result the site counts replaces them.
Feature
Turnip_v26.3.0-R5
turnip_faux123_v1.2.0
Change
depthClamp
VkPhysicalDeviceFeatures
untested
pass
gained
largePoints
VkPhysicalDeviceFeatures
untested
pass
gained
compat.helper_loop_terminator
core
untested
pass
gained
compat.nested_map
core
untested
pass
gained
core.blend_advertised_formats
core
untested
pass
gained
core.compute_big_stack
core
untested
pass
gained
core.compute_udiv
core
fail
pass
gained
core.copy_wide_row_length
core
fail
pass
gained
core.host_coherent_readback
core
untested
pass
gained
core.mrt_partial_kill
core
untested
pass
gained
core.ubo_update_buffer
core
untested
pass
gained
core.ubo_written_after_record
core
untested
pass
gained
core.varying_subset
core
untested
pass
gained
mem.image_padding
core
untested
pass
gained
stage.geometry_max_output
core
untested
pass
gained
stage.geometry_point_size
core
untested
pass
gained
sync.first_submit_clear_then_compute
core
untested
pass
gained
Speed test scenes (benchmark)
unverified turnip_faux123_v1.2.0: The times below were sent from a device this site could not confirm. A result the site counts replaces them.
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
Turnip_v26.3.0-R5 ms
turnip_faux123_v1.2.0 ms
Difference
Starts
GPU clock, MHz
Picture vs stock
compute_nbody
n/a
n/a
only one side
0 of 3 vs 3 of 3
? vs 500 clock unknown
not checked
compute_nbody_2x
n/a
n/a
only one side
? vs 3 of 3
? vs 669 clock unknown
not checked
hdr_2160p
44.72 typical 43.85
15.36 typical 15.24
191% faster
3 of 3 vs 3 of 3
? vs 549 clock unknown
no large difference0.0no small differenceworst 0.364x36
oit_linked_lists
29.58 typical 29.46
25.14 typical 25.14
18% faster
3 of 3 vs 3 of 3
? vs 719 clock unknown
no large difference0.0no small differenceworst 0.064x36
pipeline_barriers
2.69 typical 2.63
2.25 typical 2.23
too light, see pipeline_barriers_2160p
3 of 3 vs 3 of 3
? vs 636 clock unknown
no large difference10.6differs in 1482 small areasworst 62.364x36
pipeline_barriers_2160p
11.65 typical 11.43
7.78 typical 7.64
50% faster
3 of 3 vs 3 of 3
? vs 667 clock unknown
no large difference0.0no small differenceworst 0.064x36
subpasses
4.50 typical 4.55
3.58 typical 3.56
26% faster
3 of 3 vs 3 of 3
? vs 719 clock unknown
not checked
subpasses_2160p
19.11
n/a
only one side
3 of 3 vs 3 of 3
? vs 719 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 turnip_faux123_v1.2.0 against Turnip_v26.3.0-R5. "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 turnip_faux123_v1.2.0 (0)
None
Extensions only in Turnip_v26.3.0-R5 (0)
None
Core features that differ (0)
None
Limits that differ (0)
Limit
Turnip_v26.3.0-R5
turnip_faux123_v1.2.0
Formats supported by only one driver (0 gained, 0 lost)