Skip to content

v0.3.50 — UI comparisons you can trust

Choose a tag to compare

View all tags
@FoxsterDev FoxsterDev released this 23 Aug 15:33
· 83 commits to master since this release
v0.3.50
a9ecefc

Why this matters

The first UI acceptance release could report “passed” when the evidence was not actually produced by Unity, or when a missing UI element was diluted by a full-screen average. That is a dangerous false positive for teams using screenshots as a release gate.

What this gives you

  • Only result files written by the editor can make a comparison decision-ready; caller-supplied JSON cannot impersonate an editor receipt.
  • Image dimensions and PNG data are validated and bounded, preventing corrupted or oversized images from producing misleading results or exhausting memory.
  • UI comparisons now measure meaningful regions, so a missing button or text block is not hidden by a large average area.
  • Identical designs captured at different resolutions compare correctly.
  • A failed optional lane is visible in the final verdict instead of being silently ignored.
  • Overwrite failures, blocked nested operations, and prefab render geometry now fail with actionable evidence.

Validation

  • The audit regression suite covers every finding and also checks that genuinely matching screens still pass.
Assets 2
Loading