Unverified Quasar-v0.4.7: The results below were sent from a device this site could not confirm. A result the site counts replaces them.
Every feature check ends the same way on both drivers.
Speed test scenes (benchmark)
Scene
Quasar-v0.4.0-mesa ms
Quasar-v0.4.7 ms
Difference
Starts
GPU clock, MHz
Picture vs stock
compute_nbody
5.44 typical 5.36
n/a
only one side
3 of 3 vs ?
? vs ? clock unknown
not checked
compute_nbody_2x
n/a
n/a
only one side
3 of 3 vs ?
? vs ? clock unknown
not checked
hdr_2160p
30.48 typical 29.83
n/a
only one side
3 of 3 vs ?
? vs ? clock unknown
not checked
oit_linked_lists
8.06 typical 8.02
n/a
only one side
3 of 3 vs ?
? vs ? clock unknown
not checked
pipeline_barriers
n/a
n/a
only one side
3 of 3 vs ?
? vs ? clock unknown
not checked
pipeline_barriers_2160p
9.37 typical 9.34
n/a
only one side
3 of 3 vs ?
? vs ? clock unknown
not checked
subpasses
n/a
n/a
only one side
3 of 3 vs ?
? vs ? clock unknown
not checked
subpasses_2160p
13.77 typical 13.74
n/a
only one side
3 of 3 vs ?
? 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 Quasar-v0.4.7 against Quasar-v0.4.0-mesa. "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 Quasar-v0.4.7 (0)
None
Extensions only in Quasar-v0.4.0-mesa (1)
VK_EXT_fragment_shader_interlock
Core features that differ (0)
None
Limits that differ (0)
Limit
Quasar-v0.4.0-mesa
Quasar-v0.4.7
Formats supported by only one driver (0 gained, 0 lost)