Skip to content

Viewer: automatic quality steps down sooner, and on Retina ends with fewer pixels - #83

Merged
SamG-Coder merged 1 commit into
mainfrom
claude/m3-auto-quality
Nov 13, 2026
Merged

SamG-Coder merged 1 commit into
mainfrom
claude/m3-auto-quality

Conversation

@SamG-Coder

Copy link
Copy Markdown
Owner

What and why

Someone reported Solstice is really slow on an Apple M3 Pro MacBook. There is no Mac here, so this works from measurement on stand-ins. A MacBook's Retina display (devicePixelRatio 2) draws about 4x the pixels of the same window at ratio 1. Even at Low it costs more than High at 1x: on the integrated Radeon, cove Low at 3024x1800 takes 175 ms, against 111 ms for High at 1512x900. Automatic quality also took 7 s to reach Low, and stopped there.

  • Automatic quality steps down sooner. Two half-second reports in a row under 14 fps settle a step; under 28 fps it still takes three. After each step one report is skipped, not four.
  • On a display with a ratio above 1 it takes one more step: Low at one canvas pixel per CSS pixel, shown as "Automatic (low, fewer pixels)". Presets chosen by hand still draw at full density. Displays at ratio 1 get no such step and see no change.
  • The logic moves to apps/viewer/web/auto-quality.js (copied by build-web.sh) and is tested in editor/test.mjs.

Findings, ranked, plus what needs a Mac to confirm: m3-pro-perf.md in the coordinator's notes folder. In short: the Retina pixel count first, screen GI as the largest pass, then the slow step-down. The visibility buffer's atomics without a depth test may cost more on Apple's tile-based GPUs, but only a Mac capture can tell.

Verified

  • Native captures (--stream --frames 120 --day-length 2), total GPU ms. RTX 5080: cove High 2.55 at 1920x1080 vs 5.01 at 3024x1800; forest High 3.80 vs 7.73. Integrated Radeon: cove High 111 at 1512x900 vs 621 at 3024x1800; Low 53 vs 175.
  • In the browser (local build, Chrome 156), with a faked 10 fps frame clock and devicePixelRatio 2: Automatic went high → medium → low → "low, fewer pixels", and the canvas went from 1600x900 to 800x450 with 0 GPU errors. Picking High by hand restored 1600x900; Automatic went back to 800x450. At ratio 1 it stopped at Low.
  • bash scripts/check-changed.sh --all: All checks passed for: all.
  • node apps/viewer/web/editor/test.mjs: all passed (10 new checks for automatic quality).

Authorship

Written by: Claude Opus 5.5 through Claude Code

Reviewed by: Claude Sonnet 5.5 (no correctness bugs found; noted that the ratio is fixed when the page starts, as before)

  • All code, text and comments in this pull request were written by a frontier AI model, with no human-written code, and will be reviewed by a frontier AI model before merging, as the Code of Conduct requires.

🤖 Generated with Claude Code

…fewer pixels

A Retina display draws four times the pixels, and Low there costs more than
High at one pixel per CSS pixel (integrated Radeon, cove: 175 ms vs 111 ms).
Automatic quality now settles a frame rate under half its target in two
reports, skips one report rather than four after each step, and on a display
of ratio over 1 takes a last step: Low at one canvas pixel per CSS pixel.
Presets chosen by hand still draw at full density.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@SamG-Coder
SamG-Coder merged commit 765343c into main Nov 13, 2026
1 check passed
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