docs(tested): native mesh shaders on an RX 9070 XT (RADV): memory tour and Market fps against Compute #1087

Open
GrimVisage wants to merge 1 commit from GrimVisage/Longshot:docs/tested-mesh-native-rdna4 into main
Contributor

Type: docs · Risk: low · Tested on: Linux (Fedora 45), Ryzen 5 5600X, RX 9070 XT (RADV 26.2.7) · Needs: none

Why

On Linux AMD the game draws with mesh shaders run as compute shaders (Compute), on every card, since https://github.com/NotRexed/Hookshot/pull/2362: RADV's native task and mesh path hung Navi 2x and the RDNA 3 APUs. Nobody had recorded how the native path does on RDNA 4, where RADV offers it. This PR records eight runs from an RX 9070 XT (GFX1201) on RADV, RX_VK_MESH_SHADERS=native against the default, so the next look at the Linux AMD default has numbers from RDNA 4: memory with the repo's memory tour, and fps in the Castle Town market. It changes no default. See #583 (an RX 6600 losing its device with native mesh shaders, on Windows): the same switch, other hardware. No issue or tracking issue on this tracker covers native mesh shaders on Linux AMD (searched: RX_VK_MESH_SHADERS, "mesh shaders", [Tracking], "AMD Linux", "RADV").

What changed

Eight run files under docs/tested/, nothing else. They compare the Linux AMD default (Compute) against RX_VK_MESH_SHADERS=native in one build of main 1764fed2, on a Ryzen 5 5600X with an RX 9070 XT on Fedora 45.

  • docs: docs/tested/2026-11-15-mesh-shaders-native-memtour-grimvisage-run01.md to run04.md, one memory tour each (run01 and run04 Compute, run02 and run03 Native), in the format of docs/tested/README.md.
  • docs: docs/tested/2026-11-15-mesh-shaders-native-market-grimvisage-run01.md to run04.md, one fps run each in the Market (run01 and run04 Compute, run02 and run03 Native), each with its five parts' numbers.

The runs these files record

One build of main 1764fed2 (longshot abc-main1764 (source f6bc6f5f)), built as a player's (the builder AppImage's --cli), copied into two game folders, one a side: the program cache's stamp holds the mesh path, so one folder switched back and forth would prepare its programs again in the measured runs. Both folders were prepared and warmed before the series. The log said vk: mesh shaders: Automatic, from the default: the compute path in every Compute run and vk: mesh shaders: Native, from RX_VK_MESH_SHADERS: native in every Native run.

Memory tours: scripts/memtour.py from main bbe421f5 with its defaults (the test profile: no window, no audio; settle 20 s, then destinations 13,1,2,3,0,7,9,11 with 40 s of walking and camera swings in each, memory sampled every 2 s), one child save copied fresh each run, interleaved Compute, Native, Native, Compute.

fps runs: fullscreen 2560x1440 (HOS_FULLSCREEN=1), SDR, the game's own upscaler at Render resolution 100% (Quality preset Auto (this PC); no FSR 4 library in the test folders), frame generation off, the FPS counter off, Threaded rendering Auto (on), uncapped (HOS_FPS_MAX=240), RX_VK_AUTO_TUNE=0, the frame-time log on (RX_VK_FRAME_LOG), Disable camera centering On, one kept options file (HOS_OPTIONS_FILE). Link was steered by his position through the control bridge in the #688 routine, five parts of 30 s each: standing at the gate, laps between the gate and the fountain, the same laps turning the camera (right stick at half), standing at the fountain, turning the camera there. Before each part the clock was set to 12:00 with the Debug tab's Set time (Debug tools on for the test run only, HOS_OOT_CHEATS=1; the log's cheats: requested 12:00 checked each time). A warm-up run of each side, then four measured runs interleaved Compute, Native, Native, Compute. Every run's log shows one swapchain size, 2560x1440, from start to end.

Measurements

Verdict: nothing to measure in the game for this PR: docs only. The files pass their format check, and the game-free suite gives the same result as on main (CONTRIBUTING.md, "Measurements": docs).

Hardware: Ryzen 5 5600X, 31 GB, Fedora 45 (kernel 7.3.3)
Scene: none (game-free checks)
Method: python -I -B tests/test_tested_configurations.py, and python -I -B tests/run_all.py on main and on this PR
How to reproduce: the two commands above from the repository root

Before: main @ f7922126 After: this PR @ aa34b58e
tests/test_tested_configurations.py 25 tests OK (without these files) 25 tests OK, with the eight files
tests/run_all.py 562 passed, 13 failed, 89 skipped 562 passed, 13 failed (the same 13), 89 skipped
$ python -I -B tests/test_tested_configurations.py
Ran 25 tests in 0.073s
OK

$ python -I -B tests/run_all.py
562 passed, 13 failed, 89 skipped in 91 s (linux, 12 at once)
(failed on main f7922126 and on this PR alike: test_bug_report_defaults, test_crt_options, test_failed_compile_keeps_objects, test_guest_imported, test_link_skip, test_linux_update, test_make_game_cache, test_missing_nup, test_mods_size_table, test_pending_guest_import, test_run_all_changed, test_vk_occlusion_queries, test_walk_key)
(a first run on this PR also had tests/test_display_pointer.py fail once, on its timing check `reads > 0`; it passed alone three times on this PR and on main, and the full run above is the re-run)

What the runs show

Baseline: main @ 1764fed2 with mesh shaders Compute (the Linux AMD default), against the same build with RX_VK_MESH_SHADERS=native: the switch is on main already, so its effect is the switch, not a main-against-PR build.

Memory (memtour): with its programs prepared, Native holds about 1 GB less of the game's private memory than Compute, in every area from the start; shared memory is the same. The two sides don't overlap (a side's two runs differ by 20 to 115 MB).

Compute: main @ 1764fed2 (run01, run04) Native: main @ 1764fed2 (run02, run03)
peak game total, resident + swapped (MB) 10,523, 10,470 9,541, 9,428
peak private, RssAnon + its swap (MB) 3,888, 3,909 2,868, 2,822
peak shared, resident + swapped (MB) 6,682, 6,690 6,686, 6,698
lowest MemAvailable (MB) 11,374, 11,500 12,819, 13,099

fps (Market): within the spread in every part: the two sides' runs overlap in fps, 1% low and frame times. The scene is CPU-bound here (21 to 26 ms a frame against about 12 ms of GPU time), so the GPU time is the number that moves: Native is 0.4 to 0.6 ms a frame lower in four of the five parts, with the sides' runs apart (gate 11.80, 11.60 against 10.95, 11.30 ms; laps 12.90, 13.30 against 12.50, 12.60; fountain 11.70, 11.85 against 11.60, 11.20; fountain turning the camera 12.20, 12.50 against 11.90, 11.90). The replay's submit time leans the other way, by about half a millisecond at the gate (12.61, 12.14 against 12.91, 13.19 ms).

Medians of the two runs a side; fps, 1% low, median and p99 frame time from RX_VK_FRAME_LOG over each part's presents; the replay's submit time and GPU time the medians of the log's status lines in each part.

Compute: main @ 1764fed2 Native: main @ 1764fed2
gate: fps / 1% low 46.9 / 31.5 47.2 / 31.9
gate: median / p99 ms 21.13 / 28.09 20.98 / 27.81
laps: fps / 1% low 38.3 / 19.3 38.1 / 20.9
laps: median / p99 ms 25.38 / 41.98 25.50 / 41.18
laps turning the camera: fps / 1% low 41.5 / 22.1 42.1 / 18.2
laps turning the camera: median / p99 ms 23.57 / 37.19 23.07 / 37.57
fountain: fps / 1% low 39.4 / 24.6 38.9 / 25.7
fountain: median / p99 ms 25.05 / 35.09 25.60 / 35.14
fountain turning the camera: fps / 1% low 38.3 / 25.3 37.8 / 25.0
fountain turning the camera: median / p99 ms 25.78 / 35.79 26.11 / 36.87
replay submit a frame (gate, laps, fountain) 12.38, 14.14, 12.28 ms 13.05, 14.81, 12.86 ms
GPU time a frame (gate, laps, fountain) 11.70, 13.10, 11.78 ms 11.12, 12.55, 11.40 ms

The laps-turning-the-camera 1% low of the Native side (18.2) is one run's dip (run02: 12.7; run03: 23.7); its fps and frame times are in line.

Stability: no device lost, no GPU hung line, no amdgpu kernel line in any Native run (the two tours, the warm-up and the two fps runs), nor in a 20-minute Native soak before the series (the Market, then Kokiri Forest, Hyrule Field, Kakariko Village, Death Mountain Trail and back).

A caution for a first start: that soak was the Native folder's first start, and it prepared its programs inside the game: the game's private memory reached 7.9 GB (a working set of 11.5 GB), the log said vk: memory pressure on Linux 93 times, and with the PC's 8 GB of swap full (0 MB swap free in those lines) MemAvailable fell to 1.3 GB and the desktop nearly froze. The prepared runs above stay near 2.8 GB private. A PC with 16 GB on a first Native start is the case to watch.

A status line of each side, in the fountain part (run01 and run02):

[hos host] vk: 8520 presents, 39.9 fps
[hos host] vk: GPU time 11.7 ms a frame (the longest submission 4.4 ms); 7.7 textures made a frame
[hos host] vk: mesh shaders: Automatic, from the default: the compute path

[hos host] vk: 8520 presents, 39.0 fps
[hos host] vk: GPU time 11.5 ms a frame (the longest submission 4.6 ms); 6.3 textures made a frame
[hos host] vk: mesh shaders: Native, from RX_VK_MESH_SHADERS: native

Flags and settings

None: this PR adds or changes no switch, menu row, ini key or build flag (the runs use RX_VK_MESH_SHADERS, unchanged).

Testing

Tested: the eight files with tests/test_tested_configurations.py (25 tests OK) and the whole game-free suite with tests/run_all.py (the same 13 failures as on main f7922126), on Fedora 45. The runs themselves are what the files record.

Not tested: native mesh shaders on other RDNA 4 cards, on RDNA 2 and 3 under a newer RADV than the one behind https://github.com/NotRexed/Hookshot/pull/2362, and on Windows: this PC only. A first Native start on a 16 GB PC, after the caution above.

Must be tested: None (docs only; the runs make no claim about other PCs).

Risks

What could break: nothing in the game: eight Markdown files under docs/tested/.

Turning it off: revert the commit.

Compatibility: Nothing changes.

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.
  • A file in docs/tested/ for each new measured run (format in docs/tested-configurations.md).
  • Docs updated.

🤖 Generated with Claude Code

https://claude.ai/code/session_015WSf5yacFywzof5jcUYpsk

**Type:** docs · **Risk:** low · **Tested on:** Linux (Fedora 45), Ryzen 5 5600X, RX 9070 XT (RADV 26.2.7) · **Needs:** none ## Why On Linux AMD the game draws with mesh shaders run as compute shaders (Compute), on every card, since https://github.com/NotRexed/Hookshot/pull/2362: RADV's native task and mesh path hung Navi 2x and the RDNA 3 APUs. Nobody had recorded how the native path does on RDNA 4, where RADV offers it. This PR records eight runs from an RX 9070 XT (GFX1201) on RADV, `RX_VK_MESH_SHADERS=native` against the default, so the next look at the Linux AMD default has numbers from RDNA 4: memory with the repo's memory tour, and fps in the Castle Town market. It changes no default. See #583 (an RX 6600 losing its device with native mesh shaders, on Windows): the same switch, other hardware. No issue or tracking issue on this tracker covers native mesh shaders on Linux AMD (searched: `RX_VK_MESH_SHADERS`, "mesh shaders", `[Tracking]`, "AMD Linux", "RADV"). ## What changed Eight run files under `docs/tested/`, nothing else. They compare the Linux AMD default (Compute) against `RX_VK_MESH_SHADERS=native` in one build of main 1764fed2, on a Ryzen 5 5600X with an RX 9070 XT on Fedora 45. - docs: `docs/tested/2026-11-15-mesh-shaders-native-memtour-grimvisage-run01.md` to `run04.md`, one memory tour each (run01 and run04 Compute, run02 and run03 Native), in the format of `docs/tested/README.md`. - docs: `docs/tested/2026-11-15-mesh-shaders-native-market-grimvisage-run01.md` to `run04.md`, one fps run each in the Market (run01 and run04 Compute, run02 and run03 Native), each with its five parts' numbers. ### The runs these files record One build of main 1764fed2 (`longshot abc-main1764 (source f6bc6f5f)`), built as a player's (the builder AppImage's `--cli`), copied into two game folders, one a side: the program cache's stamp holds the mesh path, so one folder switched back and forth would prepare its programs again in the measured runs. Both folders were prepared and warmed before the series. The log said `vk: mesh shaders: Automatic, from the default: the compute path` in every Compute run and `vk: mesh shaders: Native, from RX_VK_MESH_SHADERS: native` in every Native run. **Memory tours:** `scripts/memtour.py` from main bbe421f5 with its defaults (the test profile: no window, no audio; settle 20 s, then destinations 13,1,2,3,0,7,9,11 with 40 s of walking and camera swings in each, memory sampled every 2 s), one child save copied fresh each run, interleaved Compute, Native, Native, Compute. **fps runs:** fullscreen 2560x1440 (`HOS_FULLSCREEN=1`), SDR, the game's own upscaler at Render resolution 100% (Quality preset Auto (this PC); no FSR 4 library in the test folders), frame generation off, the FPS counter off, Threaded rendering Auto (on), uncapped (`HOS_FPS_MAX=240`), `RX_VK_AUTO_TUNE=0`, the frame-time log on (`RX_VK_FRAME_LOG`), Disable camera centering On, one kept options file (`HOS_OPTIONS_FILE`). Link was steered by his position through the control bridge in the #688 routine, five parts of 30 s each: standing at the gate, laps between the gate and the fountain, the same laps turning the camera (right stick at half), standing at the fountain, turning the camera there. Before each part the clock was set to 12:00 with the Debug tab's Set time (Debug tools on for the test run only, `HOS_OOT_CHEATS=1`; the log's `cheats: requested 12:00` checked each time). A warm-up run of each side, then four measured runs interleaved Compute, Native, Native, Compute. Every run's log shows one swapchain size, 2560x1440, from start to end. ## Measurements **Verdict:** nothing to measure in the game for this PR: docs only. The files pass their format check, and the game-free suite gives the same result as on main (CONTRIBUTING.md, "Measurements": `docs`). Hardware: Ryzen 5 5600X, 31 GB, Fedora 45 (kernel 7.3.3) Scene: none (game-free checks) Method: `python -I -B tests/test_tested_configurations.py`, and `python -I -B tests/run_all.py` on main and on this PR How to reproduce: the two commands above from the repository root | | Before: main @ f7922126 | After: this PR @ aa34b58e | |---|---|---| | `tests/test_tested_configurations.py` | 25 tests OK (without these files) | 25 tests OK, with the eight files | | `tests/run_all.py` | 562 passed, 13 failed, 89 skipped | 562 passed, 13 failed (the same 13), 89 skipped | ``` $ python -I -B tests/test_tested_configurations.py Ran 25 tests in 0.073s OK $ python -I -B tests/run_all.py 562 passed, 13 failed, 89 skipped in 91 s (linux, 12 at once) (failed on main f7922126 and on this PR alike: test_bug_report_defaults, test_crt_options, test_failed_compile_keeps_objects, test_guest_imported, test_link_skip, test_linux_update, test_make_game_cache, test_missing_nup, test_mods_size_table, test_pending_guest_import, test_run_all_changed, test_vk_occlusion_queries, test_walk_key) (a first run on this PR also had tests/test_display_pointer.py fail once, on its timing check `reads > 0`; it passed alone three times on this PR and on main, and the full run above is the re-run) ``` ### What the runs show Baseline: main @ 1764fed2 with mesh shaders Compute (the Linux AMD default), against the same build with `RX_VK_MESH_SHADERS=native`: the switch is on main already, so its effect is the switch, not a main-against-PR build. **Memory (memtour):** with its programs prepared, Native holds about 1 GB less of the game's private memory than Compute, in every area from the start; shared memory is the same. The two sides don't overlap (a side's two runs differ by 20 to 115 MB). | | Compute: main @ 1764fed2 (run01, run04) | Native: main @ 1764fed2 (run02, run03) | |---|---|---| | peak game total, resident + swapped (MB) | 10,523, 10,470 | 9,541, 9,428 | | peak private, RssAnon + its swap (MB) | 3,888, 3,909 | 2,868, 2,822 | | peak shared, resident + swapped (MB) | 6,682, 6,690 | 6,686, 6,698 | | lowest MemAvailable (MB) | 11,374, 11,500 | 12,819, 13,099 | **fps (Market):** within the spread in every part: the two sides' runs overlap in fps, 1% low and frame times. The scene is CPU-bound here (21 to 26 ms a frame against about 12 ms of GPU time), so the GPU time is the number that moves: Native is 0.4 to 0.6 ms a frame lower in four of the five parts, with the sides' runs apart (gate 11.80, 11.60 against 10.95, 11.30 ms; laps 12.90, 13.30 against 12.50, 12.60; fountain 11.70, 11.85 against 11.60, 11.20; fountain turning the camera 12.20, 12.50 against 11.90, 11.90). The replay's submit time leans the other way, by about half a millisecond at the gate (12.61, 12.14 against 12.91, 13.19 ms). Medians of the two runs a side; fps, 1% low, median and p99 frame time from `RX_VK_FRAME_LOG` over each part's presents; the replay's submit time and GPU time the medians of the log's status lines in each part. | | Compute: main @ 1764fed2 | Native: main @ 1764fed2 | |---|---|---| | gate: fps / 1% low | 46.9 / 31.5 | 47.2 / 31.9 | | gate: median / p99 ms | 21.13 / 28.09 | 20.98 / 27.81 | | laps: fps / 1% low | 38.3 / 19.3 | 38.1 / 20.9 | | laps: median / p99 ms | 25.38 / 41.98 | 25.50 / 41.18 | | laps turning the camera: fps / 1% low | 41.5 / 22.1 | 42.1 / 18.2 | | laps turning the camera: median / p99 ms | 23.57 / 37.19 | 23.07 / 37.57 | | fountain: fps / 1% low | 39.4 / 24.6 | 38.9 / 25.7 | | fountain: median / p99 ms | 25.05 / 35.09 | 25.60 / 35.14 | | fountain turning the camera: fps / 1% low | 38.3 / 25.3 | 37.8 / 25.0 | | fountain turning the camera: median / p99 ms | 25.78 / 35.79 | 26.11 / 36.87 | | replay submit a frame (gate, laps, fountain) | 12.38, 14.14, 12.28 ms | 13.05, 14.81, 12.86 ms | | GPU time a frame (gate, laps, fountain) | 11.70, 13.10, 11.78 ms | 11.12, 12.55, 11.40 ms | The laps-turning-the-camera 1% low of the Native side (18.2) is one run's dip (run02: 12.7; run03: 23.7); its fps and frame times are in line. **Stability:** no device lost, no `GPU hung` line, no amdgpu kernel line in any Native run (the two tours, the warm-up and the two fps runs), nor in a 20-minute Native soak before the series (the Market, then Kokiri Forest, Hyrule Field, Kakariko Village, Death Mountain Trail and back). **A caution for a first start:** that soak was the Native folder's first start, and it prepared its programs inside the game: the game's private memory reached 7.9 GB (a working set of 11.5 GB), the log said `vk: memory pressure on Linux` 93 times, and with the PC's 8 GB of swap full (`0 MB swap free` in those lines) MemAvailable fell to 1.3 GB and the desktop nearly froze. The prepared runs above stay near 2.8 GB private. A PC with 16 GB on a first Native start is the case to watch. A status line of each side, in the fountain part (run01 and run02): ``` [hos host] vk: 8520 presents, 39.9 fps [hos host] vk: GPU time 11.7 ms a frame (the longest submission 4.4 ms); 7.7 textures made a frame [hos host] vk: mesh shaders: Automatic, from the default: the compute path [hos host] vk: 8520 presents, 39.0 fps [hos host] vk: GPU time 11.5 ms a frame (the longest submission 4.6 ms); 6.3 textures made a frame [hos host] vk: mesh shaders: Native, from RX_VK_MESH_SHADERS: native ``` ### Flags and settings None: this PR adds or changes no switch, menu row, ini key or build flag (the runs use `RX_VK_MESH_SHADERS`, unchanged). ## Testing **Tested:** the eight files with `tests/test_tested_configurations.py` (25 tests OK) and the whole game-free suite with `tests/run_all.py` (the same 13 failures as on main f7922126), on Fedora 45. The runs themselves are what the files record. **Not tested:** native mesh shaders on other RDNA 4 cards, on RDNA 2 and 3 under a newer RADV than the one behind https://github.com/NotRexed/Hookshot/pull/2362, and on Windows: this PC only. A first Native start on a 16 GB PC, after the caution above. **Must be tested:** None (docs only; the runs make no claim about other PCs). ## Risks **What could break:** nothing in the game: eight Markdown files under `docs/tested/`. **Turning it off:** revert the commit. **Compatibility:** Nothing changes. ## 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] A file in `docs/tested/` for each new measured run (format in `docs/tested-configurations.md`). - [x] Docs updated. 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_015WSf5yacFywzof5jcUYpsk
docs(tested): native mesh shaders on an RX 9070 XT (RADV): memory tour and Market fps against Compute
Some checks are pending
CI / SPIR-V fixtures (global narrow load/store, direct surface atomics, F2I immediate) (pull_request) Blocked by required conditions
CI / Workflow lint (actionlint) (pull_request) Blocked by required conditions
CI / Conventional Commit title (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
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) 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 3s
aa34b58e3b
Eight measured runs of main 1764fed2 on a Ryzen 5 5600X and an RX 9070 XT (RADV 26.2.7) on Fedora 45, RX_VK_MESH_SHADERS=native against the Linux AMD default (Compute), each interleaved Compute, Native, Native, Compute: four memory tours (scripts/memtour.py, the default eight areas) and four fps runs in the Market (five 30 s parts, fullscreen 2560x1440, Link steered through the control bridge).

Assisted-by: Claude Opus 5.5
Co-Authored-By: Claude Opus 5.5 <[email protected]>
Claude-Session: https://claude.ai/code/session_015WSf5yacFywzof5jcUYpsk
GrimVisage changed title from WIP: docs(tested): native mesh shaders on an RX 9070 XT (RADV): memory tour and Market fps against Compute to docs(tested): native mesh shaders on an RX 9070 XT (RADV): memory tour and Market fps against Compute 2026-11-16 07:14:51 +00:00
Some checks are pending
CI / SPIR-V fixtures (global narrow load/store, direct surface atomics, F2I immediate) (pull_request) Blocked by required conditions
CI / Workflow lint (actionlint) (pull_request) Blocked by required conditions
CI / Conventional Commit title (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
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) 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 3s
This pull request doesn't have enough approvals yet. 0 of 1 approvals granted.
Some workflows are waiting to be reviewed.
This branch is out-of-date with the base branch
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u 'docs/tested-mesh-native-rdna4:GrimVisage-docs/tested-mesh-native-rdna4'
git switch 'GrimVisage-docs/tested-mesh-native-rdna4'
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!1087
No description provided.