WIP: fix(vk): the Anisotropic filtering row leaves images of one level alone, so no bright lines along edges #910

Draft
bvtterbrot wants to merge 1 commit from bvtterbrot/Longshot:fix/aniso-one-level into main
First-time contributor

Type: fix · Risk: low · Tested on: Windows 11, AMD Radeon RX 7900 XTX, driver 26.10.1 (in Slingshot, a fork with the same sampler code; game-free checks here) · Needs: Windows or Linux, an AMD card, Lon Lon Ranch or Hyrule Field on main with this change

Why

With Anisotropic filtering above "Game's" (the default is 16x), thin dashed bright lines run along edges: mountain
ridges against the sky, roofs, shelves, and across the ground at Lon Lon Ranch. Players work around it by setting the
row to "Game's", which also takes the ground's sharpness away. Fixes #834, fixes #293, see #308 (its first point).

How to reproduce

Seen on: Windows 11, AMD Radeon RX 7900 XTX, driver 26.10.1 (in Slingshot; reported here on an RX 9070 XT, an RX 7800 XT on CachyOS and an RX 6750 XT: #834, #308)
Settings and switches: Anisotropic filtering 16x (any value above "Game's")
Steps: Stand in Lon Lon Ranch's field, or in Hyrule Field facing the mountains, and look along the ridges and roof edges.
Expected: Clean edges, as with the row at "Game's".
Actual: Dashed bright lines along the edges, one or two pixels wide.

What changed

The row's anisotropy is no longer added to a sampler when the image bound with it has a single level. The game's own
anisotropy stays, and mipmapped textures keep the row's value, so the ground's sharpness is unchanged.

The cause: the row's value went to every sampler with mip filtering, also where the game reads back a picture it drew
itself. OoT composites its half-size fog and particle layer (program 1a7482c0ec9991ea) through such a sampler. Where
a 2x2 block of pixels crosses an object's edge, its texture coordinates lie far apart, and the anisotropic filter
takes texels along that whole span: from the sky behind a ridge into the ridge.

  • renderer: sampler_make() and sampler_for() in gpu/vk/vk_draw.cpp take one_level; with it the row's value is
    left out of the sampler and of its cache key. sampler_for()'s thread table has a second index for it.
    build_descriptors() passes tex && tex->levels <= 1.
  • tests: tests/sampler_admission_test.cpp and tests/test_sampler_admission.py take the new argument and add the
    case anisotropy-one-level.
  • docs: the README's note on the row; docs/worklist.md moves the row to Fixed.

Measurements

Verdict: Not measured in Longshot yet. In Slingshot, with the same change to the same code, the lines went: 180
bright edge pixels on one ridge before, 0 to 3 after, and the ground's detail at 16x was kept.

Hardware: Windows 11, AMD Radeon RX 7900 XTX, driver 26.10.1
Scene: Lon Lon Ranch, day; a fixed camera from a save, headless, Anisotropic filtering 16x
Method: a frame saved before and after (RX_VK_SHOTS), bright pixels counted along one ridge by a script; RX_VK_ANISO=0 as the control (lines gone, ground blurred)
How to reproduce: the steps above, with the row at 16x and at "Game's"

Flags and settings

None new. The Anisotropic filtering row and RX_VK_ANISO no longer reach samplers bound with an image of one level.

Testing

Tested: The game-free checks on Windows 11: tests/test_sampler_admission.py passes with the new case. The whole
run (python -I -B tests/run_all.py --jobs 8, with the Vulkan headers): 561 passed, 20 failed, 42 skipped; the same
20 fail on main @ f637b42 on this PC (test_appimage_player_build, test_auto_handheld, test_cpp_preflight,
test_crash_dialog, test_crt_options, test_env_on, test_fpx_sticky, test_lift_cleanup_error, test_linux_preflight,
test_make_game_cache, test_make_game_prepare, test_missing_nup, test_oot_state_tap, test_options_budget_once,
test_readback_late, test_spawn_emit, test_tested_configurations, test_vk_occlusion_queries, test_vk_pgo,
test_walk_key). In the game: in Slingshot only (see Measurements), where it has been played since.

Not tested: Longshot built with this change, in the game. NVIDIA and Intel cards. Linux.

Must be tested:

  • Windows or Linux, an AMD card (amd, radv): Lon Lon Ranch's field and Hyrule Field facing the mountains with Anisotropic filtering at 16x, expecting no dashed bright lines along ridges and roofs and the ground as sharp as before (by hand: the same spot on main and on this branch, a screenshot each).
  • Windows or Linux, an NVIDIA or Intel card: the same spots at 16x, expecting no change from main (by hand: a screenshot each).

Risks

What could break: A single-level texture that is not a picture the game drew (a small texture without mipmaps)
no longer gets the row's anisotropy; it keeps the game's. With one level there is nothing sharper to pick, so the
difference should not show.

Turning it off: Revert the commit; "Game's" on the row behaves as before.

Compatibility: Nothing changes for saves, longshot_options.ini, the shader and pipeline caches or the vk ABI.

Issues

Fixes #834
Fixes #293
See #308

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. (measured in Slingshot, not yet in Longshot)
  • 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.
  • Screenshots of the same spot, captioned like the Measurements columns, for a change that shows on screen. (to come with the run in Longshot)
  • A game-free test added for the fix, failing on main and passing here.
  • 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. (the changed functions compile in the sampler check on Windows; the game was not built with it yet)
  • Docs updated.

🤖 Generated with Claude Code

**Type:** fix · **Risk:** low · **Tested on:** Windows 11, AMD Radeon RX 7900 XTX, driver 26.10.1 (in Slingshot, a fork with the same sampler code; game-free checks here) · **Needs:** Windows or Linux, an AMD card, Lon Lon Ranch or Hyrule Field on `main` with this change ## Why With Anisotropic filtering above "Game's" (the default is 16x), thin dashed bright lines run along edges: mountain ridges against the sky, roofs, shelves, and across the ground at Lon Lon Ranch. Players work around it by setting the row to "Game's", which also takes the ground's sharpness away. Fixes #834, fixes #293, see #308 (its first point). ## How to reproduce **Seen on:** Windows 11, AMD Radeon RX 7900 XTX, driver 26.10.1 (in Slingshot; reported here on an RX 9070 XT, an RX 7800 XT on CachyOS and an RX 6750 XT: #834, #308) **Settings and switches:** Anisotropic filtering 16x (any value above "Game's") **Steps:** Stand in Lon Lon Ranch's field, or in Hyrule Field facing the mountains, and look along the ridges and roof edges. **Expected:** Clean edges, as with the row at "Game's". **Actual:** Dashed bright lines along the edges, one or two pixels wide. ## What changed The row's anisotropy is no longer added to a sampler when the image bound with it has a single level. The game's own anisotropy stays, and mipmapped textures keep the row's value, so the ground's sharpness is unchanged. The cause: the row's value went to every sampler with mip filtering, also where the game reads back a picture it drew itself. OoT composites its half-size fog and particle layer (program `1a7482c0ec9991ea`) through such a sampler. Where a 2x2 block of pixels crosses an object's edge, its texture coordinates lie far apart, and the anisotropic filter takes texels along that whole span: from the sky behind a ridge into the ridge. - renderer: `sampler_make()` and `sampler_for()` in `gpu/vk/vk_draw.cpp` take `one_level`; with it the row's value is left out of the sampler and of its cache key. `sampler_for()`'s thread table has a second index for it. `build_descriptors()` passes `tex && tex->levels <= 1`. - tests: `tests/sampler_admission_test.cpp` and `tests/test_sampler_admission.py` take the new argument and add the case `anisotropy-one-level`. - docs: the README's note on the row; `docs/worklist.md` moves the row to Fixed. ## Measurements **Verdict:** Not measured in Longshot yet. In Slingshot, with the same change to the same code, the lines went: 180 bright edge pixels on one ridge before, 0 to 3 after, and the ground's detail at 16x was kept. Hardware: Windows 11, AMD Radeon RX 7900 XTX, driver 26.10.1 Scene: Lon Lon Ranch, day; a fixed camera from a save, headless, Anisotropic filtering 16x Method: a frame saved before and after (`RX_VK_SHOTS`), bright pixels counted along one ridge by a script; `RX_VK_ANISO=0` as the control (lines gone, ground blurred) How to reproduce: the steps above, with the row at 16x and at "Game's" ### Flags and settings None new. The Anisotropic filtering row and `RX_VK_ANISO` no longer reach samplers bound with an image of one level. ## Testing **Tested:** The game-free checks on Windows 11: `tests/test_sampler_admission.py` passes with the new case. The whole run (`python -I -B tests/run_all.py --jobs 8`, with the Vulkan headers): 561 passed, 20 failed, 42 skipped; the same 20 fail on `main` @ f637b42 on this PC (test_appimage_player_build, test_auto_handheld, test_cpp_preflight, test_crash_dialog, test_crt_options, test_env_on, test_fpx_sticky, test_lift_cleanup_error, test_linux_preflight, test_make_game_cache, test_make_game_prepare, test_missing_nup, test_oot_state_tap, test_options_budget_once, test_readback_late, test_spawn_emit, test_tested_configurations, test_vk_occlusion_queries, test_vk_pgo, test_walk_key). In the game: in Slingshot only (see Measurements), where it has been played since. **Not tested:** Longshot built with this change, in the game. NVIDIA and Intel cards. Linux. **Must be tested:** - Windows or Linux, an AMD card (amd, radv): Lon Lon Ranch's field and Hyrule Field facing the mountains with Anisotropic filtering at 16x, expecting no dashed bright lines along ridges and roofs and the ground as sharp as before (by hand: the same spot on `main` and on this branch, a screenshot each). - Windows or Linux, an NVIDIA or Intel card: the same spots at 16x, expecting no change from `main` (by hand: a screenshot each). ## Risks **What could break:** A single-level texture that is not a picture the game drew (a small texture without mipmaps) no longer gets the row's anisotropy; it keeps the game's. With one level there is nothing sharper to pick, so the difference should not show. **Turning it off:** Revert the commit; "Game's" on the row behaves as before. **Compatibility:** Nothing changes for saves, `longshot_options.ini`, the shader and pipeline caches or the vk ABI. ## Issues Fixes #834 Fixes #293 See #308 ## 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). - [ ] Measurements has a verdict, or one line saying why there is nothing to measure. (measured in Slingshot, not yet in Longshot) - [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. - [ ] Screenshots of the same spot, captioned like the Measurements columns, for a change that shows on screen. (to come with the run in Longshot) - [x] A game-free test added for the fix, failing on `main` and passing here. - [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. (the changed functions compile in the sampler check on Windows; the game was not built with it yet) - [x] Docs updated. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
fix(vk): the Anisotropic filtering row leaves images of one level alone, so no bright lines along edges
Some checks failed
Website / Website on Cloudflare (pull_request_target) Has been skipped
PR description / Description follows the template (pull_request_target) Has been cancelled
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
b8959c5a40
The row's anisotropy (16x by default) went to every sampler with mip filtering, also where the game reads back a
picture it drew itself. OoT composites its half-size fog and particle layer (program 1a7482c0ec9991ea) through such a
sampler; where a 2x2 block of pixels crosses an object's edge its texture coordinates lie far apart, and the
anisotropic filter took texels along that whole span: dashed bright lines along mountain ridges, roofs and shelves
(#834, #293, #308's first point).

sampler_make and sampler_for take whether the bound image has one level; then only the game's own anisotropy applies,
and the row's value is not part of the sampler's key. Mipmapped textures keep the row's value.

Ported from Slingshot, where it was reproduced headless on an RX 7900 XTX at Lon Lon Ranch: 180 bright edge pixels on
one ridge before, 0 to 3 after, with the ground's detail at 16x kept. Not yet played in Longshot.

Co-Authored-By: Claude Fable 5.2 <[email protected]>
bvtterbrot force-pushed fix/aniso-one-level from b8959c5a40
Some checks failed
Website / Website on Cloudflare (pull_request_target) Has been skipped
PR description / Description follows the template (pull_request_target) Has been cancelled
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
to 29ed5fb9b2
Some checks reported errors
PR description / Description follows the template (pull_request_target) Successful in 3s
Website / Website on Cloudflare (pull_request_target) Has been skipped
beanstalk/approval approved by HumanBean (reviewed)
beanstalk/amd 0/1 pass, 0 running, 1 queued
beanstalk/nvidia 0/1 pass, 1 error
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
2026-11-15 20:15:38 +00:00
Compare
Owner

@Beanstalk

@Beanstalk
Member

Beanstalk test farm

Commit e4609af · tier reviewed · approved by HumanBean · dashboard

What will be tested · AI plan (gpt-6.1-terra)

On Tommy’s and futondestroyer’s Windows PCs, this plan compares Kokiri Forest, Hyrule Field and the Lake Hylia teleport area against main, taking about 13 minutes per PC. It tests both the game’s anisotropy and 16x because the fix changes how the filtering override is applied. Screenshots, frametimes and load times are compared; crashes, large visual differences or specified performance regressions fail the plan. The screenshot comparison cannot by itself establish that AMD’s bright-line artifact is fixed.

  • Where: windows+tester-tommy (1 report), windows+tester-futondestroyer (1 report).
  • Matrix: 2 cells, each on main and the PR: anisotropic_filtering 0 or 4.
  • outdoor-filtering: from a new save, then take the picture kokiri to compare with main, measure kokiri for 10 s (after 5 s warm-up), teleport to Hyrule Field, take the picture field to compare with main, measure field for 10 s (after 5 s warm-up), teleport to Lake Hylia, take the picture lake to compare with main, measure lake for 10 s (after 5 s warm-up); 1 run on each side for each of 2 cells (1 game start a run).
  • Measured: crashes, frame times, stutters and hitches, load times.
  • The PR fails if: it crashes; or a picture differs from main by more than 3%; or longest load is more than 25% above main; or frame time (p99) is more than 20% above main.
  • Time: about 15 min of game runs per tester (2 game starts), plus the two builds.

Started. Run 16: the farm's reports were cleared after its Windows and Linux fixes: started again.

Target Reports Crash Frame p99 (ms) vs main VRAM peak (MB) vs main Result
windows+tester-tommy 0/1 — — — queued
windows+tester-futondestroyer · 1: windows+nvidia+nvidia-proprietary+dgpu NVIDIA GeForce RTX 4070, 621.1.0 1/1 1 none 41.2 vs 51.4 (−20%) — fail
Scenario · matrix cell Target Frame p99 (ms) vs main Result
outdoor-filtering · anisotropic_filtering=0 windows+tester-tommy — —
outdoor-filtering · anisotropic_filtering=0 windows+tester-futondestroyer 41.2 vs 51.4 (−20%) pass
outdoor-filtering · anisotropic_filtering=4 windows+tester-tommy — —
outdoor-filtering · anisotropic_filtering=4 windows+tester-futondestroyer 22.3 vs 24.1 (−7%) fail

Measurements · windows+tester-futondestroyer

Verdict: fail on windows+tester-futondestroyer (1/1 report): outdoor-filtering screenshot.max_diff failed.

Hardware: 1: windows+nvidia+nvidia-proprietary+dgpu NVIDIA GeForce RTX 4070, 621.1.0 13th Gen Intel(R) Core(TM) i7-13700F, 32 GB RAM
Scene: outdoor-filtering, from a new save; each cell's settings and switches as the table names them
Method: the Beanstalk test farm: main and this PR built and run on the same PC in one session, game starts alternating (ABBA); outdoor-filtering: 1 game start a side, kokiri 10 s after 5 s warm-up, field 10 s after 5 s warm-up, lake 10 s after 5 s warm-up; each number the median of the runs, then of 1 report
How to reproduce: the farm's plan above (@Beanstalk on this PR runs it again)

Before: main @ 0260816 After: this PR @ e4609af
outdoor-filtering · anisotropic_filtering=0 · longest load (s) 5.8 4.3 (−25%)
outdoor-filtering · anisotropic_filtering=0 · lake · frame time (p99) (ms) 51.4 41.2 (−20%)
outdoor-filtering · anisotropic_filtering=0 · field · frame time (p99) (ms) 20.9 21.4 (+3%)
outdoor-filtering · anisotropic_filtering=0 · kokiri · frame time (p99) (ms) 22.6 26.1 (+16%)
outdoor-filtering · anisotropic_filtering=4 · longest load (s) 0.0 0.0 (+0%)
outdoor-filtering · anisotropic_filtering=4 · lake · frame time (p99) (ms) 24.1 22.3 (−7%)
outdoor-filtering · anisotropic_filtering=4 · field · frame time (p99) (ms) 20.0 23.5 (+17%)
outdoor-filtering · anisotropic_filtering=4 · kokiri · frame time (p99) (ms) 22.3 24.6 (+10%)

Flags and settings

Flag What it is Values tried Before this PR After this PR Effect (frame time (p99)) Helps / doesn't help / untested
anisotropic_filtering menu setting 0, 4 main's default the PR's default outdoor-filtering, the PR at 0 → at 4: 41.2 → 22.3 (−46%) helps
Markdown for the PR description
## Measurements

**Verdict:** fail on windows+tester-futondestroyer (1/1 report): `outdoor-filtering screenshot.max_diff` failed.

Hardware: 1: windows+nvidia+nvidia-proprietary+dgpu `NVIDIA GeForce RTX 4070, 621.1.0` `13th Gen Intel(R) Core(TM) i7-13700F, 32 GB RAM`  
Scene: outdoor-filtering, from a new save; each cell's settings and switches as the table names them  
Method: the Beanstalk test farm: main and this PR built and run on the same PC in one session, game starts alternating (ABBA); outdoor-filtering: 1 game start a side, kokiri 10 s after 5 s warm-up, field 10 s after 5 s warm-up, lake 10 s after 5 s warm-up; each number the median of the runs, then of 1 report  
How to reproduce: the farm's plan above (`@Beanstalk` on this PR runs it again)

| | Before: main @ 0260816 | After: this PR @ e4609af |
|---|---|---|
| outdoor-filtering · `anisotropic_filtering=0` · longest load (s) | 5.8 | 4.3 (−25%) |
| outdoor-filtering · `anisotropic_filtering=0` · lake · frame time (p99) (ms) | 51.4 | 41.2 (−20%) |
| outdoor-filtering · `anisotropic_filtering=0` · field · frame time (p99) (ms) | 20.9 | 21.4 (+3%) |
| outdoor-filtering · `anisotropic_filtering=0` · kokiri · frame time (p99) (ms) | 22.6 | 26.1 (+16%) |
| outdoor-filtering · `anisotropic_filtering=4` · longest load (s) | 0.0 | 0.0 (+0%) |
| outdoor-filtering · `anisotropic_filtering=4` · lake · frame time (p99) (ms) | 24.1 | 22.3 (−7%) |
| outdoor-filtering · `anisotropic_filtering=4` · field · frame time (p99) (ms) | 20.0 | 23.5 (+17%) |
| outdoor-filtering · `anisotropic_filtering=4` · kokiri · frame time (p99) (ms) | 22.3 | 24.6 (+10%) |

### Flags and settings

| Flag | What it is | Values tried | Before this PR | After this PR | Effect (frame time (p99)) | Helps / doesn't help / untested |
|---|---|---|---|---|---|---|
| `anisotropic_filtering` | menu setting | `0`, `4` | main's default | the PR's default | outdoor-filtering, the PR at 0 → at 4: 41.2 → 22.3 (−46%) | helps |
<!-- beanstalk:sticky --> ### Beanstalk test farm Commit `e4609af` · tier **reviewed** · approved by HumanBean · [dashboard](https://beanstalk.magicbean.dev/prs/910) **What will be tested** · AI plan (`gpt-6.1-terra`) On Tommy’s and futondestroyer’s Windows PCs, this plan compares Kokiri Forest, Hyrule Field and the Lake Hylia teleport area against main, taking about 13 minutes per PC. It tests both the game’s anisotropy and 16x because the fix changes how the filtering override is applied. Screenshots, frametimes and load times are compared; crashes, large visual differences or specified performance regressions fail the plan. The screenshot comparison cannot by itself establish that AMD’s bright-line artifact is fixed. - **Where:** windows+tester-tommy (1 report), windows+tester-futondestroyer (1 report). - **Matrix:** 2 cells, each on main and the PR: anisotropic_filtering `0` or `4`. - **outdoor-filtering:** from a new save, then take the picture kokiri to compare with main, measure kokiri for 10 s (after 5 s warm-up), teleport to Hyrule Field, take the picture field to compare with main, measure field for 10 s (after 5 s warm-up), teleport to Lake Hylia, take the picture lake to compare with main, measure lake for 10 s (after 5 s warm-up); 1 run on each side for each of 2 cells (1 game start a run). - **Measured:** crashes, frame times, stutters and hitches, load times. - **The PR fails if:** it crashes; or a picture differs from main by more than 3%; or longest load is more than 25% above main; or frame time (p99) is more than 20% above main. - **Time:** about 15 min of game runs per tester (2 game starts), plus the two builds. Started. Run 16: the farm's reports were cleared after its Windows and Linux fixes: started again. | Target | Reports | Crash | Frame p99 (ms) vs main | VRAM peak (MB) vs main | Result | | --- | --- | --- | --- | --- | --- | | windows+tester-tommy | 0/1 | — | — | — | queued | | windows+tester-futondestroyer · 1: windows+nvidia+nvidia-proprietary+dgpu `NVIDIA GeForce RTX 4070, 621.1.0` | 1/1 [1](https://beanstalk.magicbean.dev/reports/rp_8a2d3e9627449f0c) | none | 41.2 vs 51.4 (−20%) | — | fail | | Scenario · matrix cell | Target | Frame p99 (ms) vs main | Result | | --- | --- | --- | --- | | outdoor-filtering · `anisotropic_filtering=0` | windows+tester-tommy | — | — | | outdoor-filtering · `anisotropic_filtering=0` | windows+tester-futondestroyer | 41.2 vs 51.4 (−20%) | pass | | outdoor-filtering · `anisotropic_filtering=4` | windows+tester-tommy | — | — | | outdoor-filtering · `anisotropic_filtering=4` | windows+tester-futondestroyer | 22.3 vs 24.1 (−7%) | fail | #### Measurements · windows+tester-futondestroyer **Verdict:** fail on windows+tester-futondestroyer (1/1 report): `outdoor-filtering screenshot.max_diff` failed. Hardware: 1: windows+nvidia+nvidia-proprietary+dgpu `NVIDIA GeForce RTX 4070, 621.1.0` `13th Gen Intel(R) Core(TM) i7-13700F, 32 GB RAM` Scene: outdoor-filtering, from a new save; each cell's settings and switches as the table names them Method: the Beanstalk test farm: main and this PR built and run on the same PC in one session, game starts alternating (ABBA); outdoor-filtering: 1 game start a side, kokiri 10 s after 5 s warm-up, field 10 s after 5 s warm-up, lake 10 s after 5 s warm-up; each number the median of the runs, then of 1 report How to reproduce: the farm's plan above (`@Beanstalk` on this PR runs it again) | | Before: main @ 0260816 | After: this PR @ e4609af | |---|---|---| | outdoor-filtering · `anisotropic_filtering=0` · longest load (s) | 5.8 | 4.3 (−25%) | | outdoor-filtering · `anisotropic_filtering=0` · lake · frame time (p99) (ms) | 51.4 | 41.2 (−20%) | | outdoor-filtering · `anisotropic_filtering=0` · field · frame time (p99) (ms) | 20.9 | 21.4 (+3%) | | outdoor-filtering · `anisotropic_filtering=0` · kokiri · frame time (p99) (ms) | 22.6 | 26.1 (+16%) | | outdoor-filtering · `anisotropic_filtering=4` · longest load (s) | 0.0 | 0.0 (+0%) | | outdoor-filtering · `anisotropic_filtering=4` · lake · frame time (p99) (ms) | 24.1 | 22.3 (−7%) | | outdoor-filtering · `anisotropic_filtering=4` · field · frame time (p99) (ms) | 20.0 | 23.5 (+17%) | | outdoor-filtering · `anisotropic_filtering=4` · kokiri · frame time (p99) (ms) | 22.3 | 24.6 (+10%) | ### Flags and settings | Flag | What it is | Values tried | Before this PR | After this PR | Effect (frame time (p99)) | Helps / doesn't help / untested | |---|---|---|---|---|---|---| | `anisotropic_filtering` | menu setting | `0`, `4` | main's default | the PR's default | outdoor-filtering, the PR at 0 → at 4: 41.2 → 22.3 (−46%) | helps | <details><summary>Markdown for the PR description</summary> ```markdown ## Measurements **Verdict:** fail on windows+tester-futondestroyer (1/1 report): `outdoor-filtering screenshot.max_diff` failed. Hardware: 1: windows+nvidia+nvidia-proprietary+dgpu `NVIDIA GeForce RTX 4070, 621.1.0` `13th Gen Intel(R) Core(TM) i7-13700F, 32 GB RAM` Scene: outdoor-filtering, from a new save; each cell's settings and switches as the table names them Method: the Beanstalk test farm: main and this PR built and run on the same PC in one session, game starts alternating (ABBA); outdoor-filtering: 1 game start a side, kokiri 10 s after 5 s warm-up, field 10 s after 5 s warm-up, lake 10 s after 5 s warm-up; each number the median of the runs, then of 1 report How to reproduce: the farm's plan above (`@Beanstalk` on this PR runs it again) | | Before: main @ 0260816 | After: this PR @ e4609af | |---|---|---| | outdoor-filtering · `anisotropic_filtering=0` · longest load (s) | 5.8 | 4.3 (−25%) | | outdoor-filtering · `anisotropic_filtering=0` · lake · frame time (p99) (ms) | 51.4 | 41.2 (−20%) | | outdoor-filtering · `anisotropic_filtering=0` · field · frame time (p99) (ms) | 20.9 | 21.4 (+3%) | | outdoor-filtering · `anisotropic_filtering=0` · kokiri · frame time (p99) (ms) | 22.6 | 26.1 (+16%) | | outdoor-filtering · `anisotropic_filtering=4` · longest load (s) | 0.0 | 0.0 (+0%) | | outdoor-filtering · `anisotropic_filtering=4` · lake · frame time (p99) (ms) | 24.1 | 22.3 (−7%) | | outdoor-filtering · `anisotropic_filtering=4` · field · frame time (p99) (ms) | 20.0 | 23.5 (+17%) | | outdoor-filtering · `anisotropic_filtering=4` · kokiri · frame time (p99) (ms) | 22.3 | 24.6 (+10%) | ### Flags and settings | Flag | What it is | Values tried | Before this PR | After this PR | Effect (frame time (p99)) | Helps / doesn't help / untested | |---|---|---|---|---|---|---| | `anisotropic_filtering` | menu setting | `0`, `4` | main's default | the PR's default | outdoor-filtering, the PR at 0 → at 4: 41.2 → 22.3 (−46%) | helps | ``` </details>
HumanBean force-pushed fix/aniso-one-level from 29ed5fb9b2
Some checks reported errors
PR description / Description follows the template (pull_request_target) Successful in 3s
Website / Website on Cloudflare (pull_request_target) Has been skipped
beanstalk/approval approved by HumanBean (reviewed)
beanstalk/amd 0/1 pass, 0 running, 1 queued
beanstalk/nvidia 0/1 pass, 1 error
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
to e4609af92a
Some checks failed
CI / Workflow lint (actionlint) (pull_request) Successful in 6s
Guide screenshots / Guide images and local UI source review (pull_request) Failing after 5s
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
PR description / Description follows the template (pull_request_target) Successful in 4s
CI / Conventional Commit title (pull_request) Successful in 3s
Third-party parts / As their notes say (pull_request) Successful in 9s
Website / Website on Cloudflare (pull_request_target) Has been skipped
beanstalk/tester-tommy 0/1 pass, 0 running, 0 queued
beanstalk/windows+tester-jiro113 0/1 pass, 0 running, 0 queued
beanstalk/windows+tester-dyst 0/1 pass, 0 running, 0 queued
beanstalk/amd 0/1 pass, 0 running, 0 queued
beanstalk/nvidia 0/1 pass, 0 running, 0 queued
beanstalk/tester-zealotn 0/1 pass, 0 running, 0 queued
beanstalk/tester-futondestroyer 0/1 pass, 0 running, 0 queued
beanstalk/approval approved by HumanBean (reviewed)
beanstalk/windows+tester-tommy 0/1 pass, 0 running, 1 queued
beanstalk/windows+tester-futondestroyer 1/1 fail
2026-11-15 22:40:26 +00:00
Compare
Owner

Rebased onto main @ 02608169 (now e4609af9). One conflict, in sampler_for (gpu/vk/vk_draw.cpp): main added a frame to each thread-table entry (the sampler book, near the device's sampler limit), so the entry is now {gen, s, frame} in table[compare][one_level][id], checked as e.gen == gen && e.frame == frame. The rest of the change is as you wrote it.

Checks after the rebase (Linux): tests/test_sampler_admission.py --headers /usr/include --cxx clang++ passes all 153 cases, also with --sanitize. In the full run_all.py (Vulkan, SPIR-V and VMA headers given) 20 fail, the same 20 as on main without this change.

In the game on an RTX 3090 (Linux), as a renderer pack on main @ a00c485c, Anisotropic filtering at 16x, headless: Lake Hylia's ridges, the Hyrule Field gorge and the Kokiri start look the same as main, at 60 fps, with no new errors in the log. This GPU doesn't show the lines on main either, so it says nothing about the fix itself: that still needs an AMD run, main then this PR, at Lon Lon Ranch or the Kokiri start.

Rebased onto main @ 02608169 (now e4609af9). One conflict, in `sampler_for` (`gpu/vk/vk_draw.cpp`): main added a frame to each thread-table entry (the sampler book, near the device's sampler limit), so the entry is now `{gen, s, frame}` in `table[compare][one_level][id]`, checked as `e.gen == gen && e.frame == frame`. The rest of the change is as you wrote it. Checks after the rebase (Linux): `tests/test_sampler_admission.py --headers /usr/include --cxx clang++` passes all 153 cases, also with `--sanitize`. In the full `run_all.py` (Vulkan, SPIR-V and VMA headers given) 20 fail, the same 20 as on main without this change. In the game on an RTX 3090 (Linux), as a renderer pack on main @ a00c485c, Anisotropic filtering at 16x, headless: Lake Hylia's ridges, the Hyrule Field gorge and the Kokiri start look the same as main, at 60 fps, with no new errors in the log. This GPU doesn't show the lines on main either, so it says nothing about the fix itself: that still needs an AMD run, main then this PR, at Lon Lon Ranch or the Kokiri start.
Owner

@Beanstalk

@Beanstalk
Owner

@Beanstalk

@Beanstalk
Member

@HumanBean e4609af is already running: see the dashboard.

@HumanBean `e4609af` is already running: see the [dashboard](https://beanstalk.magicbean.dev/prs/910).
Owner

@Beanstalk cancel

@Beanstalk cancel
Owner

@Beanstalk

@Beanstalk
Member

@HumanBean e4609af is already running: see the dashboard.

@HumanBean `e4609af` is already running: see the [dashboard](https://beanstalk.magicbean.dev/prs/910).
Owner

@Beanstalk cancel

@Beanstalk cancel
Member

@HumanBean cancelled 1 queued job.

@HumanBean cancelled 1 queued job.
Owner

@Beanstalk

@Beanstalk
Owner

@Beanstalk cancel

@Beanstalk cancel
Member

@HumanBean cancelled 1 queued job.

@HumanBean cancelled 1 queued job.
Owner

@Beanstalk

@Beanstalk
Owner

@Beanstalk cancel

@Beanstalk cancel
Member

@HumanBean cancelled 1 queued job.

@HumanBean cancelled 1 queued job.
Owner

@Beanstalk

@Beanstalk
Owner

@Beanstalk cancel

@Beanstalk cancel
Member

@HumanBean cancelled 1 queued job.

@HumanBean cancelled 1 queued job.
Owner

@Beanstalk

@Beanstalk
Owner

@Beanstalk cancel

@Beanstalk cancel
Member

@HumanBean cancelled 1 queued job.

@HumanBean cancelled 1 queued job.
Owner

@Beanstalk

@Beanstalk
Owner

@Beanstalk plan One target only, Tommy's PC: tags = ["tester-tommy"] (Windows, NVIDIA; it has the Beanstalk agent with the new Windows sandbox probe). Keep the same scenes as the last plan.

@Beanstalk plan One target only, Tommy's PC: tags = ["tester-tommy"] (Windows, NVIDIA; it has the Beanstalk agent with the new Windows sandbox probe). Keep the same scenes as the last plan.
Owner

@Beanstalk plan One target only, futondestroyer's PC: tags = ["tester-futondestroyer"] (Windows, RTX 4070; it has the Beanstalk agent with the new Windows sandbox probe, and gameplay on). The same scenes as the plan before: Kokiri Forest, Hyrule Field and Lake Hylia against main.

@Beanstalk plan One target only, futondestroyer's PC: tags = ["tester-futondestroyer"] (Windows, RTX 4070; it has the Beanstalk agent with the new Windows sandbox probe, and gameplay on). The same scenes as the plan before: Kokiri Forest, Hyrule Field and Lake Hylia against main.
Owner

@Beanstalk plan One target only, zealotn's PC: tags = ["tester-zealotn"] (Windows; it has the Beanstalk agent with the new Windows sandbox probe). The same scenes as the plan before: Kokiri Forest, Hyrule Field and Lake Hylia against main.

@Beanstalk plan One target only, zealotn's PC: tags = ["tester-zealotn"] (Windows; it has the Beanstalk agent with the new Windows sandbox probe). The same scenes as the plan before: Kokiri Forest, Hyrule Field and Lake Hylia against main.
Owner

@Beanstalk plan One target only, futondestroyer's PC: tags = ["tester-futondestroyer"] (Windows, RTX 4070; it has the Beanstalk agent with the new Windows work drive). The same scenes as the plan before: Kokiri Forest, Hyrule Field and Lake Hylia against main.

@Beanstalk plan One target only, futondestroyer's PC: tags = ["tester-futondestroyer"] (Windows, RTX 4070; it has the Beanstalk agent with the new Windows work drive). The same scenes as the plan before: Kokiri Forest, Hyrule Field and Lake Hylia against main.
Owner

@Beanstalk plan One target only, Tommy's PC: tags = ["tester-tommy"] (Windows, NVIDIA; it has the Beanstalk agent with the Windows work drive and the clang fix). The same scenes as the plan before: Kokiri Forest, Hyrule Field and Lake Hylia against main.

@Beanstalk plan One target only, Tommy's PC: tags = ["tester-tommy"] (Windows, NVIDIA; it has the Beanstalk agent with the Windows work drive and the clang fix). The same scenes as the plan before: Kokiri Forest, Hyrule Field and Lake Hylia against main.
Owner

@Beanstalk plan One target only, Tommy's PC: tags = ["tester-tommy"] (Windows, NVIDIA). The same scenes as the plan before: Kokiri Forest, Hyrule Field and Lake Hylia against main. (Again: the last try lost its lease.)

@Beanstalk plan One target only, Tommy's PC: tags = ["tester-tommy"] (Windows, NVIDIA). The same scenes as the plan before: Kokiri Forest, Hyrule Field and Lake Hylia against main. (Again: the last try lost its lease.)
Owner

@Beanstalk plan One target only, Tommy's PC: tags = ["tester-tommy"] (Windows, NVIDIA; on the nightly with the clang fixes). The same scenes as the plan before: Kokiri Forest, Hyrule Field and Lake Hylia against main.

@Beanstalk plan One target only, Tommy's PC: tags = ["tester-tommy"] (Windows, NVIDIA; on the nightly with the clang fixes). The same scenes as the plan before: Kokiri Forest, Hyrule Field and Lake Hylia against main.
Owner

@Beanstalk plan Windows only, to check Windows builds end to end: two targets, one report each, Jiro113's PC (tags = ["tester-jiro113"]) and dyst's PC (tags = ["tester-dyst"]). Keep the scenarios as they were.

@Beanstalk plan Windows only, to check Windows builds end to end: two targets, one report each, Jiro113's PC (tags = ["tester-jiro113"]) and dyst's PC (tags = ["tester-dyst"]). Keep the scenarios as they were.
Owner

@Beanstalk plan Windows only again, now that the farm's Windows sandbox fix for the lift is out: two targets, one report each, Tommy's PC (tags = ["tester-tommy"]) and futondestroyer's PC (tags = ["tester-futondestroyer"]). Keep the scenarios as they were.

@Beanstalk plan Windows only again, now that the farm's Windows sandbox fix for the lift is out: two targets, one report each, Tommy's PC (tags = ["tester-tommy"]) and futondestroyer's PC (tags = ["tester-futondestroyer"]). Keep the scenarios as they were.
Author
First-time contributor

The AMD run asked for above, at Lon Lon Ranch. It is on v3.0.0-rc.4, not on main: the renderer alone was built twice from the rc.4 tag (RX_VK_ONLY), once as it is and once with this PR's change to gpu/vk/vk_draw.cpp, and each DLL was put into a copy of an rc.4 game folder, so the game, the caches and everything else are the same in both.

Verdict: the dashed bright line along the ridge is there without the change and gone with it.

Hardware: Windows 11, AMD Radeon RX 7900 XTX, driver 26.10.1
Scene: Lon Lon Ranch's field, day, facing the mountain behind the fence; 2560x1440, FSR (upscaling 2), Anisotropic filtering 16x
Method: headless (longshot_ctl.py launch --headless --ready play, RX_VK_SHOT_W=2560 RX_VK_SHOT_H=1440), the same save and camera each time, 2 runs each way interleaved, 2 screenshots a run; counted: pixels brighter than both neighbours across a line by more than 25 in luma, in the 600x110 region of the ridge (x 1300, y 230)

Before: v3.0.0-rc.4 (b784a40c) After: v3.0.0-rc.4 with this change
Isolated bright pixels on the ridge, run 1 (two shots) 177, 161 0, 0
Isolated bright pixels on the ridge, run 2 (two shots) 169, 160 1, 0

The ridge behind the fence, the counted region enlarged 3x:

Before: v3.0.0-rc.4 (b784a40c), 16x

After: v3.0.0-rc.4 with this change, 16x

The ground's detail at 16x looks the same in both (same crop compared by eye).

Not covered by this run: main with the change (the sampler's thread table differs there since the rebase), other AMD cards, Linux.

The AMD run asked for above, at Lon Lon Ranch. It is on v3.0.0-rc.4, not on `main`: the renderer alone was built twice from the rc.4 tag (`RX_VK_ONLY`), once as it is and once with this PR's change to `gpu/vk/vk_draw.cpp`, and each DLL was put into a copy of an rc.4 game folder, so the game, the caches and everything else are the same in both. **Verdict:** the dashed bright line along the ridge is there without the change and gone with it. Hardware: Windows 11, AMD Radeon RX 7900 XTX, driver 26.10.1 Scene: Lon Lon Ranch's field, day, facing the mountain behind the fence; 2560x1440, FSR (upscaling 2), Anisotropic filtering 16x Method: headless (`longshot_ctl.py launch --headless --ready play`, `RX_VK_SHOT_W=2560 RX_VK_SHOT_H=1440`), the same save and camera each time, 2 runs each way interleaved, 2 screenshots a run; counted: pixels brighter than both neighbours across a line by more than 25 in luma, in the 600x110 region of the ridge (x 1300, y 230) | | Before: v3.0.0-rc.4 (b784a40c) | After: v3.0.0-rc.4 with this change | |---|---|---| | Isolated bright pixels on the ridge, run 1 (two shots) | 177, 161 | 0, 0 | | Isolated bright pixels on the ridge, run 2 (two shots) | 169, 160 | 1, 0 | The ridge behind the fence, the counted region enlarged 3x: ![Before: v3.0.0-rc.4 (b784a40c), 16x](https://git.magicbean.dev/attachments/edc655bb-f764-46f2-b2f8-ece3c460554f) ![After: v3.0.0-rc.4 with this change, 16x](https://git.magicbean.dev/attachments/8e7a2f71-1b18-4f89-9263-670b389a0a08) The ground's detail at 16x looks the same in both (same crop compared by eye). Not covered by this run: `main` with the change (the sampler's thread table differs there since the rebase), other AMD cards, Linux.
Author
First-time contributor

On the farm's screenshot.max_diff failure at 16x (kokiri 0.366, field 0.364, lake 0.025 against main, one game start a side): I checked how much two runs of the same build differ in a scene with things moving in it.

Setup: Windows 11, RX 7900 XTX, v3.0.0-rc.4 with the renderer built twice (as it is, and with this change), Lon Lon Ranch's field from the same save, 16x, headless at 2560x1440, 2 runs each way interleaved, one picture 30 s after play. (The teleports to Kokiri and Hyrule Field were sent but did not move Link, so both pictures are of the ranch; the horses walk and the grass sways there.)

Share of pixels that differ by more than 16 in any channel:

Picture 1 Picture 2
main-equivalent vs main-equivalent (same build, two runs) 49.3% 10.3%
this change vs this change 47.7% 7.4%
main-equivalent vs this change (four pairings) 47.0% to 51.4% 6.2% to 11.3%

Two runs of the same build already differ as much as the build with and without this change, so in a scene with moving horses, grass or Link's idle pose, one picture a side can't separate this change from the scene itself. The ridge count above (177/161/169/160 → 0/0/1/0) is in a region with nothing moving. At "Game's", where this change does nothing, the farm's pictures matched within 1.2%, which suggests the scenes it compares at 16x moved more between starts. A picture taken from a fixed camera with nothing animated, or several runs a side, would tell more; I can't say from here which of the two the farm's 36% is.

On the farm's `screenshot.max_diff` failure at 16x (kokiri 0.366, field 0.364, lake 0.025 against main, one game start a side): I checked how much two runs of the same build differ in a scene with things moving in it. Setup: Windows 11, RX 7900 XTX, v3.0.0-rc.4 with the renderer built twice (as it is, and with this change), Lon Lon Ranch's field from the same save, 16x, headless at 2560x1440, 2 runs each way interleaved, one picture 30 s after play. (The teleports to Kokiri and Hyrule Field were sent but did not move Link, so both pictures are of the ranch; the horses walk and the grass sways there.) Share of pixels that differ by more than 16 in any channel: | | Picture 1 | Picture 2 | |---|---|---| | main-equivalent vs main-equivalent (same build, two runs) | 49.3% | 10.3% | | this change vs this change | 47.7% | 7.4% | | main-equivalent vs this change (four pairings) | 47.0% to 51.4% | 6.2% to 11.3% | Two runs of the same build already differ as much as the build with and without this change, so in a scene with moving horses, grass or Link's idle pose, one picture a side can't separate this change from the scene itself. The ridge count above (177/161/169/160 → 0/0/1/0) is in a region with nothing moving. At "Game's", where this change does nothing, the farm's pictures matched within 1.2%, which suggests the scenes it compares at 16x moved more between starts. A picture taken from a fixed camera with nothing animated, or several runs a side, would tell more; I can't say from here which of the two the farm's 36% is.
Some checks failed
CI / Workflow lint (actionlint) (pull_request) Successful in 6s
Guide screenshots / Guide images and local UI source review (pull_request) Failing after 5s
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
PR description / Description follows the template (pull_request_target) Successful in 4s
CI / Conventional Commit title (pull_request) Successful in 3s
Third-party parts / As their notes say (pull_request) Successful in 9s
Website / Website on Cloudflare (pull_request_target) Has been skipped
beanstalk/tester-tommy 0/1 pass, 0 running, 0 queued
beanstalk/windows+tester-jiro113 0/1 pass, 0 running, 0 queued
beanstalk/windows+tester-dyst 0/1 pass, 0 running, 0 queued
beanstalk/amd 0/1 pass, 0 running, 0 queued
beanstalk/nvidia 0/1 pass, 0 running, 0 queued
beanstalk/tester-zealotn 0/1 pass, 0 running, 0 queued
beanstalk/tester-futondestroyer 0/1 pass, 0 running, 0 queued
beanstalk/approval approved by HumanBean (reviewed)
beanstalk/windows+tester-tommy 0/1 pass, 0 running, 1 queued
beanstalk/windows+tester-futondestroyer 1/1 fail
This pull request has changes conflicting with the target branch.
  • README.md
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 'fix/aniso-one-level:bvtterbrot-fix/aniso-one-level'
git switch 'bvtterbrot-fix/aniso-one-level'
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
3 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!910
No description provided.