WIP: perf(vk): parts of 240 draws, the frame's GPU idle measured, and the draw code's key and bound state made pure #1354

Draft
HumanBean wants to merge 15 commits from HumanBean/Longshot:perf/frame-pipeline into main
Owner

Type: perf · Risk: medium · Tested on: Linux, RTX 3090 · Needs: Windows; AMD; Intel (part ends have caused picture bugs there)

Why

Tracks C and D of the renderer rework plan: the frame and the draw code. This is the one pull request for both; it took in #1340. Stacked on #1309 and #1339: review the commits after them. What the measuring found: a Kokiri Forest frame is 15 ms with 11 ms of GPU work; the rest is the GPU waiting for its first work at the frame's start, because the game waits for the frame before to finish. See #916.

What changed

Read the commits in order; each stands alone.

  1. A long submission goes to the GPU in parts of 240 draws, not 120.
  2. The log says where the GPU waits (vk: frame overlap), the presenter thread takes the swapchain alone, and docs/development/frame-pipeline.md records a frame's sequence, the numbers and what was tried and removed.
  3. The log says how much of a frame is final before the game's signal (vk: frame ahead): recording ahead of the signal was measured and dropped.
  4. The draw code's pure predicates move to draw_key.h, and their checks include it instead of cutting text.
  5. The pipeline key is a pure function, and what a command buffer has bound is one struct with two reset functions. Persisted keys are unchanged.

Measurements

Verdict: Kokiri Forest about 8% faster from the part size alone (63.0 to 67.9 fps over six interleaved sessions each), the Market about 3%, Hyrule Field the same. Nothing else here changes fps.

  • The whole rework stack against main, three interleaved pairs: Kokiri Forest 65.5, 65.1, 66.2 against 63.2, 64.9, 63.2; the Market 70.3, 71.0, 69.5 against 68.8, 72.7, 68.0; Hyrule Field 90.8, 88.4, 88.5 against 90.3, 90.6, 90.7: two of three sessions about 2% lower, inside the spread but in one direction, and not yet measured further.
  • Measured and not shipped, each recorded in the doc: lifting the frame gate with the presenter thread (3 to 5%), an early frame wait (no ceiling), short first parts, recording ahead of the signal, a program-pick cache, descriptors by section.
  • Pipeline keys: a second start made 10,082 pipelines in 2.2 s from the caches, as before.

Testing

Tested:

  • python -I -B tests/run_all.py: 665 passed, 44 failed, 19 skipped. 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 (66.0 / 90.5 / 69.5 fps), no error line; earlier: the part size over eight sessions, screenshots of the draw split against the commit before within the difference between two sessions.

Not tested:

  • Windows: not compiled.
  • AMD and Intel GPUs: a part now ends at other draws than before.
  • A slower CPU, where recording 240 draws takes longer before the GPU gets its first part.
  • Upscalers and frame generation.

Must be tested:

  • Windows AMD and Windows Intel, main against this PR: Kokiri Forest (grass, leaves, fireflies), Hyrule Field, the Market, the same picture and no lower fps (Test Farm: @Beanstalk windows amd and windows intel: main against this PR, Kokiri Forest, Hyrule Field, the Market).
  • A Steam Deck: the same route.
  • Hyrule Field here, more interleaved pairs, for the 2%.

Risks

What could break: a picture bug at a part end on a driver this PC does not have; lower fps on a slow CPU; a changed pipeline key would rebuild players' pipelines (checked: it did not here).

Turning it off: RX_VK_CHUNK=120 for the part size; the rest has no behaviour to turn off.

Compatibility: none: no cache is rebuilt, MKWVK_API_VERSION stays.

Issues

See #916

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:** perf · **Risk:** medium · **Tested on:** Linux, RTX 3090 · **Needs:** Windows; AMD; Intel (part ends have caused picture bugs there) ## Why Tracks C and D of the [renderer rework plan](https://git.magicbean.dev/MagicBeanDev/Longshot/wiki/Renderer-rework-plan): the frame and the draw code. This is the one pull request for both; it took in #1340. Stacked on #1309 and #1339: review the commits after them. What the measuring found: a Kokiri Forest frame is 15 ms with 11 ms of GPU work; the rest is the GPU waiting for its first work at the frame's start, because the game waits for the frame before to finish. See #916. ## What changed Read the commits in order; each stands alone. 1. **A long submission goes to the GPU in parts of 240 draws, not 120.** 2. **The log says where the GPU waits** (`vk: frame overlap`), the presenter thread takes the swapchain alone, and `docs/development/frame-pipeline.md` records a frame's sequence, the numbers and what was tried and removed. 3. **The log says how much of a frame is final before the game's signal** (`vk: frame ahead`): recording ahead of the signal was measured and dropped. 4. **The draw code's pure predicates move to `draw_key.h`**, and their checks include it instead of cutting text. 5. **The pipeline key is a pure function, and what a command buffer has bound is one struct** with two reset functions. Persisted keys are unchanged. ## Measurements **Verdict:** Kokiri Forest about 8% faster from the part size alone (63.0 to 67.9 fps over six interleaved sessions each), the Market about 3%, Hyrule Field the same. Nothing else here changes fps. - The whole rework stack against `main`, three interleaved pairs: Kokiri Forest 65.5, 65.1, 66.2 against 63.2, 64.9, 63.2; the Market 70.3, 71.0, 69.5 against 68.8, 72.7, 68.0; **Hyrule Field 90.8, 88.4, 88.5 against 90.3, 90.6, 90.7: two of three sessions about 2% lower, inside the spread but in one direction, and not yet measured further.** - Measured and not shipped, each recorded in the doc: lifting the frame gate with the presenter thread (3 to 5%), an early frame wait (no ceiling), short first parts, recording ahead of the signal, a program-pick cache, descriptors by section. - Pipeline keys: a second start made 10,082 pipelines in 2.2 s from the caches, as before. ## Testing **Tested:** - `python -I -B tests/run_all.py`: 665 passed, 44 failed, 19 skipped. 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 (66.0 / 90.5 / 69.5 fps), no error line; earlier: the part size over eight sessions, screenshots of the draw split against the commit before within the difference between two sessions. **Not tested:** - Windows: not compiled. - AMD and Intel GPUs: a part now ends at other draws than before. - A slower CPU, where recording 240 draws takes longer before the GPU gets its first part. - Upscalers and frame generation. **Must be tested:** - Windows AMD and Windows Intel, main against this PR: Kokiri Forest (grass, leaves, fireflies), Hyrule Field, the Market, the same picture and no lower fps (Test Farm: `@Beanstalk windows amd and windows intel: main against this PR, Kokiri Forest, Hyrule Field, the Market`). - A Steam Deck: the same route. - Hyrule Field here, more interleaved pairs, for the 2%. ## Risks **What could break:** a picture bug at a part end on a driver this PC does not have; lower fps on a slow CPU; a changed pipeline key would rebuild players' pipelines (checked: it did not here). **Turning it off:** `RX_VK_CHUNK=120` for the part size; the rest has no behaviour to turn off. **Compatibility:** none: no cache is rebuilt, `MKWVK_API_VERSION` stays. ## Issues See #916 ## 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
perf(vk): a long submission goes to the GPU in parts of 240 draws, not 120
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 9s
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 13s
Website / Website on Cloudflare (pull_request_target) Has been skipped
feb6d38ec1
The renderer rework plan's track C. Each part end costs a command buffer, a queue submit and its barriers; at 240
the first part still reaches the GPU early. Kokiri Forest 63.0 -> 67.9 fps, the Market 68.6 -> 70.8, Hyrule Field the
same (RTX 3090, 2560x1440, six interleaved sessions each). RX_VK_CHUNK still sets it.

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: eight sessions at 240 a part through Kokiri Forest, Hyrule Field and the Market at 2560x1440; Kokiri 63.0 -> 67.9 fps over six interleaved sessions each, scenes drew as at 120.

Tested in game: Linux, RTX 3090, NVIDIA 620.70: eight sessions at 240 a part through Kokiri Forest, Hyrule Field and the Market at 2560x1440; Kokiri 63.0 -> 67.9 fps over six interleaved sessions each, scenes drew as at 120.
Collaborator

Possibly related, for context:

  • PR #391 perf(vk): six small costs of a draw and of a submission's parts removed — Open PR also adjusts Vulkan submission-part costs
  • issue #402 Deck: the frame is CPU-bound in the submission path, not GPU-bound (16 fps at 50% internal, GPU-bound wait 0.4 ms) — Open issue describes CPU-bound submission overhead on Steam Deck
Possibly related, for context: - PR #391 perf(vk): six small costs of a draw and of a submission's parts removed — Open PR also adjusts Vulkan submission-part costs - issue #402 Deck: the frame is CPU-bound in the submission path, not GPU-bound (16 fps at 50% internal, GPU-bound wait 0.4 ms) — Open issue describes CPU-bound submission overhead on Steam Deck
Author
Owner

A second commit is on this branch: counters, a presenter-thread fix and a new page, no change to fps.

  • Every 600 presents vk: frame overlap says how long the GPU sat idle between a frame's recordings and how long it spent in their uploads, by place in the frame. Kokiri Forest here: up to a frame's first recording with a draw 1.92 + 0.28 (the window's copy is in the idle), after it 0.68 + 0.59, of a 15.6 ms frame with 11.0 ms of GPU work.
  • present_image waits for the presenter thread before it acquires the next image, so the swapchain is used by one thread at a time (only with RX_VK_PRESENT_THREAD=1).
  • docs/development/frame-pipeline.md (new) has a frame's sequence on every thread, the measured numbers, and what was tried and taken out again: answering the game's frame wait early (its ceiling measured 0.00 ms), short first parts (the GPU's wait for its first work fell from 2.4 to 1.5 ms and the same idle appeared mid-frame; fps the same over three interleaved pairs), lifting the frame gate with the presenter thread (3 to 5%, and the gate's reason stands).

One more session of the final build, nothing set: Kokiri Forest 65.0 fps, Hyrule Field 91.2, the Market 72.3; no error line. tests/test_frame_overlap.py is new and has not run.

A second commit is on this branch: counters, a presenter-thread fix and a new page, no change to fps. - Every 600 presents `vk: frame overlap` says how long the GPU sat idle between a frame's recordings and how long it spent in their uploads, by place in the frame. Kokiri Forest here: `up to a frame's first recording with a draw 1.92 + 0.28 (the window's copy is in the idle), after it 0.68 + 0.59`, of a 15.6 ms frame with 11.0 ms of GPU work. - `present_image` waits for the presenter thread before it acquires the next image, so the swapchain is used by one thread at a time (only with `RX_VK_PRESENT_THREAD=1`). - `docs/development/frame-pipeline.md` (new) has a frame's sequence on every thread, the measured numbers, and what was tried and taken out again: answering the game's frame wait early (its ceiling measured 0.00 ms), short first parts (the GPU's wait for its first work fell from 2.4 to 1.5 ms and the same idle appeared mid-frame; fps the same over three interleaved pairs), lifting the frame gate with the presenter thread (3 to 5%, and the gate's reason stands). One more session of the final build, nothing set: Kokiri Forest 65.0 fps, Hyrule Field 91.2, the Market 72.3; no error line. `tests/test_frame_overlap.py` is new and has not run.
feat(vk): the log says where the GPU waits for the render thread, and the presenter takes the swapchain alone
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 9s
Guide screenshots / Guide images and local UI source review (pull_request) Failing after 9s
CI / Workflow lint (actionlint) (pull_request) Successful in 12s
Third-party parts / As their notes say (pull_request) Successful in 13s
d8f996495a
The renderer rework plan's track C. Every 600 presents 'vk: frame overlap' gives the GPU's idle time and upload time
between a frame's recordings, by place in the frame, and what comes after the frame's last recording that reads the
game's memory. In Kokiri Forest (RTX 3090, 1440p): 1.9 ms idle up to the frame's first draws, 0.7 ms after, of a
15 ms frame with 11 ms of GPU work. docs/development/frame-pipeline.md records the frame's sequence, these numbers
and what was tried and removed (an early frame wait: no ceiling; short first parts: the idle only moved).
present_image waits for the presenter before it acquires, so the swapchain is one thread's at a time.

Co-Authored-By: Claude Fable 5.2 <[email protected]>
Claude-Session: https://claude.ai/code/session_017vw8dzCsAL3UdW7ft8ptL9
feat(vk): the log says how much of a frame is final before the game's signal
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 9s
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 13s
0802270b5e
The renderer rework plan's track C. 'vk: frame ahead' counts, for the parts recorded in the signal's job, how many
took nothing that came with the signal. In Kokiri Forest the frame's first part never did (0 of 595 frames), and the
game writes about 57 pages just before its signal: recording ahead of the signal is measured and dropped, and
docs/development/frame-pipeline.md says so.

Co-Authored-By: Claude Fable 5.2 <[email protected]>
Claude-Session: https://claude.ai/code/session_017vw8dzCsAL3UdW7ft8ptL9
HumanBean force-pushed perf/frame-pipeline from 0802270b5e
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 9s
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 13s
to 171722ca74
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 12s
CI / Workflow lint (actionlint) (pull_request) Successful in 20s
Guide screenshots / Guide images and local UI source review (pull_request) Failing after 19s
Third-party parts / As their notes say (pull_request) Successful in 41s
PR description / Description follows the template (pull_request_target) Successful in 11s
2026-11-17 15:48:18 +00:00
Compare
HumanBean changed title from WIP: perf(vk): a long submission goes to the GPU in parts of 240 draws, not 120 to WIP: perf(vk): parts of 240 draws, the frame's GPU idle measured, and the draw code's key and bound state made pure 2026-11-17 15:49:46 +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 12s
CI / Workflow lint (actionlint) (pull_request) Successful in 20s
Guide screenshots / Guide images and local UI source review (pull_request) Failing after 19s
Third-party parts / As their notes say (pull_request) Successful in 41s
PR description / Description follows the template (pull_request_target) Successful in 11s
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_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 'perf/frame-pipeline:HumanBean-perf/frame-pipeline'
git switch 'HumanBean-perf/frame-pipeline'
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
2 participants
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!1354
No description provided.