perf(vk): save ~1 ms on FSR 3.1 across all GPUs by writing direct output and narrowing barriers #2085

Merged
HumanBean merged 1 commit from Jer9/Longshot:perf/vk-fsr3-direct-output-barriers into main 2026-11-21 17:03:52 +00:00
Contributor

Summary

When AMD FSR 3.1 runs on the temporal upscaler chain (gpu/vk/vk_fsr3.cpp), fsr3::upscale() previously rendered into an internal g.output image and then executed a full_barrier(cmd) plus a full-resolution RGBA16F vkCmdCopyImage (12.8–18.4 MB per frame) into f.output.image. In addition, draw_engine() and actor_motion() in gpu/vk/vk_temporal.cpp emitted four full_barrier(cmd) calls around temporal upscaler execution.

This PR:

  1. Passes f.output.view directly into fsr3::upscale() (P_ACCUMULATE) per frame whenever f.output.view is valid and created with VK_IMAGE_USAGE_STORAGE_BIT, eliminating the per-frame full_barrier + vkCmdCopyImage (retaining the internal g.output + targeted-barrier copy fallback when f.output is not storage-capable).
  2. Narrows the full_barrier(cmd) calls in gpu/vk/vk_temporal.cpp (draw_engine and actor_motion) to explicit stage/access barriers (COMPUTE | TRANSFER | VERTEX | FRAGMENT and SHADER_READ | SHADER_WRITE | TRANSFER_READ on entry so actor_motion's buffer copies and depth/geometry reads are fully synchronized), and moves DLSS's post-evaluate barrier into gpu/vk/vk_dlss.cpp.

Files to read first: gpu/vk/vk_fsr3.h, gpu/vk/vk_fsr3.cpp, gpu/vk/vk_temporal.h, gpu/vk/vk_temporal.cpp, gpu/vk/vk_dlss.cpp.

Testing

Tested: Windows 11 (build 26200), AMD Ryzen AI 7 350 / AMD Radeon 860M (1002:1114, RDNA 3.5 gfx1152), Adrenalin 26.10.1 (LLPC).

  • RX_VK_PASS_TIMING=1 A/B (#2084 alone vs #2084 + this PR on FSR 3.1 75%, 1600x1000): verified recordings_glue_ms dropped from 1.14 ms to 0.71 ms (-0.43 ms) and total GPU spans dropped from 22.58 ms to 21.62 ms (-0.96 ms).
  • 3-round interleaved unprofiled A/B benchmarks on FSR 3.1 75% (1600x1000 & 1920x1200) and XeSS 2.0.2 75% (1600x1000).
  • Dynamic-resolution resize stress test (Auto, dlss=3, resolution=0): transitioned live 0 -> 4 (50% 800x500) -> 1 (100% 1600x1000) -> 0 (Auto) across KokiriForest_Child -> LostWood_Child -> HyruleField_Child with camera motion; 4/4 reallocations succeeded, 1,200 FSR 3.1 frames drawn, 0 evaluation failures, 0 VK_ERROR_DEVICE_LOST.
  • Visual parity: Inspected matched 1600x1000 (RX_VK_SHOT_FX=1, sharpness=80%) screenshots for both FSR 3.1 and XeSS 2.0.2 — identical scene, lighting, HUD, and foliage with zero sync artifacts.
  • Extended stability: 242 s 3-zone tour (KokiriForest_Child -> LostWood_Child -> HyruleField_Child, 15,276 frames, 0 evaluation failures, 0 VK_ERROR_DEVICE_LOST).
  • Unit & static checks pass (check_third_party.py, test_doc_anchors.py, test_utf8_paths.py, test_temporal_history.py, test_fsr3_release_frees.py, test_fsr3_math.py, test_fsr3_shader_options.py, test_dlss_native_transition.py).

Still to test:

  • NVIDIA Windows & Linux: run FSR 3.1, XeSS, and DLSS across zone transitions and dynamic-resolution resizes, expecting clean frames and zero synchronization validation errors (@Beanstalk please test FSR 3.1, XeSS, and DLSS on NVIDIA).
  • Intel Arc Windows & AMD Linux RADV (incl. Steam Deck): run FSR 3.1 and XeSS across zone transitions and Auto resizes, expecting clean frames and zero flicker (@Beanstalk please test FSR 3.1 and XeSS on Intel and AMD RADV).

Measurements

Verdict: Cuts FSR 3.1 recordings_glue_ms by -0.43 ms (1.14 -> 0.71 ms) and total GPU spans by -0.96 ms (22.58 -> 21.62 ms) on top of #2084; combined with #2084, lifts FSR 3.1 75% at 1600x1000 by +14.4% FPS (31.61 -> 36.17 FPS, -3.99 ms frame time, -2.1 ms unprofiled GPU time).

Setup: Windows 11 26200, AMD Radeon 860M (1002:1114), Adrenalin 26.10.1 (LLPC); KokiriForest_Child, 1600x1000 docked (handheld_profile=0, ultrawide=0, vsync=2, HOS_FPS_MAX=1000, RX_VK_PRECOMPILE=0, 0 cold frames).

3-Round Interleaved Unprofiled FPS (main vs this PR + #2084):

Workload Before: main @ 89c3d21e After: this PR @ af704a6c Delta
FSR 3.1 75% (1600x1000, with #2084) 31.61 FPS (31.64 ms, 1% low 27.11, 24.6 ms GPU) 36.17 FPS (27.65 ms, 1% low 30.15, 22.5 ms GPU) +14.4% FPS (-2.1 ms GPU)
XeSS 75% (1600x1000, with #2084) 32.73 FPS (30.55 ms, 1% low 28.30, 23.6 ms GPU) 35.54 FPS (28.14 ms, 1% low 29.57, 23.1 ms GPU) +8.6% FPS (-0.5 ms GPU)
FSR 3.1 75% (1920x1200, 1x20s, with #2084) 30.13 FPS (33.19 ms, 1% low 26.92, 26.7 ms GPU) 31.95 FPS (31.30 ms, 1% low 27.64, 26.0 ms GPU) +6.0% FPS (-0.7 ms GPU)

Isolated Pass-Timing (RX_VK_PASS_TIMING=1, FSR 3.1 75%, 1600x1000, on top of #2084):

Metric Before: #2084 (d9c10742) After: #2084 + this PR (af704a6c) Delta
recordings_glue_ms 1.14 ms 0.71 ms -0.43 ms (-37.7%)
Total GPU spans (1600x1000) 22.58 ms 21.62 ms -0.96 ms
Full barriers / frame 447.7 442.4 -5.3 / frame

(Rebased cleanly onto current forge/main 9dd41326 with zero conflicts.)

Risks

  • Cross-driver synchronization: Narrowing draw_engine and actor_motion barriers affects all GPUs using temporal upscalers (FSR 3.1, XeSS, DLSS, FSR 4). Entry barriers explicitly cover COMPUTE | TRANSFER | VERTEX | FRAGMENT and SHADER_READ | SHADER_WRITE | TRANSFER_READ for actor_motion(), and vk_dlss.cpp retains its post-evaluate barrier. Needs @Beanstalk verification on NVIDIA, Intel, and AMD RADV.
  • Storage-image fallback: If f.output ever lacks VK_IMAGE_USAGE_STORAGE_BIT or a valid view, chain_evaluate() cleanly falls back to g.output + vkCmdCopyImage.
  • Revert / player impact: A simple revert restores the previous copy and full barriers. No change to saves, longshot_options.ini, or shader/pipeline caches.

Checklist

Ready for review

  • One topic, on current main; the title is a Conventional Commit.
  • Tested on my own PC, in the game for a change the game runs, as Testing says.
  • mise run test passes (any failure that also fails on main is named). (All targeted unit tests pass; test_job_queue.py skipped on Windows due to shared-console CTRL_C_EVENT.)
  • Measured against main, or Measurements says why there is nothing to measure.
  • No game files, build output or hand-edited generated files; third_party/ untouched; nothing GPL-incompatible.

When it applies

  • Screenshots of the same spot on main and here, for a change that shows on screen.
  • AI assistance recorded with Assisted-by: / Co-Authored-By: trailers.

Ready to merge

  • Everything in Still to test has run, its results in Tested.
  • Tier 1 hardware it can affect is tested (docs/dev/standards.md, "Hardware tiers").
  • Approved in review, every comment answered.
  • CI passes on the head; on current main, measured again or a comment says why the numbers still hold.
## Summary When AMD FSR 3.1 runs on the temporal upscaler chain (`gpu/vk/vk_fsr3.cpp`), `fsr3::upscale()` previously rendered into an internal `g.output` image and then executed a `full_barrier(cmd)` plus a full-resolution `RGBA16F` `vkCmdCopyImage` (`12.8–18.4 MB` per frame) into `f.output.image`. In addition, `draw_engine()` and `actor_motion()` in `gpu/vk/vk_temporal.cpp` emitted four `full_barrier(cmd)` calls around temporal upscaler execution. This PR: 1. Passes `f.output.view` directly into `fsr3::upscale()` (`P_ACCUMULATE`) per frame whenever `f.output.view` is valid and created with `VK_IMAGE_USAGE_STORAGE_BIT`, eliminating the per-frame `full_barrier` + `vkCmdCopyImage` (retaining the internal `g.output` + targeted-barrier copy fallback when `f.output` is not storage-capable). 2. Narrows the `full_barrier(cmd)` calls in `gpu/vk/vk_temporal.cpp` (`draw_engine` and `actor_motion`) to explicit stage/access barriers (`COMPUTE | TRANSFER | VERTEX | FRAGMENT` and `SHADER_READ | SHADER_WRITE | TRANSFER_READ` on entry so `actor_motion`'s buffer copies and depth/geometry reads are fully synchronized), and moves DLSS's post-evaluate barrier into `gpu/vk/vk_dlss.cpp`. **Files to read first:** `gpu/vk/vk_fsr3.h`, `gpu/vk/vk_fsr3.cpp`, `gpu/vk/vk_temporal.h`, `gpu/vk/vk_temporal.cpp`, `gpu/vk/vk_dlss.cpp`. ## Testing **Tested:** Windows 11 (build 26200), AMD Ryzen AI 7 350 / AMD Radeon 860M (`1002:1114`, RDNA 3.5 `gfx1152`), Adrenalin `26.10.1 (LLPC)`. - `RX_VK_PASS_TIMING=1` A/B (#2084 alone vs #2084 + this PR on `FSR 3.1 75%`, `1600x1000`): verified `recordings_glue_ms` dropped from `1.14 ms` to `0.71 ms` (`-0.43 ms`) and total GPU spans dropped from `22.58 ms` to `21.62 ms` (`-0.96 ms`). - 3-round interleaved unprofiled A/B benchmarks on `FSR 3.1 75%` (`1600x1000` & `1920x1200`) and `XeSS 2.0.2 75%` (`1600x1000`). - **Dynamic-resolution resize stress test (`Auto`, `dlss=3`, `resolution=0`):** transitioned live `0 -> 4 (50% 800x500) -> 1 (100% 1600x1000) -> 0 (Auto)` across `KokiriForest_Child -> LostWood_Child -> HyruleField_Child` with camera motion; `4/4` reallocations succeeded, 1,200 FSR 3.1 frames drawn, `0` evaluation failures, `0` `VK_ERROR_DEVICE_LOST`. - **Visual parity:** Inspected matched `1600x1000` (`RX_VK_SHOT_FX=1`, `sharpness=80%`) screenshots for both FSR 3.1 and XeSS 2.0.2 — identical scene, lighting, HUD, and foliage with zero sync artifacts. - **Extended stability:** 242 s 3-zone tour (`KokiriForest_Child -> LostWood_Child -> HyruleField_Child`, 15,276 frames, `0` evaluation failures, `0` `VK_ERROR_DEVICE_LOST`). - Unit & static checks pass (`check_third_party.py`, `test_doc_anchors.py`, `test_utf8_paths.py`, `test_temporal_history.py`, `test_fsr3_release_frees.py`, `test_fsr3_math.py`, `test_fsr3_shader_options.py`, `test_dlss_native_transition.py`). **Still to test:** - NVIDIA Windows & Linux: run `FSR 3.1`, `XeSS`, and `DLSS` across zone transitions and dynamic-resolution resizes, expecting clean frames and zero synchronization validation errors (`@Beanstalk` please test FSR 3.1, XeSS, and DLSS on NVIDIA). - Intel Arc Windows & AMD Linux RADV (incl. Steam Deck): run `FSR 3.1` and `XeSS` across zone transitions and `Auto` resizes, expecting clean frames and zero flicker (`@Beanstalk` please test FSR 3.1 and XeSS on Intel and AMD RADV). ## Measurements **Verdict:** Cuts `FSR 3.1` `recordings_glue_ms` by `-0.43 ms` (`1.14 -> 0.71 ms`) and total GPU spans by **`-0.96 ms`** (`22.58 -> 21.62 ms`) on top of #2084; combined with #2084, lifts `FSR 3.1 75%` at `1600x1000` by **`+14.4%` FPS** (`31.61 -> 36.17 FPS`, `-3.99 ms` frame time, `-2.1 ms` unprofiled GPU time). Setup: Windows 11 26200, AMD Radeon 860M (`1002:1114`), Adrenalin `26.10.1 (LLPC)`; `KokiriForest_Child`, `1600x1000` docked (`handheld_profile=0`, `ultrawide=0`, `vsync=2`, `HOS_FPS_MAX=1000`, `RX_VK_PRECOMPILE=0`, `0` cold frames). **3-Round Interleaved Unprofiled FPS (`main` vs this PR + #2084):** | Workload | Before: main @ `89c3d21e` | After: this PR @ `af704a6c` | Delta | |---|---:|---:|---:| | `FSR 3.1 75%` (`1600x1000`, with #2084) | `31.61 FPS` (`31.64 ms`, `1% low 27.11`, `24.6 ms` GPU) | **`36.17 FPS`** (`27.65 ms`, `1% low 30.15`, `22.5 ms` GPU) | **`+14.4%` FPS (`-2.1 ms` GPU)** | | `XeSS 75%` (`1600x1000`, with #2084) | `32.73 FPS` (`30.55 ms`, `1% low 28.30`, `23.6 ms` GPU) | **`35.54 FPS`** (`28.14 ms`, `1% low 29.57`, `23.1 ms` GPU) | **`+8.6%` FPS (`-0.5 ms` GPU)** | | `FSR 3.1 75%` (`1920x1200`, 1x20s, with #2084) | `30.13 FPS` (`33.19 ms`, `1% low 26.92`, `26.7 ms` GPU) | **`31.95 FPS`** (`31.30 ms`, `1% low 27.64`, `26.0 ms` GPU) | **`+6.0%` FPS (`-0.7 ms` GPU)** | **Isolated Pass-Timing (`RX_VK_PASS_TIMING=1`, `FSR 3.1 75%`, `1600x1000`, on top of #2084):** | Metric | Before: #2084 (`d9c10742`) | After: #2084 + this PR (`af704a6c`) | Delta | |---|---:|---:|---:| | `recordings_glue_ms` | `1.14 ms` | **`0.71 ms`** | **`-0.43 ms` (`-37.7%`)** | | Total GPU spans (`1600x1000`) | `22.58 ms` | **`21.62 ms`** | **`-0.96 ms`** | | Full barriers / frame | `447.7` | **`442.4`** | **`-5.3 / frame`** | *(Rebased cleanly onto current `forge/main` `9dd41326` with zero conflicts.)* ## Risks - **Cross-driver synchronization:** Narrowing `draw_engine` and `actor_motion` barriers affects all GPUs using temporal upscalers (FSR 3.1, XeSS, DLSS, FSR 4). Entry barriers explicitly cover `COMPUTE | TRANSFER | VERTEX | FRAGMENT` and `SHADER_READ | SHADER_WRITE | TRANSFER_READ` for `actor_motion()`, and `vk_dlss.cpp` retains its post-evaluate barrier. Needs `@Beanstalk` verification on NVIDIA, Intel, and AMD RADV. - **Storage-image fallback:** If `f.output` ever lacks `VK_IMAGE_USAGE_STORAGE_BIT` or a valid view, `chain_evaluate()` cleanly falls back to `g.output` + `vkCmdCopyImage`. - **Revert / player impact:** A simple revert restores the previous copy and full barriers. No change to saves, `longshot_options.ini`, or shader/pipeline caches. ## Checklist ### Ready for review - [x] One topic, on current `main`; the title is a Conventional Commit. - [x] Tested on my own PC, in the game for a change the game runs, as Testing says. - [x] `mise run test` passes (any failure that also fails on `main` is named). *(All targeted unit tests pass; `test_job_queue.py` skipped on Windows due to shared-console `CTRL_C_EVENT`.)* - [x] Measured against `main`, or Measurements says why there is nothing to measure. - [x] No game files, build output or hand-edited generated files; `third_party/` untouched; nothing GPL-incompatible. ### When it applies - [x] Screenshots of the same spot on `main` and here, for a change that shows on screen. - [x] AI assistance recorded with `Assisted-by:` / `Co-Authored-By:` trailers. ### Ready to merge - [ ] Everything in Still to test has run, its results in Tested. - [ ] Tier 1 hardware it can affect is tested (`docs/dev/standards.md`, "Hardware tiers"). - [ ] Approved in review, every comment answered. - [ ] CI passes on the head; on current `main`, measured again or a comment says why the numbers still hold.
perf(vk): save ~1 ms on FSR 3.1 across all GPUs by writing direct output and narrowing barriers
Some checks are pending
CI / Workflow lint (actionlint) (pull_request) Blocked by required conditions
CI / Website build and checks (pull_request) Blocked by required conditions
CI / Python source checks (ubuntu-24.04, part 1/2) (pull_request) Blocked by required conditions
CI / Python source checks (ubuntu-24.04, part 2/2) (pull_request) Blocked by required conditions
CI / SPIR-V fixtures (global narrow load/store, direct surface atomics, F2I immediate) (pull_request) Blocked by required conditions
CI / Conventional Commit title (pull_request) Blocked by required conditions
Guide screenshots / Guide images and local UI source review (pull_request) Blocked by required conditions
Third-party parts / As their notes say (pull_request) Blocked by required conditions
Third-party parts / The same as upstream (pull_request) Blocked by required conditions
Website / Website on Cloudflare (pull_request_target) Has been skipped
PR description / Description follows the template (pull_request_target) Successful in 6s
be4c2c168b
Pass f.output.view directly into fsr3::upscale (P_ACCUMULATE) when STORAGE_BIT-capable (retaining g.output copy fallback) to remove the per-frame full_barrier + vkCmdCopyImage, narrow draw_engine and actor_motion barriers in vk_temporal.cpp, and keep DLSS's post-evaluate barrier in vk_dlss.cpp.

Assisted-by: Antigravity
Author
Contributor

Tested in game: Windows 11 26200, AMD Radeon 860M (1002:1114, RDNA 3.5 gfx1152), Adrenalin 26.10.1 LLPC: RX_VK_PASS_TIMING=1 verified -0.43 ms glue (1.14 -> 0.71 ms) and -0.96 ms total GPU spans on FSR 3.1 75% (1600x1000); 3-round interleaved A/B (+14.4% FSR 3.1 75% combined with PR 1, +6.0% at 1920x1200); Auto dynamic-resolution resize stress test (0 -> 50% -> 100% -> Auto across KokiriForest/LostWood/HyruleField, 4/4 reallocs, 1200 FSR 3.1 frames, 0 eval fails); matched RX_VK_SHOT_FX=1 sharpness=80 visual parity on FSR 3.1 and XeSS 2.0.2; 242s 3-zone stability tour (15,276 frames, 0 VK_ERROR_DEVICE_LOST).

Tested in game: Windows 11 26200, AMD Radeon 860M (1002:1114, RDNA 3.5 gfx1152), Adrenalin 26.10.1 LLPC: RX_VK_PASS_TIMING=1 verified -0.43 ms glue (1.14 -> 0.71 ms) and -0.96 ms total GPU spans on FSR 3.1 75% (1600x1000); 3-round interleaved A/B (+14.4% FSR 3.1 75% combined with PR 1, +6.0% at 1920x1200); Auto dynamic-resolution resize stress test (0 -> 50% -> 100% -> Auto across KokiriForest/LostWood/HyruleField, 4/4 reallocs, 1200 FSR 3.1 frames, 0 eval fails); matched RX_VK_SHOT_FX=1 sharpness=80 visual parity on FSR 3.1 and XeSS 2.0.2; 242s 3-zone stability tour (15,276 frames, 0 VK_ERROR_DEVICE_LOST).
HumanBean deleted branch perf/vk-fsr3-direct-output-barriers 2026-11-21 17:03:53 +00:00
First-time contributor

RADV verification, as asked in the team chat: AMD Linux RADV on FSR 3.1 — done, parity, no artifacts.

Hardware: Fedora 45 (Linux 7.3.3), GNOME Wayland · AMD Radeon RX 5700 XT (RADV NAVI10), Mesa 26.2.6 radv · Ryzen 5 3600, 15 GB — an RDNA 1 card; the catalogue's RADV desktop coverage is an RX 9070 XT-class and an RX 580, so this fills the gap between them.

Method: your PR's commit be4c2c16 cherry-picked clean onto current main (the branch head carries older-base drift, so the commit itself is what was verified); built from source with the launcher's pinned toolchain; FSR 3.1 forced (RX_VK_FSR=1), output 1280x720 windowed, cap off (HOS_FPS_MAX=1000); Hyrule Field from the repo save (kokiri-start, teleport destination 1), stick-held run + full-speed camera spin, 30 s windows through the control bridge, 2 interleaved sessions per arm against current main.

Result:

  • FSR 3.1 engaged in both arms: vk: AMD FSR 3.1 draws OoT's upscale: 1280x720 -> 2560x1440
  • GPU time, settled: main 4.8 ms/frame vs this commit 4.8–4.9 ms/frame — parity. The −0.96 ms spans win is Windows/Adrenalin glue; RADV's was already lean at this output size.
  • fps, phase-matched by the field's spawn cycle (~1050 vs ~1400 draws): main 49.0–49.7 vs branch 46.7–48.3 light, both ~40 heavy — parity on a CPU-bound box (Ryzen 5 3600), as expected for a GPU-glue change.
  • Stability: 4 sessions, no crashes, no device lost; the build was also played by hand on the owner's real settings (fullscreen 2560x1440) — no artifacts seen. A shot from the branch's arm attached (Hyrule Field, FSR 3.1 active, the upscaled present).

Not covered here: XeSS (Windows) and DLSS (NVIDIA) — named for whoever takes those. The commit itself needed no changes to build or run on RADV.

shot-P1.png

RADV verification, as asked in the team chat: AMD Linux RADV on FSR 3.1 — done, parity, no artifacts. **Hardware:** Fedora 45 (Linux 7.3.3), GNOME Wayland · AMD Radeon RX 5700 XT (RADV NAVI10), Mesa 26.2.6 radv · Ryzen 5 3600, 15 GB — an RDNA 1 card; the catalogue's RADV desktop coverage is an RX 9070 XT-class and an RX 580, so this fills the gap between them. **Method:** your PR's commit `be4c2c16` cherry-picked clean onto current `main` (the branch head carries older-base drift, so the commit itself is what was verified); built from source with the launcher's pinned toolchain; FSR 3.1 forced (`RX_VK_FSR=1`), output 1280x720 windowed, cap off (`HOS_FPS_MAX=1000`); Hyrule Field from the repo save (kokiri-start, teleport destination 1), stick-held run + full-speed camera spin, 30 s windows through the control bridge, 2 interleaved sessions per arm against current `main`. **Result:** - FSR 3.1 engaged in both arms: `vk: AMD FSR 3.1 draws OoT's upscale: 1280x720 -> 2560x1440` - GPU time, settled: main **4.8 ms/frame** vs this commit **4.8–4.9 ms/frame** — parity. The −0.96 ms spans win is Windows/Adrenalin glue; RADV's was already lean at this output size. - fps, phase-matched by the field's spawn cycle (~1050 vs ~1400 draws): main 49.0–49.7 vs branch 46.7–48.3 light, both ~40 heavy — parity on a CPU-bound box (Ryzen 5 3600), as expected for a GPU-glue change. - Stability: 4 sessions, no crashes, no device lost; the build was also played by hand on the owner's real settings (fullscreen 2560x1440) — no artifacts seen. A shot from the branch's arm attached (Hyrule Field, FSR 3.1 active, the upscaled present). Not covered here: XeSS (Windows) and DLSS (NVIDIA) — named for whoever takes those. The commit itself needed no changes to build or run on RADV. ![shot-P1.png](https://git.magicbean.dev/attachments/6d3dfef3-6833-4540-a54c-703a96d75910)
Some checks are pending
CI / Workflow lint (actionlint) (pull_request) Blocked by required conditions
CI / Website build and checks (pull_request) Blocked by required conditions
CI / Python source checks (ubuntu-24.04, part 1/2) (pull_request) Blocked by required conditions
CI / Python source checks (ubuntu-24.04, part 2/2) (pull_request) Blocked by required conditions
CI / SPIR-V fixtures (global narrow load/store, direct surface atomics, F2I immediate) (pull_request) Blocked by required conditions
CI / Conventional Commit title (pull_request) Blocked by required conditions
Guide screenshots / Guide images and local UI source review (pull_request) Blocked by required conditions
Third-party parts / As their notes say (pull_request) Blocked by required conditions
Third-party parts / The same as upstream (pull_request) Blocked by required conditions
Website / Website on Cloudflare (pull_request_target) Has been skipped
PR description / Description follows the template (pull_request_target) Successful in 6s
Some workflows are waiting to be reviewed.
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!2085
No description provided.