[mooki000]

What this is for: keep the Linux RTX 4090 results from #2595 in the tested-configurations table. What is measured: twelve rows covering four builds and three scene/settings pairs, with both repeats' log-window FPS medians and ranges. Not measured: other cards, Windows or presentation through a real window.

What changed

• Adds v2.1.0, pre-fix main ef81aee7, main 46780503, and this morning's main 51da0464, newest build first. The newest rows also retain their contemporaneous 46780503 controls rather than treating the overnight figures as that comparison.
• Folds repeats and unchanged cells as the existing table does. Logged version strings retain the diagnostic-only instrumentation; 240 fps is explicitly a cap, not Uncapped.

How they were measured

Arch Linux, i9-13900K, RTX 4090, NVIDIA 615.78.08; 2048x1152, warmed caches. Timed camera sweeps in Kokiri Forest and Hyrule Field used alternating runs in exclusive timing holds; every retained run met the quiet criteria (other CPU below three cores on average and six at the peak).

These are medians and ranges of complete 120-present game-log windows, not the trace-derived whole-window means in the overnight comparison and morning comparison. Extraction checks retained each quoted source line and checked build, device, settings, quiet eligibility and fault counts. Existing captures show the loaded scenes; camera views are not pixel-locked.

Documentation-only: git diff --check passes. No dedicated documentation checker or test reading this table was found, so there was no matching test to run through tests/run_all.py --strict --jobs 1. No code or fixture changed and no new game run was needed.

Limits

One card, no window, a timed route—not scanout, physical-input testing, continuous flicker proof or a long-session memory test. Each row carries the date its runs ended. The fixed-release reference was one overnight session and was not rerun beside every newer build: its Kokiri Forest runs ended before midnight (2026-11-11), its Hyrule Field and DLAA runs after it (2026-11-12), and those two rows say so.

Assisted-by: GPT-6 Astra
Co-Authored-By: GPT-6 Astra noreply@openai.com

[Joey-Magnus]

These are docs only, and I checked them against the description. The four builds, three scene/settings pairs and paired controls are laid out clearly, and saying that these are log-window medians, not the trace-derived means on #2595, is useful. One inconsistency: the v2.1.0 block starts with a 2026-11-11 row (docs/tested-configurations.md:26), but its Hyrule Field and DLAA continuation rows directly below it are dated 2026-11-12 with "as above" everywhere else. The description says the fixed-release measurements keep their earlier date, so those two rows probably want 2026-11-11 too. Otherwise a reader takes them as a re-run. Also, the OS cell "Arch Linux 7.2.15-1-omarchy" reads like a kernel version, so "Arch Linux (kernel 7.2.15-1-omarchy)" would be clearer. This conflicts with #2769 and #2771 on the first table row, so whichever lands later needs a one-line rebase.

[mooki000]

Thanks. Both points taken in 5bc519f2:

• The dates: they are the dates the runs ended, and the release reference straddled midnight. Its Kokiri Forest runs ended 23:29 and 23:32 on 2026-11-11; its Hyrule Field runs 02:01 and 02:04 and its DLAA runs 02:12 and 02:14 on 2026-11-12 (local time, from the runs' own records). So I kept the dates and made the two rows say it: "from the same overnight session as the Kokiri Forest row above, measured after midnight (hence the later date; not a re-run)". The description's sentence is corrected the same way.
• The OS cell now reads "Arch Linux (kernel 7.2.15-1-omarchy)".

On #2769 and #2771: understood, I will rebase the first row if either lands first.

[mooki000]

Rebased onto current main (86a9cda2) as 2dcb57d8: today's merges had added rows at the same place in the table. Nothing else changed: the twelve added rows are byte-identical to the ones reviewed, they stay together in one block (so each "as above" still points at the row it did), and every row main gained is kept in main's order.