FauxVkDB
English
Home / Adreno (TM) 740 / Compare

Balemuni_Apex_v2_ULTIMATE_SD8Gen2 vs turnip_faux123_v1.1.7

On Adreno (TM) 740 (AYN Odin2, AYN Odin2 Portal, AYN Thor, Moorechip Retroid Pocket Nova, motorola edge plus 2023, OnePlus 11 5G, POCO F6 Pro, Samsung Galaxy S23, Samsung Galaxy S23, Samsung Galaxy S23, Samsung Galaxy S23 Ultra, Samsung Galaxy S23 Ultra, Samsung Galaxy S23+, Sony Xperia 1 V, Xiaomi 13 pro). The first driver named is compared against the second, which is the baseline.

Stockturnip_faux123_v1.1.7Mesa 26.3.0-devel (git-dd45fd0baa)
vs
CustomBalemuni_Apex_v2_ULTIMATE_SD8Gen2Mesa 26.3.0-devel (SD 8 Gen 2 / Adreno 740 Apex v2 Ultimate by Balemuni)
Graphics system version (Vulkan)1.4.359 to 1.4.359
Optional features (extensions)172 to 142+0 -30
Features that pass their check (validated)50 to 490 pass only on Balemuni_Apex_v2_ULTIMATE_SD8Gen2 1 pass only on turnip_faux123_v1.1.7
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

turnip_faux123_v1.1.7 details Balemuni_Apex_v2_ULTIMATE_SD8Gen2 details

Feature checks that differ (1)

Featureturnip_faux123_v1.1.7Balemuni_Apex_v2_ULTIMATE_SD8Gen2Change
core.copy_wide_row_length
core
passfaillost

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.

Sceneturnip_faux123_v1.1.7 msBalemuni_Apex_v2_ULTIMATE_SD8Gen2 msDifferenceStartsGPU clock, MHzPicture vs stock
compute_nbody5.68 typical 5.63n/aonly one side3 of 3 vs 0 of 3680 vs ? clock unknownnot checked
compute_nbody_2x17.77 typical 17.72n/aonly one side3 of 3 vs ?680 vs ? clock unknownnot checked
hdr_2160p35.11 typical 35.04n/aonly one side3 of 3 vs ?680 vs ? clock unknownnot checked
oit_linked_lists26.54 typical 26.45n/aonly one side3 of 3 vs 0 of 3680 vs ? clock unknownnot checked
pipeline_barriers2.28 typical 2.28n/aonly one side3 of 3 vs 3 of 3680 vs 680 no large difference 7.0 differs in 1489 small areas worst 41.3 64x36
pipeline_barriers_2160p7.63 typical 7.62n/aonly one side3 of 3 vs 3 of 3680 vs 680 no large difference 8.2 differs in 1419 small areas worst 53.0 64x36
subpasses3.80 typical 3.80n/aonly one side3 of 3 vs 3 of 3680 vs 680 not checked
subpasses_2160p13.70 typical 13.71n/aonly one side3 of 3 vs 3 of 3646 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 Balemuni_Apex_v2_ULTIMATE_SD8Gen2 against turnip_faux123_v1.1.7. "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 Balemuni_Apex_v2_ULTIMATE_SD8Gen2 (0)
  • None
Extensions only in turnip_faux123_v1.1.7 (30)
  • VK_KHR_acceleration_structure
  • VK_KHR_compute_shader_derivatives
  • VK_KHR_deferred_host_operations
  • VK_KHR_dynamic_rendering
  • VK_KHR_dynamic_rendering_local_read
  • VK_KHR_format_feature_flags2
  • VK_KHR_fragment_shading_rate
  • VK_KHR_global_priority
  • VK_KHR_index_type_uint8
  • VK_KHR_line_rasterization
  • VK_KHR_load_store_op_none
  • VK_KHR_maintenance4
  • VK_KHR_maintenance5
  • VK_KHR_maintenance6
  • VK_KHR_maintenance7
  • VK_KHR_map_memory2
  • VK_KHR_pipeline_library
  • VK_KHR_ray_query
  • VK_KHR_ray_tracing_maintenance1
  • VK_KHR_shader_expect_assume
  • VK_KHR_shader_float_controls2
  • VK_KHR_shader_integer_dot_product
  • VK_KHR_shader_relaxed_extended_instruction
  • VK_KHR_shader_subgroup_rotate
  • VK_KHR_shader_subgroup_uniform_control_flow
  • VK_KHR_shader_terminate_invocation
  • VK_KHR_synchronization2
  • VK_KHR_vertex_attribute_divisor
  • VK_KHR_workgroup_memory_explicit_layout
  • VK_KHR_zero_initialize_workgroup_memory
Core features that differ (0)
None
Limits that differ (0)
Limitturnip_faux123_v1.1.7Balemuni_Apex_v2_ULTIMATE_SD8Gen2
Formats supported by only one driver (0 gained, 0 lost)

Only in Balemuni_Apex_v2_ULTIMATE_SD8Gen2:

  • None

Only in turnip_faux123_v1.1.7:

  • None