[nullifyshot]

The tested configurations had no RTX 5080 on Windows and none of the runs behind my numbers on #2306 (native float add on storage buffers). This adds them, so the next tester can see what is already covered.

Four rows, newest first, all on the same PC (RTX 5080 16 GB, NVIDIA 621.14, Windows 11, Ryzen 9 9900X3D, 64 GB), headless at the game's default 2048x1152 output, the 60 fps cap with normal pacing, Link standing 150 s, vk: GPU time every 120 presents:

Where	Native add	RX_VK_NATIVE_FADD=0
Kakariko Village, child	6.70 ms (6.5-7.5)	7.00 ms (6.7-8.0)
Death Mountain Trail, child	4.60 ms (4.4-5.2)	4.80 ms (4.7-5.7)
Death Mountain Trail, adult	5.40 ms (4.5-6.3)	5.60 ms (4.8-6.6)

• The child runs are a build of perf(vk): add floats to storage buffers with the GPU's own atomic, not a compare-and-swap loop #2306 rebased onto main 87991bc (v2.1.0-rc.3-249-g48e2fe4); the adult runs a build of main c544828 with feat(control): the Debug tab's Switch age over the bridge, so scripts reach the adult's maps #2694 (the bridge's age command, to switch to the adult) and perf(vk): add floats to storage buffers with the GPU's own atomic, not a compare-and-swap loop #2306's commits (v2.1.0-rc.3-252-g5692d75). The build strings are git describe of those commits; the run logs are gone.
• Posted on perf(vk): add floats to storage buffers with the GPU's own atomic, not a compare-and-swap loop #2306 at the time: perf(vk): add floats to storage buffers with the GPU's own atomic, not a compare-and-swap loop #2306 (comment) (adult) and the child numbers above it.
• Docs only. python -I -B tests/run_all.py: 419 passed; the 5 failures are main's own on this PC (fpx_sticky, spawn_emit, bake_portability, input_background, lift_cache).
• Not covered: one run each way, no night, no other GPU.

Before opening I checked the open PRs that edit this file (34) and main: none has these runs.

See #2306

🤖 Generated with Claude Code