Home / Adreno (TM) 725 / Compare

turnip_faux123_v1.2.5 vs WN-Turnip-1.16-b_Axxx

On Adreno (TM) 725 (motorola edge 30 ultra, OnePlus 15, POCO F5, Samsung Galaxy Z Fold4, Vivo iQOO Neo7 Pro, Xiaomi 12T Pro, Xiaomi 23013PC75G, Xiaomi 23049PCD8I). The first driver named is compared against the second, which is the baseline.

StockWN-Turnip-1.16-b_AxxxMesa 26.3.0-devel (git-a440221da3)

Customturnip_faux123_v1.2.5Mesa 26.3.0-devel (git-dd45fd0baa)

Graphics system version (Vulkan)1.4.362 to 1.4.359

Optional features (extensions)169 to 167+0 -2

Features that pass their check (validated)48 to 6921 pass only on turnip_faux123_v1.2.5 0 pass only on WN-Turnip-1.16-b_Axxx

Speed test scenes (benchmark)no shared scenes

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

WN-Turnip-1.16-b_Axxx details turnip_faux123_v1.2.5 details

Feature checks that differ (22)

Feature	WN-Turnip-1.16-b_Axxx	turnip_faux123_v1.2.5	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
perf.fb_local_barrier_large_draws core	untested	pass	gained
perf.fb_local_barrier_overdraw core	untested	pass	gained
stage.geometry_max_output core	untested	pass	gained
stage.geometry_point_size core	untested	pass	gained
stress.scratch_per_batch core	untested	pass	gained
stress.spill_helper_lanes core	untested	pass	gained
sync.first_submit_clear_then_compute core	untested	pass	gained
stress.many_command_buffers_one_submit core	untested	fail	changed

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	WN-Turnip-1.16-b_Axxx ms	turnip_faux123_v1.2.5 ms	Difference	Starts	GPU clock, MHz	Picture vs stock
compute_nbody	n/a	n/a	only one side	? vs 3 of 3	? vs ? clock unknown	not checked
hdr_2160p	n/a	n/a	only one side	? vs 3 of 3	? vs ? clock unknown	not checked
oit_linked_lists	n/a	n/a	only one side	? vs 3 of 3	? vs ? clock unknown	not checked
pipeline_barriers	n/a	n/a	only one side	? vs 3 of 3	? vs ? clock unknown	not checked
pipeline_barriers_2160p	n/a	10.75 typical 10.54	only one side	? vs 3 of 3	? vs ? clock unknown	not checked
subpasses	n/a	n/a	only one side	? vs 3 of 3	? vs ? clock unknown	not checked
subpasses_2160p	n/a	18.48 typical 18.49	only one side	? 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 turnip_faux123_v1.2.5 against WN-Turnip-1.16-b_Axxx. "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.5 (0)

None

Extensions only in WN-Turnip-1.16-b_Axxx (2)

VK_KHR_swapchain_mutable_format
VK_VALVE_buffer_device_address_allocation_alignment

Core features that differ (0)

None

Limits that differ (0)

Limit	WN-Turnip-1.16-b_Axxx	turnip_faux123_v1.2.5

Formats supported by only one driver (0 gained, 0 lost)

Only in turnip_faux123_v1.2.5:

None

Only in WN-Turnip-1.16-b_Axxx:

None