[Waryxxful]

Why. The page has no RX 5000 row yet, and RDNA1 is one of the cards without mesh shaders (#1001) that runs the compute fallback. These are the first measured runs on one, made from the same save each time so they can be compared later.

Two rows:

• Main de866017: Kokiri Forest and Hyrule Field over four runs, the first start's preparation times on this card (shader programs 120 s, predicted pipelines 3,603 s, noted pipelines 2,355 s; later starts 11 s), and VRAM at the driver's allowance.
• One switch a run: RX_VK_MIRROR=0, RX_VK_PARALLEL=3, RX_VK_PRECOMPILE=0.

All runs were scripted through the control bridge: teleport, 15 s to settle, 60 s standing, from a copied save restored before each run. The fps are the medians of the log's N presents lines.

Docs only; no checks read this page.

🤖 Generated with Claude Code

[Joey-Magnus]

I merged this onto current main (51da046) and it applies cleanly at the top of the Runs table. The rows follow the page's format: build string from the log, driver, settings, place, and fps from the "N presents" lines. They fill a real gap, the first RX 5000 card on the compute mesh fallback. No tests read this page.

Two findings in the rows deserve their own issues rather than staying only in a table. First, a first start of about 1.6 hours of pipeline preparation on this card (3,603 s predicted plus 2,355 s noted). Second, RX_VK_MIRROR=0 being 3-5 fps faster than the default here, and RX_VK_PRECOMPILE=0 cutting private memory from 27 GB to 20 GB. The 27 GB alone is worth a look on a 24 GB machine.

#2757, #2771 and #2778 also add rows at the top of the same table, so whichever lands second needs a trivial rebase.