Skip to content

Let a capture or perf run say which tier it measured - #2321

Merged
Noisemaker111 merged 1 commit into
betafrom
agent/lane-tier-flag
Oct 24, 2026
Merged

Noisemaker111 merged 1 commit into
betafrom
agent/lane-tier-flag

Conversation

@Noisemaker111

Copy link
Copy Markdown
Owner

Added

  • shoot, drive and perf take --quality <low|medium|high|ultra> and pin that graphics tier on the game page (?quality=<tier>). Each run reads the tier back from the shell (data-jg-quality) and fails when it is missing or different, so a capture or perf record always names the tier it measured. Every capture summary prints tier <tier>; perf echoes perf: tier <tier> and records it in quality.
  • The old --quality draft|full iteration mode is now the --draft switch (low tier, half viewport, -draft file names), on shoot, drive and perf; perf:gate takes --draft too. An unknown --quality value fails naming all four tiers.

Changed

  • A capture at a non-default tier writes its tier into the file name (-low, -medium, -ultra), so an ultra shot cannot overwrite the high one it was compared against.

Root cause: --quality carried the iteration preset, not the graphics tier, so a culling lane that asked for ultra got the game's default high on both sides of its comparison and could not prove a tier claim.

shoot, drive and perf take --quality low|medium|high|ultra and pin it on the page; each run reads the tier back from the shell and fails when it disagrees. The old iteration preset is now --draft.
@Noisemaker111
Noisemaker111 merged commit c7a983b into beta Oct 24, 2026
31 checks passed
@Noisemaker111 Noisemaker111 mentioned this pull request Oct 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant