WIP: refactor(shaders): 15 kill switches the translation read are deleted, and its per-PC rules read the device policy #1390

Draft
HumanBean wants to merge 6 commits from HumanBean/Longshot:refactor/shader-stamp-batch into main
Owner

Type: refactor · Risk: high · Tested on: Linux, RTX 3090 · Needs: AMD (Windows and RADV), Intel, a card without f16

Why

Merging this makes every player's shaders translate again once: the first start after the update prepares them anew (about 5 minutes measured on a Ryzen 9 7900X with an RTX 3090; "minutes on some PCs" per the README; longer where preparation is slow). That is why these changes were kept out of #1309 and #1341 and are made here together, so the cost is paid once. Track F of the renderer rework plan. Stacked on #1309 and #1341: review the last commit only. If another change to the translation is already planned, this should ride with it.

What changed

15 kill switches the translation read are deleted with the older paths they kept: RX_VK_FOLLOW_GRAPHICS, HANDLES_LIVE, MESH_NO_DEFAULTS, MESH_NO_ZERO, MMA_NO_LDSM_BARRIER, SHARED_NO_LDS_BARRIER, NO_EXTREGS, NATIVE_MMA_KEYS, NO_CBUF_LOAD_RULE, PTR_SPLIT_FALLBACK, NO_FOLLOW, NO_DRAW_PARAMS, SHARED_48K, PICK_BIND_GEN, REGISTER_AT_ONCE (all RX_VK_). Each is a GONE row; their names leave the stamp's list and the bake's mirror (nx2/bake_ds/bake_ds.cpp, nx2/make_game.py), and a run that still sets one keeps its cache.

7 are kept, each for a reason: RX_VK_CAPTURE (twelve uses and a whole second collection path: not mechanical), HANDLE_TABLES (its default follows the GPU), MESH_FB_LAYOUT (a second emitter layout with a measured docs row), NAN_GUARD (the way back from a guard whose NaN's source is not known), NATIVE_MMA (a third state, the only way to the exact expansion), NETWORK_KEEP (the README tells players to set it), NO_F16 (puts a capable card on the path of cards without f16).

The per-PC rules in the stamped files read the device policy (gpu/vk/device_policy.h, #1341): warp64, the fragment shuffle fallback, the gather offset, the Deku web loads, the networks left out. gpu/vk/vk_vendor.h is folded into it and deleted. For a given PC the values the stamp folds are the same as before; one word is added for the two rules that used to be stamped text.

gpu/vk/eden/ is edited (it carries Longshot's own changes and has no pinned tree hash); sirit and compat are not.

Not changed, on purpose: the order in which vk_bank.cpp bumps a slot's version and then the registration generation. A review of other work proposed swapping them; the readers (program_for, the descriptor reuse) read the generation first and rely on this order, and the swap would create the race it meant to fix. A comment now says so.

Measurements

Verdict: the same picture and frame rate on this PC.

Hardware: CachyOS (kernel 7.3.3), RTX 3090 24 GB, NVIDIA 620.70, Ryzen 9 7900X, 32 GB; 2560x1440, no upscaler.
Method: a new runtime (every shader translated and prepared again), then sessions through the job queue's timing mode; screenshots standing in each area, compared with ImageMagick's mean absolute error (0 to 1).

Kokiri Forest Hyrule Field the Market
fps, before (#1341) 63.2 90.6 68.2
fps, this PR (two sessions) 65.9, 62.4 91.2, 90.3 73.9, 69.0
picture, this PR against before 0.018 0.013 0.035
picture, two sessions of the build before 0.018 0.007 0.039
picture, two sessions of this PR 0.017 0.006 0.018

Hyrule Field's 0.013 against 0.007 was checked against four more sessions of earlier builds: they differ from the build before by 0.0065 to 0.0113 and from this one by 0.0088 to 0.0131, which overlap; side by side the two pictures are the same scene with the fairy and the fog elsewhere.

Flags and settings

15 switches removed, none added.

Testing

Tested: Linux, RTX 3090 (NVIDIA 620.70): the whole shader set translated and prepared again with 0 programs failed; three sessions through the three areas as above, no error line; RX_VK_NO_FOLLOW=1 set on purpose was answered is set, and is no longer a switch (since 2026-11-17).

Not tested:

  • tests/run_all.py: 13 existing checks were edited by reading alone.
  • nx2/bake_ds was edited and not compiled (the dev build does not build it).
  • Windows: not compiled.
  • Every GPU whose rules moved: AMD's Windows driver (the fragment shuffle fallback, warp64 on 64-lane cards), RADV, Intel, a card without f16. On an NVIDIA card with 32 lanes none of those paths runs.
  • The game beyond three areas: cutscenes, menus, the upscalers, long play.

Must be tested:

  • Windows AMD, Windows Intel and a Steam Deck, main against this PR: the first start's preparation, then Kokiri Forest (grass, fireflies), Hyrule Field, the Market, expecting main's picture (Test Farm: @Beanstalk windows amd, windows intel and steamdeck: main against this PR, Kokiri Forest, Hyrule Field, the Market)
  • A build with the bake (nx2/bake_ds) to see it compiles.

Risks

What could break: a removal that kept the wrong side changes generated shader code for everyone on that path; the paths this PC does not take are the ones at risk. A value the stamp no longer folds would leave a PC with shaders translated for another rule.

Turning it off: revert the commit (shaders translate once more).

Compatibility: the translator's stamp changes: the program cache, the prepare record and the pipeline cache files are made again once. MKWVK_API_VERSION stays.

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). Not run on this PC; left to the forge's checks.
  • 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:** refactor · **Risk:** high · **Tested on:** Linux, RTX 3090 · **Needs:** AMD (Windows and RADV), Intel, a card without f16 ## Why **Merging this makes every player's shaders translate again once**: the first start after the update prepares them anew (about 5 minutes measured on a Ryzen 9 7900X with an RTX 3090; "minutes on some PCs" per the README; longer where preparation is slow). That is why these changes were kept out of #1309 and #1341 and are made here together, so the cost is paid once. Track F of the [renderer rework plan](https://git.magicbean.dev/MagicBeanDev/Longshot/wiki/Renderer-rework-plan). Stacked on #1309 and #1341: review the last commit only. If another change to the translation is already planned, this should ride with it. ## What changed **15 kill switches the translation read are deleted** with the older paths they kept: `RX_VK_FOLLOW_GRAPHICS`, `HANDLES_LIVE`, `MESH_NO_DEFAULTS`, `MESH_NO_ZERO`, `MMA_NO_LDSM_BARRIER`, `SHARED_NO_LDS_BARRIER`, `NO_EXTREGS`, `NATIVE_MMA_KEYS`, `NO_CBUF_LOAD_RULE`, `PTR_SPLIT_FALLBACK`, `NO_FOLLOW`, `NO_DRAW_PARAMS`, `SHARED_48K`, `PICK_BIND_GEN`, `REGISTER_AT_ONCE` (all `RX_VK_`). Each is a `GONE` row; their names leave the stamp's list and the bake's mirror (`nx2/bake_ds/bake_ds.cpp`, `nx2/make_game.py`), and a run that still sets one keeps its cache. **7 are kept**, each for a reason: `RX_VK_CAPTURE` (twelve uses and a whole second collection path: not mechanical), `HANDLE_TABLES` (its default follows the GPU), `MESH_FB_LAYOUT` (a second emitter layout with a measured docs row), `NAN_GUARD` (the way back from a guard whose NaN's source is not known), `NATIVE_MMA` (a third state, the only way to the exact expansion), `NETWORK_KEEP` (the README tells players to set it), `NO_F16` (puts a capable card on the path of cards without f16). **The per-PC rules in the stamped files read the device policy** (`gpu/vk/device_policy.h`, #1341): warp64, the fragment shuffle fallback, the gather offset, the Deku web loads, the networks left out. `gpu/vk/vk_vendor.h` is folded into it and deleted. For a given PC the values the stamp folds are the same as before; one word is added for the two rules that used to be stamped text. `gpu/vk/eden/` is edited (it carries Longshot's own changes and has no pinned tree hash); `sirit` and `compat` are not. Not changed, on purpose: the order in which `vk_bank.cpp` bumps a slot's version and then the registration generation. A review of other work proposed swapping them; the readers (`program_for`, the descriptor reuse) read the generation first and rely on this order, and the swap would create the race it meant to fix. A comment now says so. ## Measurements **Verdict:** the same picture and frame rate on this PC. Hardware: CachyOS (kernel 7.3.3), RTX 3090 24 GB, NVIDIA 620.70, Ryzen 9 7900X, 32 GB; 2560x1440, no upscaler. Method: a new runtime (every shader translated and prepared again), then sessions through the job queue's timing mode; screenshots standing in each area, compared with ImageMagick's mean absolute error (0 to 1). | | Kokiri Forest | Hyrule Field | the Market | |---|---|---|---| | fps, before (#1341) | 63.2 | 90.6 | 68.2 | | fps, this PR (two sessions) | 65.9, 62.4 | 91.2, 90.3 | 73.9, 69.0 | | picture, this PR against before | 0.018 | 0.013 | 0.035 | | picture, two sessions of the build before | 0.018 | 0.007 | 0.039 | | picture, two sessions of this PR | 0.017 | 0.006 | 0.018 | Hyrule Field's 0.013 against 0.007 was checked against four more sessions of earlier builds: they differ from the build before by 0.0065 to 0.0113 and from this one by 0.0088 to 0.0131, which overlap; side by side the two pictures are the same scene with the fairy and the fog elsewhere. ### Flags and settings 15 switches removed, none added. ## Testing **Tested:** Linux, RTX 3090 (NVIDIA 620.70): the whole shader set translated and prepared again with 0 programs failed; three sessions through the three areas as above, no error line; `RX_VK_NO_FOLLOW=1` set on purpose was answered `is set, and is no longer a switch (since 2026-11-17)`. **Not tested:** - `tests/run_all.py`: 13 existing checks were edited by reading alone. - **`nx2/bake_ds` was edited and not compiled** (the dev build does not build it). - Windows: not compiled. - Every GPU whose rules moved: AMD's Windows driver (the fragment shuffle fallback, warp64 on 64-lane cards), RADV, Intel, a card without f16. On an NVIDIA card with 32 lanes none of those paths runs. - The game beyond three areas: cutscenes, menus, the upscalers, long play. **Must be tested:** - Windows AMD, Windows Intel and a Steam Deck, main against this PR: the first start's preparation, then Kokiri Forest (grass, fireflies), Hyrule Field, the Market, expecting main's picture (Test Farm: `@Beanstalk windows amd, windows intel and steamdeck: main against this PR, Kokiri Forest, Hyrule Field, the Market`) - A build with the bake (`nx2/bake_ds`) to see it compiles. ## Risks **What could break:** a removal that kept the wrong side changes generated shader code for everyone on that path; the paths this PC does not take are the ones at risk. A value the stamp no longer folds would leave a PC with shaders translated for another rule. **Turning it off:** revert the commit (shaders translate once more). **Compatibility:** the translator's stamp changes: the program cache, the prepare record and the pipeline cache files are made again once. `MKWVK_API_VERSION` stays. ## 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`. - [ ] `python -I -B tests/run_all.py` passes (any failure that also fails on `main` is named). Not run on this PC; left to the forge's checks. - [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(vk): the per-PC decisions get one place and one log block: device_policy.h
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 11s
PR description / Description follows the template (pull_request_target) Successful in 15s
CI / Workflow lint (actionlint) (pull_request) Successful in 15s
Guide screenshots / Guide images and local UI source review (pull_request) Failing after 16s
Third-party parts / As their notes say (pull_request) Successful in 15s
Website / Website on Cloudflare (pull_request_target) Has been skipped
beanstalk/approval planning the tests
9765371bb6
The renderer rework plan's track F, the per-GPU rules, step 1. DeviceFacts is filled once before the device is made
and device_policy() works out 67 decisions from it, each with its reason; "vk: policy:" says them at the start. Four
sites read their unset default from it (astc_on_cpu, batch_on, FSR 4's tune, the spare captures' cap); the others
still decide where they did, and no switch's parsing changes.

Co-Authored-By: Claude Fable 5.2 <[email protected]>
Claude-Session: https://claude.ai/code/session_017vw8dzCsAL3UdW7ft8ptL9
feat(vk): 15 per-PC switches are read in one place by one rule, and four rules test the driver they name
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
CI / Workflow lint (actionlint) (pull_request) Successful in 11s
Guide screenshots / Guide images and local UI source review (pull_request) Failing after 10s
Third-party parts / As their notes say (pull_request) Successful in 16s
beanstalk/approval not approved yet
99d7880615
The renderer rework plan's track F, the per-GPU rules, steps 2 to 4. device_policy_env reads the switches of the
converted sites by one rule (unset or empty: the PC's default; an off word: off; else on; numbers digits only, in
range, else ignored and said), and the start's block marks what a switch set and the driver version each driver fix
was seen on. Fifteen sites read dev.policy; the native add's list and the integrated GPUs' RAM table are written
once. Four rules that tested the vendor now test the driver their reason names: Compute under Automatic is RADV's
(AMDVLK keeps its mesh shaders), one program's builds at a time is AMD's Windows driver's, serial compute builds are
Intel's Windows driver's, and batch_on uses the one definition of GCN.

Co-Authored-By: Claude Fable 5.2 <[email protected]>
Claude-Session: https://claude.ai/code/session_017vw8dzCsAL3UdW7ft8ptL9
refactor(shaders): 15 kill switches the translation read are deleted, and its per-PC rules read the device policy
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 17s
Website / Website on Cloudflare (pull_request_target) Has been skipped
8d1f4c949e
The renderer rework plan's track F, the part that edits the shader translation's stamped files, in one change so
players' shaders translate again once. Fifteen switches and the older paths they kept leave vk_shader.cpp, the
recompiler and the bake's mirror (GONE rows; a run that still sets one keeps its cache); seven are kept, each for a
stated reason. vk_shader.cpp reads dev.policy for warp64, the fragment shuffle fallback, the gather offset, the Deku
web loads and the networks left out; vk_vendor.h is folded into device_policy.h. For a given PC the values the
stamp folds are as before, plus one word for the two rules that left the stamped text.

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: every shader translated and prepared again (0 failed), three sessions through Kokiri Forest, Hyrule Field and the Market at 2560x1440 with main's frame rates, and screenshots within the difference between two sessions of the build before.

Tested in game: Linux, RTX 3090, NVIDIA 620.70: every shader translated and prepared again (0 failed), three sessions through Kokiri Forest, Hyrule Field and the Market at 2560x1440 with main's frame rates, and screenshots within the difference between two sessions of the build before.
HumanBean force-pushed refactor/shader-stamp-batch from 8d1f4c949e
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 17s
Website / Website on Cloudflare (pull_request_target) Has been skipped
to 41f445ea35
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 9s
PR description / Description follows the template (pull_request_target) Successful in 17s
CI / Workflow lint (actionlint) (pull_request) Successful in 18s
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 32s
2026-11-17 15:48:20 +00:00
Compare
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 9s
PR description / Description follows the template (pull_request_target) Successful in 17s
CI / Workflow lint (actionlint) (pull_request) Successful in 18s
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 32s
This pull request has changes conflicting with the target branch.
  • docs/development/device-policy.md
  • gpu/vk/device_policy.h
  • gpu/vk/switches.def
  • gpu/vk/vk_internal.h
  • gpu/vk/vk_main.cpp
  • tests/test_device_policy.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 'refactor/shader-stamp-batch:HumanBean-refactor/shader-stamp-batch'
git switch 'HumanBean-refactor/shader-stamp-batch'
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!1390
No description provided.