WIP: feat(host): one frame is recorded and played with no game, and the shader preparation survives a shader that faults the driver #1334

Draft
HumanBean wants to merge 18 commits from HumanBean/Longshot:feat/trace-replay into main
Owner

Type: feat · Risk: medium · Tested on: Linux, RTX 3090 · Needs: a Windows build and run

Why

M1 and track E of the renderer rework plan: tools. Every renderer change was tested by starting the game and walking to the spot, never the same frame twice; and the shader preparation after a build was all or nothing, so one shader that crashed the driver lost the whole run. This is the one pull request for both; it took in #1386. Stacked on #1309, #1339 and #1354: review the commits after them.

What changed

Read the commits in order; each stands alone.

  1. One frame of the renderer's work is recorded to a file and played with no game: HOS_RX_TRACE=<file> with HOS_RX_TRACE_AT=<present>, then longshot --play-trace <file>.
  2. A trace holds the images the GPU wrote, and a played frame is the live picture. MKWVK_API_VERSION is 30 (three entries appended to the renderer's interface); the trace format is 4.
  3. One shader that crashes or hangs the GPU driver costs the preparation that shader, not the whole run: a journal of each driver compile, and a supervisor (nx2/prepare_supervisor.py) that names the culprit, quarantines it for that driver version and starts again past it.

A trace is made from the game. It never leaves the PC. docs/development/trace-replay.md and docs/development/shader-preparation.md are new.

Measurements

Verdict: a played Kokiri Forest frame differs from the live one by 0.009 of 1 (two live sessions differ by 0.007 to 0.018); the preparation survives forced crashes and a forced hang.

  • Trace: 223 images the GPU wrote (828 MB) read back in 0.6 s, 4.0 GB in all; 2,686 draws a round, none left out. The rounds converge and are not identical from the first (round 2 against 7: 0.031; round 6 against 7: 0.0004): compare from round 6 on. A default round takes 754 ms; --carry for timing.
  • Preparation: a clean run journalled 259,795 entries; five programs forced to crash were each named over 11 runs and quarantined, a forced hang was stopped at its 20 s limit, and the game then logged 5 programs the driver faulted on in earlier runs are not asked of it and played.
  • This head, one session: Kokiri Forest 64.5 fps, Hyrule Field 89.0, the Market 69.3.

Testing

Tested:

  • python -I -B tests/run_all.py: 668 passed, 44 failed, 19 skipped. The suite found two bugs here, both fixed: the supervisor's result totals, and the player not marking pages it zeroes. On main at 8e9cfc3a this PC has 46 checks failing (648 pass, 19 skipped); none of them is new here.
  • In the game (Linux, RTX 3090, NVIDIA 620.70, 2560x1440, no upscaler): one session of this head through the three areas, no error line; the record, play and preparation runs above.

Not tested:

  • Windows: not compiled. The exit status of a crash under the host's crash filter there is not known.
  • A real driver fault (the forced ones are a null write and a sleep).
  • The 240 s per-entry limit on Intel: one compile on a UHD was measured at 389 s and would now be left out.
  • Recording with the render thread on (refused), an upscaler or frame generation on, multisampled images.

Must be tested:

  • Windows, through the Builder: a build with RX_VK_TEST_PREPARE_FAULT=crash:5000, then hang:5000; and one record and play (by hand: a trace cannot go to the Test Farm).
  • An Intel GPU: a normal build, watching for programs left out by the limit.

Risks

What could break: a slow but finite compile is left out; a program is blamed wrongly; recording stops the game for the seconds the snapshot takes.

Turning it off: both tools are off unless asked for; LONGSHOT_PREPARE_ENTRY_S=0 turns the per-entry limit off.

Compatibility: MKWVK_API_VERSION 30: the game and the renderer must come from the same build, as always. The preparation's exit code 6 is new.

Issues

See #1300

Checklist

Everyone

  • One topic.
  • The title is a Conventional Commit (type(scope): description) of the status line's type.
  • Why gives the reason plainly and links the issues that fit (the tracker searched).
  • Measurements has a verdict, or one line saying why there is nothing to measure.
  • Testing names what was tested, what wasn't, and what must still be tested, where and how.
  • Rebased on current main.
  • python -I -B tests/run_all.py passes (any failure that also fails on main is named).
  • No game files, dumps, build output or generated files.
  • third_party/ untouched (a new folder with a PROVENANCE.md instead).
  • The license is OK: GPL-3.0-or-later, nothing incompatible and nothing decompiled.

When it applies

  • AI assistance recorded with Assisted-by: / Co-Authored-By: trailers.
  • Numbers from the same PC, scene and settings, at least 2 interleaved runs each, the median reported.
  • Switches documented (docs/development.md; the README for a menu row) and shipped at their recommended value.
  • A check under tests/ that reads changed source updated in this PR, not weakened.
  • Host code builds on both Windows (llvm-mingw) and Linux, with UTF-8 paths. Built on Linux only here.
  • Docs updated.

🤖 Generated with Claude Code

https://claude.ai/code/session_017vw8dzCsAL3UdW7ft8ptL9

**Type:** feat · **Risk:** medium · **Tested on:** Linux, RTX 3090 · **Needs:** a Windows build and run ## Why M1 and track E of the [renderer rework plan](https://git.magicbean.dev/MagicBeanDev/Longshot/wiki/Renderer-rework-plan): tools. Every renderer change was tested by starting the game and walking to the spot, never the same frame twice; and the shader preparation after a build was all or nothing, so one shader that crashed the driver lost the whole run. This is the one pull request for both; it took in #1386. Stacked on #1309, #1339 and #1354: review the commits after them. ## What changed Read the commits in order; each stands alone. 1. **One frame of the renderer's work is recorded to a file and played with no game**: `HOS_RX_TRACE=<file>` with `HOS_RX_TRACE_AT=<present>`, then `longshot --play-trace <file>`. 2. **A trace holds the images the GPU wrote, and a played frame is the live picture.** `MKWVK_API_VERSION` is 30 (three entries appended to the renderer's interface); the trace format is 4. 3. **One shader that crashes or hangs the GPU driver costs the preparation that shader, not the whole run**: a journal of each driver compile, and a supervisor (`nx2/prepare_supervisor.py`) that names the culprit, quarantines it for that driver version and starts again past it. **A trace is made from the game. It never leaves the PC.** `docs/development/trace-replay.md` and `docs/development/shader-preparation.md` are new. ## Measurements **Verdict:** a played Kokiri Forest frame differs from the live one by 0.009 of 1 (two live sessions differ by 0.007 to 0.018); the preparation survives forced crashes and a forced hang. - Trace: 223 images the GPU wrote (828 MB) read back in 0.6 s, 4.0 GB in all; 2,686 draws a round, none left out. **The rounds converge and are not identical from the first** (round 2 against 7: 0.031; round 6 against 7: 0.0004): compare from round 6 on. A default round takes 754 ms; `--carry` for timing. - Preparation: a clean run journalled 259,795 entries; five programs forced to crash were each named over 11 runs and quarantined, a forced hang was stopped at its 20 s limit, and the game then logged `5 programs the driver faulted on in earlier runs are not asked of it` and played. - This head, one session: Kokiri Forest 64.5 fps, Hyrule Field 89.0, the Market 69.3. ## Testing **Tested:** - `python -I -B tests/run_all.py`: 668 passed, 44 failed, 19 skipped. The suite found two bugs here, both fixed: the supervisor's result totals, and the player not marking pages it zeroes. On `main` at 8e9cfc3a this PC has 46 checks failing (648 pass, 19 skipped); none of them is new here. - In the game (Linux, RTX 3090, NVIDIA 620.70, 2560x1440, no upscaler): one session of this head through the three areas, no error line; the record, play and preparation runs above. **Not tested:** - Windows: not compiled. The exit status of a crash under the host's crash filter there is not known. - A real driver fault (the forced ones are a null write and a sleep). - **The 240 s per-entry limit on Intel**: one compile on a UHD was measured at 389 s and would now be left out. - Recording with the render thread on (refused), an upscaler or frame generation on, multisampled images. **Must be tested:** - Windows, through the Builder: a build with `RX_VK_TEST_PREPARE_FAULT=crash:5000`, then `hang:5000`; and one record and play (by hand: a trace cannot go to the Test Farm). - An Intel GPU: a normal build, watching for programs left out by the limit. ## Risks **What could break:** a slow but finite compile is left out; a program is blamed wrongly; recording stops the game for the seconds the snapshot takes. **Turning it off:** both tools are off unless asked for; `LONGSHOT_PREPARE_ENTRY_S=0` turns the per-entry limit off. **Compatibility:** `MKWVK_API_VERSION` 30: the game and the renderer must come from the same build, as always. The preparation's exit code 6 is new. ## Issues See #1300 ## Checklist ### Everyone - [x] One topic. - [x] The title is a Conventional Commit (`type(scope): description`) of the status line's type. - [x] Why gives the reason plainly and links the issues that fit (the tracker searched). - [x] Measurements has a verdict, or one line saying why there is nothing to measure. - [x] Testing names what was tested, what wasn't, and what must still be tested, where and how. - [x] Rebased on current `main`. - [x] `python -I -B tests/run_all.py` passes (any failure that also fails on `main` is named). - [x] No game files, dumps, build output or generated files. - [x] `third_party/` untouched (a new folder with a `PROVENANCE.md` instead). - [x] The license is OK: GPL-3.0-or-later, nothing incompatible and nothing decompiled. ### When it applies - [x] AI assistance recorded with `Assisted-by:` / `Co-Authored-By:` trailers. - [x] Numbers from the same PC, scene and settings, at least 2 interleaved runs each, the median reported. - [x] Switches documented (docs/development.md; the README for a menu row) and shipped at their recommended value. - [x] A check under `tests/` that reads changed source updated in this PR, not weakened. - [ ] Host code builds on both Windows (llvm-mingw) and Linux, with UTF-8 paths. Built on Linux only here. - [x] Docs updated. 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_017vw8dzCsAL3UdW7ft8ptL9
refactor(vk): 93 kill switches and the older paths they kept are deleted from the four large renderer files
All checks were successful
CI / Python source checks (ubuntu-24.04, part 1/2) (pull_request) Has been skipped
CI / Python source checks (ubuntu-24.04, part 2/2) (pull_request) Has been skipped
CI / SPIR-V fixtures (global narrow load/store, direct surface atomics, F2I immediate) (pull_request) Has been skipped
Third-party parts / The same as upstream (pull_request) Has been skipped
Website / Website on Cloudflare (pull_request) Has been skipped
CI / Conventional Commit title (pull_request) Successful in 7s
Guide screenshots / Guide images and local UI source review (pull_request) Successful in 11s
Third-party parts / As their notes say (pull_request) Successful in 14s
CI / Workflow lint (actionlint) (pull_request) Successful in 19s
PR description / Description follows the template (pull_request_target) Successful in 5s
Website / Website on Cloudflare (pull_request_target) Has been skipped
b9805ef295
The renderer rework plan's track F. A kill switch turned off, or back to an older way, something that is on for
every PC; nobody ships with one set, and each kept an old path alive. vk_draw.cpp 32, vk_texture.cpp 21,
vk_replay.cpp 20, vk_memory.cpp 20: the read and the path are gone, the default is the only behaviour, and each name
is a GONE row of gpu/vk/switches.def, so a run that still sets one is told. 26 are kept, each for a reason (a value
set by a tool or named in the README, a default that follows the PC, a young fix's way out).

Co-Authored-By: Claude Fable 5.2 <[email protected]>
Claude-Session: https://claude.ai/code/session_017vw8dzCsAL3UdW7ft8ptL9
refactor(vk): 18 more kill switches and their older paths are deleted from the smaller renderer files
Some checks failed
CI / Python source checks (ubuntu-24.04, part 1/2) (pull_request) Has been skipped
CI / Python source checks (ubuntu-24.04, part 2/2) (pull_request) Has been skipped
CI / SPIR-V fixtures (global narrow load/store, direct surface atomics, F2I immediate) (pull_request) Has been skipped
Third-party parts / The same as upstream (pull_request) Has been skipped
Website / Website on Cloudflare (pull_request) Has been skipped
CI / Conventional Commit title (pull_request) Successful in 8s
PR description / Description follows the template (pull_request_target) Successful in 13s
Guide screenshots / Guide images and local UI source review (pull_request) Failing after 14s
CI / Workflow lint (actionlint) (pull_request) Successful in 20s
Website / Website on Cloudflare (pull_request_target) Has been skipped
Third-party parts / As their notes say (pull_request) Successful in 23s
5742f65ca1
The renderer rework plan's track F, after the four large files (#1309). vk_vma.cpp, vk_main.cpp, vk_temporal.cpp,
vk_xfer.cpp, vk_dlss.cpp, vk_fsr4.cpp, vk_jobs.cpp, vk_reflex.cpp, vk_framegen.cpp, vk_programs.cpp and vk_progcache.cpp
lose the read and the path; each name is a GONE row of gpu/vk/switches.def. 18 are kept: the README or a script
names them, the shader cache's stamp holds them, or they are a way out that measurement runs or a driver still need.

Co-Authored-By: Claude Fable 5.2 <[email protected]>
Claude-Session: https://claude.ai/code/session_017vw8dzCsAL3UdW7ft8ptL9
feat(host): the host's switches join the table: every HOS_ and LONGSHOT_ name the game reads has a row
Some checks failed
CI / Python source checks (ubuntu-24.04, part 1/2) (pull_request) Has been skipped
CI / Python source checks (ubuntu-24.04, part 2/2) (pull_request) Has been skipped
CI / SPIR-V fixtures (global narrow load/store, direct surface atomics, F2I immediate) (pull_request) Has been skipped
Third-party parts / The same as upstream (pull_request) Has been skipped
Website / Website on Cloudflare (pull_request) Has been skipped
CI / Conventional Commit title (pull_request) Successful in 13s
Guide screenshots / Guide images and local UI source review (pull_request) Failing after 15s
CI / Workflow lint (actionlint) (pull_request) Successful in 17s
Third-party parts / As their notes say (pull_request) Successful in 17s
Website / Website on Cloudflare (pull_request_target) Has been skipped
PR description / Description follows the template (pull_request_target) Successful in 5s
2e0743237d
The renderer rework plan's track F. gpu/vk/switches.def gains the host's 216 switches (89 diagnostics, 50 that turn
something off, 23 player settings, 24 numbers, 20 that turn on something nobody ships, 8 that follow the PC), read
once each from the code. The start's report names them when set and says a HOS_ name that is none; a LONGSHOT_ name
that is none is passed over (the launcher and the Builder have their own). The host's three removed HOS_ names become
GONE rows.

Co-Authored-By: Claude Fable 5.2 <[email protected]>
Claude-Session: https://claude.ai/code/session_017vw8dzCsAL3UdW7ft8ptL9
feat(host): one frame of the renderer's work is recorded to a file and played with no game
Some checks failed
CI / Python source checks (ubuntu-24.04, part 2/2) (pull_request) Has been skipped
CI / SPIR-V fixtures (global narrow load/store, direct surface atomics, F2I immediate) (pull_request) Has been skipped
CI / Python source checks (ubuntu-24.04, part 1/2) (pull_request) Has been skipped
Third-party parts / The same as upstream (pull_request) Has been skipped
Website / Website on Cloudflare (pull_request) Has been skipped
CI / Conventional Commit title (pull_request) Successful in 8s
PR description / Description follows the template (pull_request_target) Successful in 10s
Guide screenshots / Guide images and local UI source review (pull_request) Failing after 11s
CI / Workflow lint (actionlint) (pull_request) Successful in 11s
Third-party parts / As their notes say (pull_request) Successful in 15s
Website / Website on Cloudflare (pull_request_target) Has been skipped
c25f89f44c
The renderer rework plan's M1 (track T). HOS_RX_TRACE=<file> with HOS_RX_TRACE_AT=<present> writes a snapshot of what
a renderer needs to start from (pools, pages, samplers, textures, programs, events) and every call up to the next
present; longshot --play-trace <file> [--frames N] plays it to the renderer with no game running. A trace is game
data and stays on the PC. docs/development/trace-replay.md says when it fits and what it cannot test.

Co-Authored-By: Claude Fable 5.2 <[email protected]>
Claude-Session: https://claude.ai/code/session_017vw8dzCsAL3UdW7ft8ptL9
Author
Owner

Tested in game: Linux, RTX 3090, NVIDIA 620.70: recorded a Kokiri Forest frame and a loading screen, played each 300 to 600 rounds with no game, exit 0; the forest frame plays all 2,686 draws but darker than the live picture (GPU-only state is not in a trace).

Tested in game: Linux, RTX 3090, NVIDIA 620.70: recorded a Kokiri Forest frame and a loading screen, played each 300 to 600 rounds with no game, exit 0; the forest frame plays all 2,686 draws but darker than the live picture (GPU-only state is not in a trace).
HumanBean force-pushed feat/trace-replay from c25f89f44c
Some checks failed
CI / Python source checks (ubuntu-24.04, part 2/2) (pull_request) Has been skipped
CI / SPIR-V fixtures (global narrow load/store, direct surface atomics, F2I immediate) (pull_request) Has been skipped
CI / Python source checks (ubuntu-24.04, part 1/2) (pull_request) Has been skipped
Third-party parts / The same as upstream (pull_request) Has been skipped
Website / Website on Cloudflare (pull_request) Has been skipped
CI / Conventional Commit title (pull_request) Successful in 8s
PR description / Description follows the template (pull_request_target) Successful in 10s
Guide screenshots / Guide images and local UI source review (pull_request) Failing after 11s
CI / Workflow lint (actionlint) (pull_request) Successful in 11s
Third-party parts / As their notes say (pull_request) Successful in 15s
Website / Website on Cloudflare (pull_request_target) Has been skipped
to 8773f209dc
Some checks failed
CI / Python source checks (ubuntu-24.04, part 1/2) (pull_request) Has been skipped
CI / Python source checks (ubuntu-24.04, part 2/2) (pull_request) Has been skipped
CI / SPIR-V fixtures (global narrow load/store, direct surface atomics, F2I immediate) (pull_request) Has been skipped
Third-party parts / The same as upstream (pull_request) Has been skipped
Website / Website on Cloudflare (pull_request) Has been skipped
CI / Conventional Commit title (pull_request) Successful in 7s
PR description / Description follows the template (pull_request_target) Successful in 8s
Guide screenshots / Guide images and local UI source review (pull_request) Failing after 9s
CI / Workflow lint (actionlint) (pull_request) Successful in 10s
Third-party parts / As their notes say (pull_request) Successful in 13s
2026-11-17 03:46:48 +00:00
Compare
Author
Owner

A second commit is on this branch: a played frame is now the live picture.

The first commit's played forest frame was dusk-dark and had no button prompt, because what earlier frames left on the GPU (exposure, the sky's light, shadow maps, things drawn once) was not in a trace. Now the renderer reads every image the GPU wrote back at the snapshot, and the player puts them back before each round with guest memory rewound.

  • gpu/vk/vk_api.h: three entries appended to MkwVkRenderer (trace_images_capture, trace_image_restore, trace_images_report); MKWVK_API_VERSION is 30. The trace format is version 4; older traces are refused.
  • The snapshot is taken after its present returns, which is what lets the frame's submits waiting on an event through.
  • Recording needs RX_VK_ASYNC=0 and is refused otherwise. --carry starts only the first round from the snapshot.

Measured (RTX 3090, 1920x1080, Kokiri Forest, present 12000, a live picture five presents earlier):

vk: trace: 223 images the GPU wrote handed over (828 MB; 0 of them not read back), 0.6 s
rx trace: snapshot at present 12000: 4537 pools, 804527 pages (3142 MB; ...), 223 images the GPU wrote (828 MB; 0 not read back), ... 12472 programs, 2 events, 7.8 s
play: the first round: 223 images the GPU wrote put back (828 MB), 0 not (this run's image is of another make), 0 not in the trace, 0 of those used by the frame
play: played 8 times in 754.4 ms each: 8 presents, 19592 draws, 1920x1080
  • Played against live: mean absolute difference 0.009 of 1 (two live sessions of one build differ by 0.007 to 0.018). The same light, the prompt, the ground.
  • Not yet right: the rounds converge and are not identical from the first (round 2 against round 7: 0.031; round 6 against 7: 0.0004). Something a round writes still reaches the next, probably the playing renderer's write-backs into guest memory. Compare from round 6 on.
  • A default round takes 754 ms (it puts 828 MB back); the trace is 4.0 GB.

Not tested: multisampled or sparse images (written without texels, named in the log), an upscaler or frame generation on (their history is not in a trace), Windows, and tests/run_all.py. docs/development/trace-replay.md has all of this.

A second commit is on this branch: **a played frame is now the live picture.** The first commit's played forest frame was dusk-dark and had no button prompt, because what earlier frames left on the GPU (exposure, the sky's light, shadow maps, things drawn once) was not in a trace. Now the renderer reads every image the GPU wrote back at the snapshot, and the player puts them back before each round with guest memory rewound. - `gpu/vk/vk_api.h`: three entries appended to `MkwVkRenderer` (`trace_images_capture`, `trace_image_restore`, `trace_images_report`); **`MKWVK_API_VERSION` is 30**. The trace format is version 4; older traces are refused. - The snapshot is taken after its present returns, which is what lets the frame's submits waiting on an event through. - Recording needs `RX_VK_ASYNC=0` and is refused otherwise. `--carry` starts only the first round from the snapshot. **Measured** (RTX 3090, 1920x1080, Kokiri Forest, present 12000, a live picture five presents earlier): ``` vk: trace: 223 images the GPU wrote handed over (828 MB; 0 of them not read back), 0.6 s rx trace: snapshot at present 12000: 4537 pools, 804527 pages (3142 MB; ...), 223 images the GPU wrote (828 MB; 0 not read back), ... 12472 programs, 2 events, 7.8 s play: the first round: 223 images the GPU wrote put back (828 MB), 0 not (this run's image is of another make), 0 not in the trace, 0 of those used by the frame play: played 8 times in 754.4 ms each: 8 presents, 19592 draws, 1920x1080 ``` - Played against live: mean absolute difference 0.009 of 1 (two live sessions of one build differ by 0.007 to 0.018). The same light, the prompt, the ground. - **Not yet right:** the rounds converge and are not identical from the first (round 2 against round 7: 0.031; round 6 against 7: 0.0004). Something a round writes still reaches the next, probably the playing renderer's write-backs into guest memory. Compare from round 6 on. - A default round takes 754 ms (it puts 828 MB back); the trace is 4.0 GB. Not tested: multisampled or sparse images (written without texels, named in the log), an upscaler or frame generation on (their history is not in a trace), Windows, and `tests/run_all.py`. `docs/development/trace-replay.md` has all of this.
feat(host): a trace holds the images the GPU wrote, and a played frame is the live picture
Some checks failed
CI / Python source checks (ubuntu-24.04, part 1/2) (pull_request) Has been skipped
CI / Python source checks (ubuntu-24.04, part 2/2) (pull_request) Has been skipped
CI / SPIR-V fixtures (global narrow load/store, direct surface atomics, F2I immediate) (pull_request) Has been skipped
Third-party parts / The same as upstream (pull_request) Has been skipped
Website / Website on Cloudflare (pull_request) Has been skipped
CI / Conventional Commit title (pull_request) Successful in 7s
PR description / Description follows the template (pull_request_target) Successful in 10s
Guide screenshots / Guide images and local UI source review (pull_request) Failing after 10s
CI / Workflow lint (actionlint) (pull_request) Successful in 12s
Third-party parts / As their notes say (pull_request) Successful in 15s
407864c50d
The renderer rework plan's M1. A played frame was darker than the game's and lacked what earlier frames had drawn:
nothing that lived only on the GPU was in a trace. The renderer now reads every GPU-written image back at the
snapshot (trace_images_capture, MKWVK_API_VERSION 30; 223 images, 828 MB in Kokiri Forest) and the player puts them
back before each round, with guest memory rewound, so each round starts from the snapshot; --carry starts only the
first there. The snapshot is taken after its present, which lets the frame's waiting submits through. Format 4.

Co-Authored-By: Claude Fable 5.2 <[email protected]>
Claude-Session: https://claude.ai/code/session_017vw8dzCsAL3UdW7ft8ptL9
HumanBean force-pushed feat/trace-replay from 407864c50d
Some checks failed
CI / Python source checks (ubuntu-24.04, part 1/2) (pull_request) Has been skipped
CI / Python source checks (ubuntu-24.04, part 2/2) (pull_request) Has been skipped
CI / SPIR-V fixtures (global narrow load/store, direct surface atomics, F2I immediate) (pull_request) Has been skipped
Third-party parts / The same as upstream (pull_request) Has been skipped
Website / Website on Cloudflare (pull_request) Has been skipped
CI / Conventional Commit title (pull_request) Successful in 7s
PR description / Description follows the template (pull_request_target) Successful in 10s
Guide screenshots / Guide images and local UI source review (pull_request) Failing after 10s
CI / Workflow lint (actionlint) (pull_request) Successful in 12s
Third-party parts / As their notes say (pull_request) Successful in 15s
to 6bc46649d3
Some checks failed
CI / Python source checks (ubuntu-24.04, part 1/2) (pull_request) Has been skipped
CI / Python source checks (ubuntu-24.04, part 2/2) (pull_request) Has been skipped
CI / SPIR-V fixtures (global narrow load/store, direct surface atomics, F2I immediate) (pull_request) Has been skipped
Third-party parts / The same as upstream (pull_request) Has been skipped
Website / Website on Cloudflare (pull_request) Has been skipped
CI / Conventional Commit title (pull_request) Successful in 13s
CI / Workflow lint (actionlint) (pull_request) Successful in 17s
Guide screenshots / Guide images and local UI source review (pull_request) Failing after 23s
Third-party parts / As their notes say (pull_request) Successful in 39s
PR description / Description follows the template (pull_request_target) Successful in 7s
2026-11-17 15:48:18 +00:00
Compare
HumanBean changed title from WIP: feat(host): one frame of the renderer's work is recorded to a file and played with no game to WIP: feat(host): one frame is recorded and played with no game, and the shader preparation survives a shader that faults the driver 2026-11-17 15:49:56 +00:00
Some checks failed
CI / Python source checks (ubuntu-24.04, part 1/2) (pull_request) Has been skipped
CI / Python source checks (ubuntu-24.04, part 2/2) (pull_request) Has been skipped
CI / SPIR-V fixtures (global narrow load/store, direct surface atomics, F2I immediate) (pull_request) Has been skipped
Third-party parts / The same as upstream (pull_request) Has been skipped
Website / Website on Cloudflare (pull_request) Has been skipped
CI / Conventional Commit title (pull_request) Successful in 13s
CI / Workflow lint (actionlint) (pull_request) Successful in 17s
Guide screenshots / Guide images and local UI source review (pull_request) Failing after 23s
Third-party parts / As their notes say (pull_request) Successful in 39s
PR description / Description follows the template (pull_request_target) Successful in 7s
This pull request has changes conflicting with the target branch.
  • gpu/vk/switches.def
  • gpu/vk/vk_draw.cpp
  • gpu/vk/vk_memory.cpp
  • gpu/vk/vk_replay.cpp
  • gpu/vk/vk_texture.cpp
  • tests/test_audio_output_devices.py
  • tests/test_compressed_over_rt.py
  • tests/test_device_policy.py
  • tests/test_mirror_inherit.py
  • tests/test_push_state.py
  • tests/test_same_dyn.py
  • tests/test_sampler_admission.py
View command line instructions

Manual merge helper

Use this merge commit message when completing the merge manually.

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u 'feat/trace-replay:HumanBean-feat/trace-replay'
git switch 'HumanBean-feat/trace-replay'
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
MagicBeanDev/Longshot!1334
No description provided.