docs(tested): native float add on an RX 9070 XT (RADV) in Kakariko and on Death Mountain Trail #1088

Open
GrimVisage wants to merge 1 commit from GrimVisage/Longshot:docs/tested-native-fadd-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

The game's shaders add floats into storage buffers. Where the GPU's own float add is trusted it is used (VK_EXT_shader_atomic_float); elsewhere, AMD included, the add runs as a compare-exchange loop. https://github.com/NotRexed/Hookshot/pull/2306 asked for a run on AMD, in Kakariko Village and on Death Mountain Trail, before AMD's default changes. This PR records that run from an RX 9070 XT (RDNA 4) on RADV, RX_VK_NATIVE_FADD=1 against the loop, so the AMD default has numbers to go on. It changes no default. No issue or tracking issue on this tracker covers it (searched: RX_VK_NATIVE_FADD, "float add", [Tracking], "AMD Linux", "RADV"); #816 is the same switch for Intel's Panther Lake.

What changed

Four run files under docs/tested/, nothing else. They compare the compare-exchange loop (the default here) against RX_VK_NATIVE_FADD=1 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-native-float-add-kakariko-dmt-grimvisage-run01.md to run04.md, one run each, in the format of docs/tested/README.md: run01 and run04 the loop, run02 and run03 native, each with its four 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 float add's choice, 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: float atomic add on storage buffers: compare-exchange loop in every loop run and vk: float atomic add on storage buffers: native (VK_EXT_shader_atomic_float), RX_VK_NATIVE_FADD=1 in every native run.

Each run: 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, mesh shaders Automatic (Compute), 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), a fresh copy of one child save. In play, the debug teleport to Kakariko Village, then to Death Mountain Trail; in each, 15 s to settle, the clock 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), then 30 s standing with no input and 30 s turning the camera (right stick at half). A warm-up run of each side, then four measured runs interleaved loop, native, native, loop. 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 @ c6f9f281
tests/test_tested_configurations.py 25 tests OK (without these files) 25 tests OK, with the four 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.049s
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)

What the runs show

Baseline: main @ 1764fed2 with the compare-exchange loop (the default on AMD), against the same build with RX_VK_NATIVE_FADD=1: the switch is on main already, so its effect is the switch, not a main-against-PR build.

Within the spread. In Kakariko Village the runs are steady (a side's two runs within about 1 fps) and the two sides match: fps, 1% low, frame times and GPU time overlap. On Death Mountain Trail the runs vary far more than the two sides differ, on both sides alike (standing: loop 46.0 and 60.4 fps, native 57.7 and 49.8; turning the camera: loop 53.6 and 58.2, native 57.3 and 50.2), so that scene can't show a difference this small; its medians are given but are not a result. No device lost in any run.

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.

Loop: main @ 1764fed2 Native, RX_VK_NATIVE_FADD=1: main @ 1764fed2
Kakariko standing: fps / 1% low 48.2 / 27.2 48.2 / 26.3
Kakariko standing: median / p99 ms 20.05 / 32.51 19.99 / 33.17
Kakariko standing: GPU / replay submit ms 10.65 / 11.78 10.68 / 11.91
Kakariko turning the camera: fps / 1% low 58.9 / 33.0 58.3 / 33.4
Kakariko turning the camera: median / p99 ms 16.57 / 25.75 16.75 / 25.52
Kakariko turning the camera: GPU / replay submit ms 8.55 / 6.00 8.53 / 6.12
Death Mountain Trail standing: fps / 1% low (noisy) 53.2 / 29.8 53.8 / 28.7
Death Mountain Trail standing: median / p99 ms (noisy) 18.28 / 32.42 17.75 / 31.71
Death Mountain Trail turning the camera: fps / 1% low (noisy) 55.9 / 31.3 53.7 / 31.7
Death Mountain Trail turning the camera: median / p99 ms (noisy) 17.23 / 30.59 18.17 / 28.68

A status line of each side, in Kakariko standing (run01 and run02):

[hos host] vk: 5520 presents, 48.6 fps
[hos host] vk: GPU time 10.9 ms a frame (the longest submission 4.3 ms); 0.9 textures made a frame
[hos host] vk: float atomic add on storage buffers: compare-exchange loop, by default only with NVIDIA's driver and Intel's Windows driver on Meteor Lake, Arrow Lake and Battlemage (RX_VK_NATIVE_FADD=1: native where the GPU has it)

[hos host] vk: 5040 presents, 46.9 fps
[hos host] vk: GPU time 11.1 ms a frame (the longest submission 3.8 ms); 1.1 textures made a frame
[hos host] vk: float atomic add on storage buffers: native (VK_EXT_shader_atomic_float), RX_VK_NATIVE_FADD=1

Flags and settings

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

Testing

Tested: the four 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: the native float add on other AMD cards (RDNA 2 and 3, the APUs), on AMD's Windows driver, and in other scenes: this PC only.

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

Risks

What could break: nothing in the game: four 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

**Type:** docs · **Risk:** low · **Tested on:** Linux (Fedora 45), Ryzen 5 5600X, RX 9070 XT (RADV 26.2.7) · **Needs:** none ## Why The game's shaders add floats into storage buffers. Where the GPU's own float add is trusted it is used (`VK_EXT_shader_atomic_float`); elsewhere, AMD included, the add runs as a compare-exchange loop. https://github.com/NotRexed/Hookshot/pull/2306 asked for a run on AMD, in Kakariko Village and on Death Mountain Trail, before AMD's default changes. This PR records that run from an RX 9070 XT (RDNA 4) on RADV, `RX_VK_NATIVE_FADD=1` against the loop, so the AMD default has numbers to go on. It changes no default. No issue or tracking issue on this tracker covers it (searched: `RX_VK_NATIVE_FADD`, "float add", `[Tracking]`, "AMD Linux", "RADV"); #816 is the same switch for Intel's Panther Lake. ## What changed Four run files under `docs/tested/`, nothing else. They compare the compare-exchange loop (the default here) against `RX_VK_NATIVE_FADD=1` 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-native-float-add-kakariko-dmt-grimvisage-run01.md` to `run04.md`, one run each, in the format of `docs/tested/README.md`: run01 and run04 the loop, run02 and run03 native, each with its four 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 float add's choice, 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: float atomic add on storage buffers: compare-exchange loop` in every loop run and `vk: float atomic add on storage buffers: native (VK_EXT_shader_atomic_float), RX_VK_NATIVE_FADD=1` in every native run. Each run: 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, mesh shaders Automatic (Compute), 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`), a fresh copy of one child save. In play, the debug teleport to Kakariko Village, then to Death Mountain Trail; in each, 15 s to settle, the clock 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), then 30 s standing with no input and 30 s turning the camera (right stick at half). A warm-up run of each side, then four measured runs interleaved loop, native, native, loop. 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 @ c6f9f281 | |---|---|---| | `tests/test_tested_configurations.py` | 25 tests OK (without these files) | 25 tests OK, with the four 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.049s 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) ``` ### What the runs show Baseline: main @ 1764fed2 with the compare-exchange loop (the default on AMD), against the same build with `RX_VK_NATIVE_FADD=1`: the switch is on main already, so its effect is the switch, not a main-against-PR build. **Within the spread.** In Kakariko Village the runs are steady (a side's two runs within about 1 fps) and the two sides match: fps, 1% low, frame times and GPU time overlap. On Death Mountain Trail the runs vary far more than the two sides differ, on both sides alike (standing: loop 46.0 and 60.4 fps, native 57.7 and 49.8; turning the camera: loop 53.6 and 58.2, native 57.3 and 50.2), so that scene can't show a difference this small; its medians are given but are not a result. No device lost in any run. 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. | | Loop: main @ 1764fed2 | Native, RX_VK_NATIVE_FADD=1: main @ 1764fed2 | |---|---|---| | Kakariko standing: fps / 1% low | 48.2 / 27.2 | 48.2 / 26.3 | | Kakariko standing: median / p99 ms | 20.05 / 32.51 | 19.99 / 33.17 | | Kakariko standing: GPU / replay submit ms | 10.65 / 11.78 | 10.68 / 11.91 | | Kakariko turning the camera: fps / 1% low | 58.9 / 33.0 | 58.3 / 33.4 | | Kakariko turning the camera: median / p99 ms | 16.57 / 25.75 | 16.75 / 25.52 | | Kakariko turning the camera: GPU / replay submit ms | 8.55 / 6.00 | 8.53 / 6.12 | | Death Mountain Trail standing: fps / 1% low (noisy) | 53.2 / 29.8 | 53.8 / 28.7 | | Death Mountain Trail standing: median / p99 ms (noisy) | 18.28 / 32.42 | 17.75 / 31.71 | | Death Mountain Trail turning the camera: fps / 1% low (noisy) | 55.9 / 31.3 | 53.7 / 31.7 | | Death Mountain Trail turning the camera: median / p99 ms (noisy) | 17.23 / 30.59 | 18.17 / 28.68 | A status line of each side, in Kakariko standing (run01 and run02): ``` [hos host] vk: 5520 presents, 48.6 fps [hos host] vk: GPU time 10.9 ms a frame (the longest submission 4.3 ms); 0.9 textures made a frame [hos host] vk: float atomic add on storage buffers: compare-exchange loop, by default only with NVIDIA's driver and Intel's Windows driver on Meteor Lake, Arrow Lake and Battlemage (RX_VK_NATIVE_FADD=1: native where the GPU has it) [hos host] vk: 5040 presents, 46.9 fps [hos host] vk: GPU time 11.1 ms a frame (the longest submission 3.8 ms); 1.1 textures made a frame [hos host] vk: float atomic add on storage buffers: native (VK_EXT_shader_atomic_float), RX_VK_NATIVE_FADD=1 ``` ### Flags and settings None: this PR adds or changes no switch, menu row, ini key or build flag (the runs use `RX_VK_NATIVE_FADD`, unchanged). ## Testing **Tested:** the four 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:** the native float add on other AMD cards (RDNA 2 and 3, the APUs), on AMD's Windows driver, and in other scenes: this PC only. **Must be tested:** None (docs only; the runs make no claim about other PCs). ## Risks **What could break:** nothing in the game: four 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)
docs(tested): native float add on an RX 9070 XT (RADV) in Kakariko and on Death Mountain Trail
Some checks failed
PR description / Description follows the template (pull_request_target) Successful in 3s
Website / Website on Cloudflare (pull_request_target) Has been skipped
CI / Conventional Commit title (pull_request) Has been cancelled
CI / Python source checks (ubuntu-24.04, part 1/2) (pull_request) Has been cancelled
CI / Python source checks (ubuntu-24.04, part 2/2) (pull_request) Has been cancelled
CI / SPIR-V fixtures (global narrow load/store, direct surface atomics, F2I immediate) (pull_request) Has been cancelled
CI / Workflow lint (actionlint) (pull_request) Has been cancelled
Guide screenshots / Guide images and local UI source review (pull_request) Has been cancelled
Third-party parts / As their notes say (pull_request) Has been cancelled
Third-party parts / The same as upstream (pull_request) Has been cancelled
Website / Website on Cloudflare (pull_request) Has been cancelled
c6f9f281b0
Four measured runs of main 1764fed2 on a Ryzen 5 5600X and an RX 9070 XT (RADV 26.2.7) on Fedora 45, RX_VK_NATIVE_FADD=1 against the compare-exchange loop (the default on AMD), interleaved loop, native, native, loop: Kakariko Village and Death Mountain Trail, 30 s standing and 30 s turning the camera in each, fullscreen 2560x1440.

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 float add on an RX 9070 XT (RADV) in Kakariko and on Death Mountain Trail to docs(tested): native float add on an RX 9070 XT (RADV) in Kakariko and on Death Mountain Trail 2026-11-16 07:14:53 +00:00
GrimVisage force-pushed docs/tested-native-fadd-rdna4 from c6f9f281b0
Some checks failed
PR description / Description follows the template (pull_request_target) Successful in 3s
Website / Website on Cloudflare (pull_request_target) Has been skipped
CI / Conventional Commit title (pull_request) Has been cancelled
CI / Python source checks (ubuntu-24.04, part 1/2) (pull_request) Has been cancelled
CI / Python source checks (ubuntu-24.04, part 2/2) (pull_request) Has been cancelled
CI / SPIR-V fixtures (global narrow load/store, direct surface atomics, F2I immediate) (pull_request) Has been cancelled
CI / Workflow lint (actionlint) (pull_request) Has been cancelled
Guide screenshots / Guide images and local UI source review (pull_request) Has been cancelled
Third-party parts / As their notes say (pull_request) Has been cancelled
Third-party parts / The same as upstream (pull_request) Has been cancelled
Website / Website on Cloudflare (pull_request) Has been cancelled
to 40d55c99bb
Some checks are pending
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
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
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
PR description / Description follows the template (pull_request_target) Successful in 5s
2026-11-16 21:18:28 +00:00
Compare
Author
Contributor

Commit message reworded: a link that didn't belong in it is gone, and the same link is gone from the description. Same files, same base (c6f9f281 is now 40d55c99).

Commit message reworded: a link that didn't belong in it is gone, and the same link is gone from the description. Same files, same base (c6f9f281 is now 40d55c99).
Member

Basic code-only review of 40d55c99bb; informational feedback, with final approval left to another reviewer.

No obvious defect found in this documentation-only change. The four independent run records follow the tested-catalogue format and retain the hardware, driver, build identity, effective switch, scene, settings and run order. The submitted per-run numbers support the description's cautious conclusion: Kakariko is within the observed spread, while Death Mountain Trail is too variable to establish a benefit. This does not justify changing AMD's default or extrapolating to other cards/drivers.

I also checked the renderer's feature selection and program-cache stamp: the description correctly distinguishes the compare-exchange default from explicitly enabled native float add, and explains using separately warmed folders. No runtime code or default changes here. The adjacent mesh-shader measurements are a separate experiment, not a dependency.

The author reports 25 format checks passing and the same 13 suite failures on both sides. I reviewed the submitted evidence and source; I did not independently reproduce the measurements. No tests or builds run.

Basic code-only review of 40d55c99bba20b8a8dde2b4ef6e62036a8080104; informational feedback, with final approval left to another reviewer. No obvious defect found in this documentation-only change. The four independent run records follow the tested-catalogue format and retain the hardware, driver, build identity, effective switch, scene, settings and run order. The submitted per-run numbers support the description's cautious conclusion: Kakariko is within the observed spread, while Death Mountain Trail is too variable to establish a benefit. This does not justify changing AMD's default or extrapolating to other cards/drivers. I also checked the renderer's feature selection and program-cache stamp: the description correctly distinguishes the compare-exchange default from explicitly enabled native float add, and explains using separately warmed folders. No runtime code or default changes here. The adjacent [mesh-shader measurements](https://git.magicbean.dev/MagicBeanDev/Longshot/pulls/1087) are a separate experiment, not a dependency. The author reports 25 format checks passing and the same 13 suite failures on both sides. I reviewed the submitted evidence and source; I did not independently reproduce the measurements. No tests or builds run.
Some checks are pending
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
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
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
PR description / Description follows the template (pull_request_target) Successful in 5s
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-native-fadd-rdna4:GrimVisage-docs/tested-native-fadd-rdna4'
git switch 'GrimVisage-docs/tested-native-fadd-rdna4'
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!1088
No description provided.