perf(vk): Custom with no preset behind it trims the large textures where Auto would pick Minimum #1388

Open
zeldaootr wants to merge 3 commits from zeldaootr/Longshot:vk-texture-trim-auto-tier into main
Contributor

Type: perf · Risk: low · Tested on: Steam Deck OLED (SteamOS 3.9.5, RADV) · Needs: Windows, an AMD or Intel integrated GPU (renderer only)

Why

On a Steam Deck, and other PCs with an integrated GPU and 16 GB of RAM or less, a player whose Quality preset reads Custom with no preset behind it gets the largest textures at full size, while Auto and Minimum on the same PC get them a level smaller. On a Deck that doubles the long frame at every arrival that brings in the terrain (on this PR's Deck A/B, the Kokiri save load's longest frame 2,249 ms on main against 1,026 ms here, the Hyrule Field return after the Market 1,352 ms against 682 ms, medians), and the player has no menu row to change it.

Who has Custom with no preset behind it (memory_budget=0 or no such line): everyone whose options file comes from a build before 2026-11-11, when a first start still meant Custom with the defaults and memory_budget did not exist yet (Hookshot PR 1358, Hookshot PR 2187), and anyone who picks Custom on the Quality preset row. A file from before memory_budget with a preset on gets the preset's number when it is read; one with Custom stays at 0 for good, and nothing in the menu sets it. Of the 74 issues and pull requests here that quote memory_budget, 25 show memory_budget=0, 20 of them on Custom; three of those are on hardware the rule covers: issue 1304 (Ryzen 5 6600H's integrated GPU, 14 GB), issue 748 (GTX 1650) and issue 835 (GTX 1050).

How to reproduce

Seen on: Steam Deck OLED, SteamOS 3.9.5, RADV (AMD Custom GPU 0932 (RADV VANGOGH)), main @ 8e3dfde6e
Settings and switches: Quality preset Custom, longshot_options.ini with no memory_budget line (or memory_budget=0); 1280x720, Render resolution 50%, the game's own upscaler, sharpness 50
Steps: load a save in Kokiri Forest; go to the Market, then back to Hyrule Field
Expected: the terrain's two 1365x1365x90 ASTC arrays with their top level left out, as on Auto or Minimum on the same Deck: vk: texture 0x10a00ea600 1365x1365x1 x90 (NVN 0x8e, 852 MB): its 1 top level(s) left out (212 MB), 40 such lines a run
Actual: the arrays at full size, 214 MB each in the renderer's largest-textures list (vk: 214 MB: 0x10a00ea600 1365x1365x1 x90 levels 11 NVN 0x8e ASTC), one top level(s) left out line a run (a 6144x6144 texture), and the load and the Field return twice as long as with the trimming

What changed

Minimum's texture trimming on a small or shared GPU now goes by the memory tier the settings come from, and Custom with no preset behind it takes Auto (this PC)'s tier for this PC, as the Shadow resolution's Auto already does. Every preset still saves its own number as memory_budget, so a player who applied Low or higher keeps full-size textures; only Custom with none changes, and only where Auto would pick Minimum.

  • renderer: low_vram_texture_mips() in gpu/vk/vk_texture.cpp asks opts.preset == 1 || menu_memory_tier() == 1 (was opts.budget == 1). The size rule itself (integrated GPU with 16 GB of RAM or less, or a driver budget of 4.5 GiB or less) is unchanged.
  • menu: menu_memory_tier() in gpu/vk/vk_menu.cpp, declared in gpu/vk/vk_menu.h: memory_budget when set, else the preset's (a file with a preset and memory_budget=0), else Auto's tier for this PC (auto_choice.tier, chosen in menu_auto_for_gpu at the start, before any texture). Auto's tier is Minimum on every integrated GPU and handheld, on cards of 4.5 GB or less and on cards without mesh shaders (gpu/vk/auto_settings.h tier_of).
  • check: tests/test_low_vram_texture_mips.py cuts menu_memory_tier too, gives the fixture Auto's tier, and adds 20 cases for a Deck (14798 MB of RAM, 5872 MB allowed, Auto's tier Minimum) and for discrete 8 GB and 4 GB cards. It now runs every case and names all that fail, instead of stopping at the first.
  • docs: README.md (the low-VRAM mips paragraph), docs/development.md (a memory_budget row in the options file's table), docs/steam-deck-playbook.md (one bullet under Settings, and its line on what Auto picks on a Deck, which said Low and FSR 3.1: it is Minimum and the game's own upscaler, tier_of and choose in gpu/vk/auto_settings.h, as every Deck log says), and the defaults of RX_VK_LOW_VRAM_MIPS, RX_VK_TEX_MAX_DIM and RX_VK_TEX_SKIP_MB in gpu/vk/switches.def.
  • tested runs: five files under docs/tested/ (2026-11-17-textrim-deck-zeldaootr-*.md), one for each Deck run below.
  • deliberately unchanged: menu_shadow_res() (it already goes by memory_budget or Auto's tier; tests/test_oot_shadow.py checks its line), no options migration, no menu row.

Measurements

Verdict: on a Steam Deck OLED at a player's Custom rows with no memory_budget line, this PR halves the long frames at arrivals (Kokiri save load 2,249 → 1,026 ms, Field return after the Market 1,352 → 682 ms, medians of 2 runs each, interleaved), with standing fps the same (20.24 → 20.70, within the noise), no softer ground in the screenshots, and nothing written into the player's options file. RX_VK_LOW_VRAM_MIPS=0 gives main's numbers back. The check: 2 of its 61 cases fail on main, the two this PR changes, and all 61 pass here.

Baseline: the Deck ran this PR's renderer (only longshot_vk.so changes) packed on main @ 8e3dfde6e, against that main; this PR is now on main @ 544229a26. Of the 9 commits between them, one touches the files the rule lives in (gpu/vk/vk_texture.cpp, gpu/vk/vk_menu.cpp, gpu/vk/auto_settings.h): 7fd3e2ace, the fullscreen monitor row in vk_menu.cpp, with no line on the trimming, the presets, memory_budget or Auto's tier. The numbers hold for this base.

Hardware: Steam Deck OLED, SteamOS 3.9.5 build 20261023.100, Mesa 26.2.0-devel (5c65d4fc31), RADV; plugged in, headless, nothing else running; GPU clock held at a manual 1600 MHz before and after every run (vk: GPU clock: the driver's own: the GPU's power level was chosen (not auto): it stays (the power level: manual) in every log)
Scene: a child Kokiri Forest save; standing 45 s at the save, then 7 teleports (1 Field, 2 Lost Woods, 3 Market, 4 Field, 5 Lost Woods, 6 Market, 7 Field); 1280x720 output, Render resolution 50%, the game's own upscaler, sharpness 50, frame pacing off, frame generation off, Custom (quality_preset=0) with no memory_budget line; one shared shader cache, no preparation in any run
Method: the longest frame (ms) from 10 presents before each map: line to 10 s after it; standing fps and p99 over the 45 s sample; the arrays' upload from the a frame's uploads took line and the GPU-busy block after it (10 Hz). Order A B B A, then B0: tA-1 (main), tB-1, tB-2 (this PR), tA-2 (main), tB0-1 (this PR with RX_VK_LOW_VRAM_MIPS=0); the median of the two runs an arm
How to reproduce: the options above with no memory_budget line, a renderer-only build of each side on the same base, RX_VK_SLOW_LOG=100

At the player's rows (1280x720, 50%) Before: main @ 8e3dfde6e (tA-1 / tA-2) After: this PR @ 23eb8116d (tB-1 / tB-2) After, RX_VK_LOW_VRAM_MIPS=0: this PR @ 23eb8116d (tB0-1)
Kokiri save load, longest frame 2,292 / 2,205 ms (median 2,249) 1,008 / 1,044 ms (median 1,026) 2,252 ms
Field after the Market (arrival 4), longest frame 1,366 / 1,338 ms 709 / 685 ms 1,334 ms
Field after the Market (arrival 7), longest frame 1,375 / 1,334 ms 678 / 603 ms 1,396 ms
Field returns, median (4 arrivals an arm) 1,352 ms (1,334-1,375) 682 ms (603-709)
standing fps / p99 frame 20.44 / 69.1 ms; 20.03 / 70.2 ms (median 20.24 fps) 21.43 / 63.8 ms; 19.96 / 70.7 ms (median 20.70 fps) 19.80 / 72.6 ms
arrays' uploads (ms, GPU busy after it s) 92, 1.3; 352, 1.4; 302, 1.3 / 95, 2.3; 368, 1.4; 306, 1.5 240, 0.7; 245, 0.6 / 209, 0.7; 249, 0.5 96, 1.3; 305, 0.3; 383, 0.2
the terrain arrays 1365x1365x90 levels 11, 214 MB each 682x682x90 levels 10, 53 MB each 1365x1365x90 levels 11
top level(s) left out lines 1 / 1 40 / 40 1
memory_budget lines in the staged / saved options file; saved = staged 0 / 0; yes (both runs) 0 / 0; yes (both runs) 0 / 0; yes

The other arrivals (longest frame ms, arrivals 1 Field, 2 Lost Woods, 3 Market, 5 Lost Woods, 6 Market): tA-1 648 260 2,446 390 657; tA-2 549 228 739 285 631; tB-1 486 164 3,470 259 1,042; tB-2 547 181 670 172 548; tB0-1 567 230 3,512 243 731. The first Market arrival has a multi-second frame in some runs of every arm, main included (tA-1, tB-1, tB0-1 here; 2,484 ms on main and 4,505 ms on Auto in the earlier hand-set series on the same main): not this change. Apart from it, this PR's other arrivals are inside or under main's range except tB-1's arrival 6 (Market) (1,042 ms against main's 631-657).

Memory: the integrated GPU texture budget was 2,560 MB in every run. MemAvailable at its low point: main 1,325 / 1,393 MiB, this PR 1,436 / 1,400, B0 1,351. MemAvailable + SwapFree at that point: main 8,251 / 5,691 MiB, this PR 7,948 / 5,938, B0 5,139: this PR inside main's range. No kill (oom_kill delta 0, no earlyoom), no VK_ERROR, device lost, upload failure or amdgpu line, exit 0 in every run.

Picture: full-size crops of the ground, main (tA-1) above this PR (tB-1), are in this PR's screenshots comment: the Kokiri save's spot after the 45 s stand (the stone path), the Hyrule Field entrance 20 s after the first arrival (grass and rock), and the last Field return (where this PR kept its trimmed arrays and main made them again). In each, this PR is not softer; no missing, black, garbage or wrong texture; Link lit in both.

vk: integrated GPU texture budget: 2560 MB (system RAM 14 GB, driver allows 5872-5902 MB, its share for textures 2642-2656 MB, reserved 8 GB)
vk: Auto (this PC) would be: integrated GPU: Minimum; the game's own upscaler (...)
main:     vk:   214 MB: 0x10a00ea600 1365x1365x1 x90 levels 11 NVN 0x8e ASTC, ...
this PR:  vk: texture 0x10a00ea600 1365x1365x1 x90 (NVN 0x8e, 852 MB): its 1 top level(s) left out (212 MB)
this PR:  vk:   53 MB: 0x10a00ea600 682x682x1 x90 levels 10 NVN 0x8e ASTC, ...

The same setting by hand, before this PR: main @ 8e3dfde6e against the same main with memory_budget=1 added to the options file (what low_vram_texture_mips() sees on this PR for such a player on a Deck), same Deck, rows and route, order main, memory_budget=1, memory_budget=1, main: Kokiri load 2,253 / 2,443 → 1,049 / 1,050 ms, Field after the Market 1,328-1,441 → 648-675 ms, standing fps 20.46 / 20.58 → 20.38 / 21.23, no difference seen on the ground. At 1280x800, Render resolution 100% (one run with memory_budget=1, two without): load 2,164 / 2,221 → 1,056 ms, Field after the Market 1,334-1,392 → 711 / 755 ms. This PR's own runs match it.

Limits: two runs an arm (one with the switch off), runs of about 10 minutes, four areas (Kokiri Forest, Hyrule Field, the Lost Woods, the Market); a long session is not measured.

The check, on main's source (this PR's test commit, 821fcdcff) and on this PR:

test commit 821fcdcff (main's source):  FAIL 2 of 61 mip-policy configurations: deck-custom-no-budget, discrete-4gb-custom-no-budget
this PR @ 02844b622:                    PASS 61 mip-policy configurations

What it costs where it was not measured

  • Other integrated GPUs with 16 GB of RAM or less (AMD 680M/780M/880M laptops and handhelds, Intel Iris Xe and UHD, on Custom with no preset): ASTC textures wider than 1024 texels and over 8 MB decoded lose their top level(s), as on Auto or Minimum there today. Not run on any of them; the picture was judged on a Deck at 1280x800 and below only, at three spots. On a large screen (1440p and up) a 682-texel terrain layer may be visibly softer up close.
  • Cards of 4.5 GB or less (GTX 1650, GTX 1050, RX 6500 XT ...) on Custom with no preset: the same trimming, which Minimum and Auto there already apply. Not measured on any discrete card.
  • Everyone else is unchanged: an integrated GPU with more than 16 GB of RAM and a driver budget over 4.5 GiB, every card over 4.5 GB, and anyone whose memory_budget is a preset's (Low and up keep full size; Minimum and Auto at Minimum were trimmed already).

Flags and settings

No new switch or row. The meaning of memory_budget=0 on Custom changes: from "no trimming" to "Auto's tier for this PC".

Flag What it is Before this PR After this PR Effect Helps / doesn't help / untested Recommendation
memory_budget=0 with quality_preset=0 (ini, no row) Custom with no preset behind it Minimum's trimming off Minimum's trimming where Auto picks Minimum (integrated GPU with 16 GB or less, or a driver budget of 4.5 GiB or less) the largest ASTC textures one level smaller helps on a Steam Deck OLED (arrival stalls halved); untested on other integrated GPUs and small cards on for everyone (the default)
RX_VK_LOW_VRAM_MIPS=0 the existing off switch turns the rule off the same, now also for this case: the way back to full size (measured: tB0-1 equals main) full-size textures n/a unchanged

The way back for a player who wants full-size textures: apply Low (6GB) or a higher preset (each saves its own memory_budget, which this PR leaves alone), then change rows as before; or memory_budget=2 in longshot_options.ini; or RX_VK_LOW_VRAM_MIPS=0. RX_VK_TEX_MAX_DIM=2048 alone is not a way back: it spares the 1365-texel arrays but the 8 MB threshold stays. The check covers each: deck-custom-after-low and deck-low (full size), deck-custom-no-budget-switch-off (full size).

Testing

Tested: in the game on a Steam Deck OLED (SteamOS 3.9.5, RADV): this PR's renderer on main @ 8e3dfde6e against that main, Custom with no memory_budget line, the arrival route above, A B B A plus one run with RX_VK_LOW_VRAM_MIPS=0 (Measurements); the options file checked after every run, the ground compared at three spots. python -I -B tests/run_all.py --changed forge/main on Linux, with the Vulkan headers found: 134 passed, 18 failed, 1 skipped (nx2/test_bc_storage_views.py, which needs a Windows Vulkan device). The same checks on main @ 544229a26 fail the same 18: test_bug_report, test_bug_report_defaults, test_crt_options, test_damage_debug_menu, test_framegen_preset, test_hud_layout_row, test_linux_pressure, test_parallel_init_order, test_readback_timeout_source, test_rumble_menu, test_staging_burst, test_switch_table (RX_VK_PGO_FILE has a row and nothing reads it), test_target_image_pool, test_tested_configurations (four docs/tested/ files already on main with more than one row; this PR's five files read clean on their own), test_upscaler_round_trip, test_upscaler_rows, test_vk_occlusion_queries, test_walk_key. test_low_vram_texture_mips (fails on the test commit alone, passes here), test_oot_shadow, test_options_budget_once and test_readme_menu_rows pass.

Not tested: Windows; other integrated GPUs and 4 GB cards (what it costs there is above); picture quality beyond three spots on a Deck at 1280x720 (and at 1280x800 by hand on main); a session longer than about 10 minutes.

Must be tested:

  • An AMD or Intel integrated GPU with 16 GB of RAM or less on Windows, on Custom with no memory_budget (Test Farm: @Beanstalk windows, amd or intel integrated: Custom with memory_budget removed from longshot_options.ini, Kokiri Forest and Hyrule Field, expecting the "top level(s) left out" lines and no visible blur on the ground at the PC's own resolution).

Risks

What could break: textures look softer up close for Custom players with no preset on integrated GPUs with 16 GB or less and on cards of 4.5 GB or less, most on a large screen. Nothing else reads menu_memory_tier().

Turning it off: RX_VK_LOW_VRAM_MIPS=0; for one player, applying Low or a higher preset. Or revert the commit.

Compatibility: longshot_options.ini is read and written as before (no line added, no migration; on the Deck every run's saved file equals the one it started with). The shader and pipeline caches are untouched. MKWVK_API_VERSION is unchanged (vk_api.h untouched). Textures over the limits are made smaller at their creation, so a player on the affected hardware sees the change at the next start.

Issues

See #1304 (Custom, memory_budget=0, an integrated GPU with 14 GB). The rule's own PR: #404, which made it go by Minimum's budget (memory_budget=1) so the Debug tab's button would get it on Custom; the reporter it was for ran Custom too.

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).
  • Tested on my own PC where it runs (in the game, for a change the game runs), as Testing's Tested says; what
    can't be run by hand is in Testing's Not testable by hand, with why.
  • Measurements has a verdict, or one line saying why there is nothing to measure.
  • Nothing gets worse that I know of: any cost (speed, latency, memory, a setup that worked before) is measured and
    in Risks.
  • 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.
  • Screenshots of the same spot, captioned like the Measurements columns, for a change that shows on screen.
  • A file in docs/tested/ for each new measured run (format in docs/tested-configurations.md).
  • 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.
  • Docs updated.
**Type:** perf · **Risk:** low · **Tested on:** Steam Deck OLED (SteamOS 3.9.5, RADV) · **Needs:** Windows, an AMD or Intel integrated GPU (renderer only) ## Why On a Steam Deck, and other PCs with an integrated GPU and 16 GB of RAM or less, a player whose Quality preset reads Custom with no preset behind it gets the largest textures at full size, while Auto and Minimum on the same PC get them a level smaller. On a Deck that doubles the long frame at every arrival that brings in the terrain (on this PR's Deck A/B, the Kokiri save load's longest frame 2,249 ms on main against 1,026 ms here, the Hyrule Field return after the Market 1,352 ms against 682 ms, medians), and the player has no menu row to change it. Who has Custom with no preset behind it (`memory_budget=0` or no such line): everyone whose options file comes from a build before 2026-11-11, when a first start still meant Custom with the defaults and `memory_budget` did not exist yet ([Hookshot PR 1358](https://github.com/NotRexed/Hookshot/pull/1358), [Hookshot PR 2187](https://github.com/NotRexed/Hookshot/pull/2187)), and anyone who picks Custom on the Quality preset row. A file from before `memory_budget` with a preset on gets the preset's number when it is read; one with Custom stays at 0 for good, and nothing in the menu sets it. Of the 74 issues and pull requests here that quote `memory_budget`, 25 show `memory_budget=0`, 20 of them on Custom; three of those are on hardware the rule covers: [issue 1304](https://git.magicbean.dev/MagicBeanDev/Longshot/issues/1304) (Ryzen 5 6600H's integrated GPU, 14 GB), [issue 748](https://git.magicbean.dev/MagicBeanDev/Longshot/issues/748) (GTX 1650) and [issue 835](https://git.magicbean.dev/MagicBeanDev/Longshot/issues/835) (GTX 1050). ## How to reproduce **Seen on:** Steam Deck OLED, SteamOS 3.9.5, RADV (`AMD Custom GPU 0932 (RADV VANGOGH)`), main @ 8e3dfde6e **Settings and switches:** Quality preset Custom, `longshot_options.ini` with no `memory_budget` line (or `memory_budget=0`); 1280x720, Render resolution 50%, the game's own upscaler, sharpness 50 **Steps:** load a save in Kokiri Forest; go to the Market, then back to Hyrule Field **Expected:** the terrain's two 1365x1365x90 ASTC arrays with their top level left out, as on Auto or Minimum on the same Deck: `vk: texture 0x10a00ea600 1365x1365x1 x90 (NVN 0x8e, 852 MB): its 1 top level(s) left out (212 MB)`, 40 such lines a run **Actual:** the arrays at full size, 214 MB each in the renderer's largest-textures list (`vk: 214 MB: 0x10a00ea600 1365x1365x1 x90 levels 11 NVN 0x8e ASTC`), one `top level(s) left out` line a run (a 6144x6144 texture), and the load and the Field return twice as long as with the trimming ## What changed Minimum's texture trimming on a small or shared GPU now goes by the memory tier the settings come from, and Custom with no preset behind it takes Auto (this PC)'s tier for this PC, as the Shadow resolution's Auto already does. Every preset still saves its own number as `memory_budget`, so a player who applied Low or higher keeps full-size textures; only Custom with none changes, and only where Auto would pick Minimum. - renderer: `low_vram_texture_mips()` in `gpu/vk/vk_texture.cpp` asks `opts.preset == 1 || menu_memory_tier() == 1` (was `opts.budget == 1`). The size rule itself (integrated GPU with 16 GB of RAM or less, or a driver budget of 4.5 GiB or less) is unchanged. - menu: `menu_memory_tier()` in `gpu/vk/vk_menu.cpp`, declared in `gpu/vk/vk_menu.h`: `memory_budget` when set, else the preset's (a file with a preset and `memory_budget=0`), else Auto's tier for this PC (`auto_choice.tier`, chosen in `menu_auto_for_gpu` at the start, before any texture). Auto's tier is Minimum on every integrated GPU and handheld, on cards of 4.5 GB or less and on cards without mesh shaders (`gpu/vk/auto_settings.h` `tier_of`). - check: `tests/test_low_vram_texture_mips.py` cuts `menu_memory_tier` too, gives the fixture Auto's tier, and adds 20 cases for a Deck (14798 MB of RAM, 5872 MB allowed, Auto's tier Minimum) and for discrete 8 GB and 4 GB cards. It now runs every case and names all that fail, instead of stopping at the first. - docs: `README.md` (the low-VRAM mips paragraph), `docs/development.md` (a `memory_budget` row in the options file's table), `docs/steam-deck-playbook.md` (one bullet under Settings, and its line on what Auto picks on a Deck, which said Low and FSR 3.1: it is Minimum and the game's own upscaler, `tier_of` and `choose` in `gpu/vk/auto_settings.h`, as every Deck log says), and the defaults of `RX_VK_LOW_VRAM_MIPS`, `RX_VK_TEX_MAX_DIM` and `RX_VK_TEX_SKIP_MB` in `gpu/vk/switches.def`. - tested runs: five files under `docs/tested/` (`2026-11-17-textrim-deck-zeldaootr-*.md`), one for each Deck run below. - deliberately unchanged: `menu_shadow_res()` (it already goes by `memory_budget` or Auto's tier; `tests/test_oot_shadow.py` checks its line), no options migration, no menu row. ## Measurements **Verdict:** on a Steam Deck OLED at a player's Custom rows with no `memory_budget` line, this PR halves the long frames at arrivals (Kokiri save load 2,249 → 1,026 ms, Field return after the Market 1,352 → 682 ms, medians of 2 runs each, interleaved), with standing fps the same (20.24 → 20.70, within the noise), no softer ground in the screenshots, and nothing written into the player's options file. `RX_VK_LOW_VRAM_MIPS=0` gives main's numbers back. The check: 2 of its 61 cases fail on main, the two this PR changes, and all 61 pass here. Baseline: the Deck ran this PR's renderer (only `longshot_vk.so` changes) packed on main @ 8e3dfde6e, against that main; this PR is now on main @ 544229a26. Of the 9 commits between them, one touches the files the rule lives in (`gpu/vk/vk_texture.cpp`, `gpu/vk/vk_menu.cpp`, `gpu/vk/auto_settings.h`): 7fd3e2ace, the fullscreen monitor row in `vk_menu.cpp`, with no line on the trimming, the presets, `memory_budget` or Auto's tier. The numbers hold for this base. Hardware: Steam Deck OLED, SteamOS 3.9.5 build 20261023.100, Mesa 26.2.0-devel (5c65d4fc31), RADV; plugged in, headless, nothing else running; GPU clock held at a manual 1600 MHz before and after every run (`vk: GPU clock: the driver's own: the GPU's power level was chosen (not auto): it stays (the power level: manual)` in every log) Scene: a child Kokiri Forest save; standing 45 s at the save, then 7 teleports (1 Field, 2 Lost Woods, 3 Market, 4 Field, 5 Lost Woods, 6 Market, 7 Field); 1280x720 output, Render resolution 50%, the game's own upscaler, sharpness 50, frame pacing off, frame generation off, Custom (`quality_preset=0`) with no `memory_budget` line; one shared shader cache, no preparation in any run Method: the longest frame (ms) from 10 presents before each `map:` line to 10 s after it; standing fps and p99 over the 45 s sample; the arrays' upload from the `a frame's uploads took` line and the GPU-busy block after it (10 Hz). Order A B B A, then B0: tA-1 (main), tB-1, tB-2 (this PR), tA-2 (main), tB0-1 (this PR with `RX_VK_LOW_VRAM_MIPS=0`); the median of the two runs an arm How to reproduce: the options above with no `memory_budget` line, a renderer-only build of each side on the same base, `RX_VK_SLOW_LOG=100` | At the player's rows (1280x720, 50%) | Before: main @ 8e3dfde6e (tA-1 / tA-2) | After: this PR @ 23eb8116d (tB-1 / tB-2) | After, `RX_VK_LOW_VRAM_MIPS=0`: this PR @ 23eb8116d (tB0-1) | |---|---|---|---| | Kokiri save load, longest frame | 2,292 / 2,205 ms (median 2,249) | **1,008 / 1,044 ms (median 1,026)** | 2,252 ms | | Field after the Market (arrival 4), longest frame | 1,366 / 1,338 ms | **709 / 685 ms** | 1,334 ms | | Field after the Market (arrival 7), longest frame | 1,375 / 1,334 ms | **678 / 603 ms** | 1,396 ms | | Field returns, median (4 arrivals an arm) | 1,352 ms (1,334-1,375) | **682 ms (603-709)** | | | standing fps / p99 frame | 20.44 / 69.1 ms; 20.03 / 70.2 ms (median 20.24 fps) | 21.43 / 63.8 ms; 19.96 / 70.7 ms (median 20.70 fps) | 19.80 / 72.6 ms | | arrays' uploads (ms, GPU busy after it s) | 92, 1.3; 352, 1.4; 302, 1.3 / 95, 2.3; 368, 1.4; 306, 1.5 | 240, 0.7; 245, 0.6 / 209, 0.7; 249, 0.5 | 96, 1.3; 305, 0.3; 383, 0.2 | | the terrain arrays | 1365x1365x90 levels 11, 214 MB each | 682x682x90 levels 10, 53 MB each | 1365x1365x90 levels 11 | | `top level(s) left out` lines | 1 / 1 | 40 / 40 | 1 | | `memory_budget` lines in the staged / saved options file; saved = staged | 0 / 0; yes (both runs) | 0 / 0; yes (both runs) | 0 / 0; yes | The other arrivals (longest frame ms, arrivals 1 Field, 2 Lost Woods, 3 Market, 5 Lost Woods, 6 Market): tA-1 648 260 2,446 390 657; tA-2 549 228 739 285 631; tB-1 486 164 3,470 259 1,042; tB-2 547 181 670 172 548; tB0-1 567 230 3,512 243 731. The first Market arrival has a multi-second frame in some runs of every arm, main included (tA-1, tB-1, tB0-1 here; 2,484 ms on main and 4,505 ms on Auto in the earlier hand-set series on the same main): not this change. Apart from it, this PR's other arrivals are inside or under main's range except tB-1's arrival 6 (Market) (1,042 ms against main's 631-657). Memory: the integrated GPU texture budget was 2,560 MB in every run. MemAvailable at its low point: main 1,325 / 1,393 MiB, this PR 1,436 / 1,400, B0 1,351. MemAvailable + SwapFree at that point: main 8,251 / 5,691 MiB, this PR 7,948 / 5,938, B0 5,139: this PR inside main's range. No kill (`oom_kill` delta 0, no earlyoom), no `VK_ERROR`, device lost, upload failure or amdgpu line, exit 0 in every run. Picture: full-size crops of the ground, main (tA-1) above this PR (tB-1), are in this PR's screenshots comment: the Kokiri save's spot after the 45 s stand (the stone path), the Hyrule Field entrance 20 s after the first arrival (grass and rock), and the last Field return (where this PR kept its trimmed arrays and main made them again). In each, this PR is not softer; no missing, black, garbage or wrong texture; Link lit in both. ``` vk: integrated GPU texture budget: 2560 MB (system RAM 14 GB, driver allows 5872-5902 MB, its share for textures 2642-2656 MB, reserved 8 GB) vk: Auto (this PC) would be: integrated GPU: Minimum; the game's own upscaler (...) main: vk: 214 MB: 0x10a00ea600 1365x1365x1 x90 levels 11 NVN 0x8e ASTC, ... this PR: vk: texture 0x10a00ea600 1365x1365x1 x90 (NVN 0x8e, 852 MB): its 1 top level(s) left out (212 MB) this PR: vk: 53 MB: 0x10a00ea600 682x682x1 x90 levels 10 NVN 0x8e ASTC, ... ``` The same setting by hand, before this PR: main @ 8e3dfde6e against the same main with `memory_budget=1` added to the options file (what `low_vram_texture_mips()` sees on this PR for such a player on a Deck), same Deck, rows and route, order main, `memory_budget=1`, `memory_budget=1`, main: Kokiri load 2,253 / 2,443 → 1,049 / 1,050 ms, Field after the Market 1,328-1,441 → 648-675 ms, standing fps 20.46 / 20.58 → 20.38 / 21.23, no difference seen on the ground. At 1280x800, Render resolution 100% (one run with `memory_budget=1`, two without): load 2,164 / 2,221 → 1,056 ms, Field after the Market 1,334-1,392 → 711 / 755 ms. This PR's own runs match it. Limits: two runs an arm (one with the switch off), runs of about 10 minutes, four areas (Kokiri Forest, Hyrule Field, the Lost Woods, the Market); a long session is not measured. The check, on main's source (this PR's test commit, 821fcdcff) and on this PR: ``` test commit 821fcdcff (main's source): FAIL 2 of 61 mip-policy configurations: deck-custom-no-budget, discrete-4gb-custom-no-budget this PR @ 02844b622: PASS 61 mip-policy configurations ``` ### What it costs where it was not measured - **Other integrated GPUs with 16 GB of RAM or less** (AMD 680M/780M/880M laptops and handhelds, Intel Iris Xe and UHD, on Custom with no preset): ASTC textures wider than 1024 texels and over 8 MB decoded lose their top level(s), as on Auto or Minimum there today. Not run on any of them; the picture was judged on a Deck at 1280x800 and below only, at three spots. On a large screen (1440p and up) a 682-texel terrain layer may be visibly softer up close. - **Cards of 4.5 GB or less** (GTX 1650, GTX 1050, RX 6500 XT ...) on Custom with no preset: the same trimming, which Minimum and Auto there already apply. Not measured on any discrete card. - **Everyone else** is unchanged: an integrated GPU with more than 16 GB of RAM and a driver budget over 4.5 GiB, every card over 4.5 GB, and anyone whose `memory_budget` is a preset's (Low and up keep full size; Minimum and Auto at Minimum were trimmed already). ### Flags and settings No new switch or row. The meaning of `memory_budget=0` on Custom changes: from "no trimming" to "Auto's tier for this PC". | Flag | What it is | Before this PR | After this PR | Effect | Helps / doesn't help / untested | Recommendation | |---|---|---|---|---|---|---| | `memory_budget=0` with `quality_preset=0` (ini, no row) | Custom with no preset behind it | Minimum's trimming off | Minimum's trimming where Auto picks Minimum (integrated GPU with 16 GB or less, or a driver budget of 4.5 GiB or less) | the largest ASTC textures one level smaller | helps on a Steam Deck OLED (arrival stalls halved); untested on other integrated GPUs and small cards | on for everyone (the default) | | `RX_VK_LOW_VRAM_MIPS=0` | the existing off switch | turns the rule off | the same, now also for this case: the way back to full size (measured: tB0-1 equals main) | full-size textures | n/a | unchanged | The way back for a player who wants full-size textures: apply Low (6GB) or a higher preset (each saves its own `memory_budget`, which this PR leaves alone), then change rows as before; or `memory_budget=2` in `longshot_options.ini`; or `RX_VK_LOW_VRAM_MIPS=0`. `RX_VK_TEX_MAX_DIM=2048` alone is not a way back: it spares the 1365-texel arrays but the 8 MB threshold stays. The check covers each: `deck-custom-after-low` and `deck-low` (full size), `deck-custom-no-budget-switch-off` (full size). ## Testing **Tested:** in the game on a Steam Deck OLED (SteamOS 3.9.5, RADV): this PR's renderer on main @ 8e3dfde6e against that main, Custom with no `memory_budget` line, the arrival route above, A B B A plus one run with `RX_VK_LOW_VRAM_MIPS=0` (Measurements); the options file checked after every run, the ground compared at three spots. `python -I -B tests/run_all.py --changed forge/main` on Linux, with the Vulkan headers found: 134 passed, 18 failed, 1 skipped (`nx2/test_bc_storage_views.py`, which needs a Windows Vulkan device). The same checks on main @ 544229a26 fail the same 18: `test_bug_report`, `test_bug_report_defaults`, `test_crt_options`, `test_damage_debug_menu`, `test_framegen_preset`, `test_hud_layout_row`, `test_linux_pressure`, `test_parallel_init_order`, `test_readback_timeout_source`, `test_rumble_menu`, `test_staging_burst`, `test_switch_table` (`RX_VK_PGO_FILE has a row and nothing reads it`), `test_target_image_pool`, `test_tested_configurations` (four `docs/tested/` files already on main with more than one row; this PR's five files read clean on their own), `test_upscaler_round_trip`, `test_upscaler_rows`, `test_vk_occlusion_queries`, `test_walk_key`. `test_low_vram_texture_mips` (fails on the test commit alone, passes here), `test_oot_shadow`, `test_options_budget_once` and `test_readme_menu_rows` pass. **Not tested:** Windows; other integrated GPUs and 4 GB cards (what it costs there is above); picture quality beyond three spots on a Deck at 1280x720 (and at 1280x800 by hand on main); a session longer than about 10 minutes. **Must be tested:** - An AMD or Intel integrated GPU with 16 GB of RAM or less on Windows, on Custom with no `memory_budget` (Test Farm: `@Beanstalk windows, amd or intel integrated: Custom with memory_budget removed from longshot_options.ini, Kokiri Forest and Hyrule Field, expecting the "top level(s) left out" lines and no visible blur on the ground at the PC's own resolution`). ## Risks **What could break:** textures look softer up close for Custom players with no preset on integrated GPUs with 16 GB or less and on cards of 4.5 GB or less, most on a large screen. Nothing else reads `menu_memory_tier()`. **Turning it off:** `RX_VK_LOW_VRAM_MIPS=0`; for one player, applying Low or a higher preset. Or revert the commit. **Compatibility:** `longshot_options.ini` is read and written as before (no line added, no migration; on the Deck every run's saved file equals the one it started with). The shader and pipeline caches are untouched. `MKWVK_API_VERSION` is unchanged (`vk_api.h` untouched). Textures over the limits are made smaller at their creation, so a player on the affected hardware sees the change at the next start. ## Issues See https://git.magicbean.dev/MagicBeanDev/Longshot/issues/1304 (Custom, `memory_budget=0`, an integrated GPU with 14 GB). The rule's own PR: https://git.magicbean.dev/MagicBeanDev/Longshot/pulls/404, which made it go by Minimum's budget (`memory_budget=1`) so the Debug tab's button would get it on Custom; the reporter it was for ran Custom too. ## 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] Tested on my own PC where it runs (in the game, for a change the game runs), as Testing's Tested says; what can't be run by hand is in Testing's Not testable by hand, with why. - [x] Measurements has a verdict, or one line saying why there is nothing to measure. - [x] Nothing gets worse that I know of: any cost (speed, latency, memory, a setup that worked before) is measured and in Risks. - [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] Screenshots of the same spot, captioned like the Measurements columns, for a change that shows on screen. - [x] A file in `docs/tested/` for each new measured run (format in `docs/tested-configurations.md`). - [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. - [x] Docs updated.
A Steam Deck on Custom with no `memory_budget` (an options file from before it, or Custom chosen on the preset row) drew the terrain's 1365x1365x90 ASTC arrays at full size, where Auto and Minimum leave out their top level. The check now gives the fixture Auto (this PC)'s tier and expects Custom with none to go by it; it fails on main for that case on the Deck and on a 4 GB card, and every other case passes.

Assisted-by: Claude
`low_vram_texture_mips` went by `memory_budget == 1`, and Custom with `memory_budget=0` (an options file from before it, or Custom chosen on the preset row) left the terrain's 1365x1365x90 arrays at full size on a Steam Deck. It now goes by `menu_memory_tier()`: `memory_budget`, else the preset's, else Auto (this PC)'s tier for this PC, as the Shadow resolution's Auto already does. Every preset still saves its own number, so Low and up keep full size; `RX_VK_LOW_VRAM_MIPS=0` turns the rule off as before.

Assisted-by: Claude
docs(tested): the Deck A/B of Custom with no memory_budget going by Auto's tier, five runs
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
Website / Website on Cloudflare (pull_request_target) Has been skipped
beanstalk/approval waiting for a BigBean's 👍 on the request
PR description / Description follows the template (pull_request_target) Successful in 9s
02844b622f
Steam Deck OLED, main @ 8e3dfde6e against the same main with this branch's renderer, interleaved A B B A, then one run
with `RX_VK_LOW_VRAM_MIPS=0`.

Assisted-by: Claude
Author
Contributor

Tested in game: Steam Deck OLED (SteamOS 3.9.5, RADV), this PR's renderer on main @ 8e3dfde6e against that main, Custom with no memory_budget line at 1280x720 / 50%, A B B A plus a run with RX_VK_LOW_VRAM_MIPS=0: the terrain arrays trimmed to 682x682x90, the Kokiri save load's longest frame 1,026 ms against 2,249 and the Field return after the Market 682 ms against 1,352 (medians), standing fps the same, the ground not softer, the options file unchanged, and the switch-off run equal to main.

Tested in game: Steam Deck OLED (SteamOS 3.9.5, RADV), this PR's renderer on main @ 8e3dfde6e against that main, Custom with no memory_budget line at 1280x720 / 50%, A B B A plus a run with RX_VK_LOW_VRAM_MIPS=0: the terrain arrays trimmed to 682x682x90, the Kokiri save load's longest frame 1,026 ms against 2,249 and the Field return after the Market 682 ms against 1,352 (medians), standing fps the same, the ground not softer, the options file unchanged, and the switch-off run equal to main.
Author
Contributor

Screenshots: full-size crops of the ground on a Steam Deck OLED, 1280x720, Render resolution 50%, the game's own upscaler, Custom with no memory_budget line. In each, the top half is Before: main @ 8e3dfde6e (tA-1) and the bottom half is After: this PR @ 23eb8116d (tB-1).

Kokiri Forest, the save's spot after the 45 s stand (the stone path). Top: Before: main @ 8e3dfde6e (tA-1). Bottom: After: this PR @ 23eb8116d (tB-1). Not softer.

Hyrule Field entrance, 20 s after the first arrival (grass and the rock on the right; the fog drifts by itself). Top: Before: main @ 8e3dfde6e (tA-1). Bottom: After: this PR @ 23eb8116d (tB-1). Not softer.

Hyrule Field, the last return (arrival 7), where this PR kept its trimmed arrays and main made them again. Top: Before: main @ 8e3dfde6e (tA-1). Bottom: After: this PR @ 23eb8116d (tB-1). Not softer; Link lit in both.

Screenshots: full-size crops of the ground on a Steam Deck OLED, 1280x720, Render resolution 50%, the game's own upscaler, Custom with no `memory_budget` line. In each, the top half is Before: main @ 8e3dfde6e (tA-1) and the bottom half is After: this PR @ 23eb8116d (tB-1). ![Kokiri Forest, the save's spot after the 45 s stand (the stone path). Top: Before: main @ 8e3dfde6e (tA-1). Bottom: After: this PR @ 23eb8116d (tB-1). Not softer.](https://git.magicbean.dev/attachments/e8c5d291-c6a8-47a6-b7b3-3a56d074b8a0) ![Hyrule Field entrance, 20 s after the first arrival (grass and the rock on the right; the fog drifts by itself). Top: Before: main @ 8e3dfde6e (tA-1). Bottom: After: this PR @ 23eb8116d (tB-1). Not softer.](https://git.magicbean.dev/attachments/a8204be5-a875-47eb-82fb-62e0c222ab03) ![Hyrule Field, the last return (arrival 7), where this PR kept its trimmed arrays and main made them again. Top: Before: main @ 8e3dfde6e (tA-1). Bottom: After: this PR @ 23eb8116d (tB-1). Not softer; Link lit in both.](https://git.magicbean.dev/attachments/192b6f85-0e0c-426e-b1b8-de076b679e84)
zeldaootr changed title from WIP: perf(vk): Custom with no preset behind it trims the large textures where Auto would pick Minimum to perf(vk): Custom with no preset behind it trims the large textures where Auto would pick Minimum 2026-11-17 09:49:38 +00:00
Collaborator

Possibly related, for context:

  • issue #586 Idea: Smaller Texture Size for 4GB VRAM — Requests smaller textures on 4 GB GPUs; this implements mip trimming where Auto selects Minimum.
  • PR #223 fix(vk): give memory back under Linux memory pressure and after the precompile — Merged Linux pressure work also changes texture budgeting for integrated GPUs, but not preset-based mip trimming.
Possibly related, for context: - issue #586 Idea: Smaller Texture Size for 4GB VRAM — Requests smaller textures on 4 GB GPUs; this implements mip trimming where Auto selects Minimum. - PR #223 fix(vk): give memory back under Linux memory pressure and after the precompile — Merged Linux pressure work also changes texture budgeting for integrated GPUs, but not preset-based mip trimming.
TrashPanda left a comment

Custom with no preset behind it now trims the large textures where Auto would pick Minimum. I read head 02844b622. It applies onto current main. The Windows integrated-GPU run it still names is open, so this is not an approval.

menu_memory_tier uses memory_budget when it is set, otherwise the preset's, otherwise Auto's tier for this PC. The mip rule still requires an integrated GPU with 16 GB of RAM or less, or a driver budget of 4.5 GiB or less, and it still trims only at tier 1. A Low or higher preset keeps full-size textures. RX_VK_LOW_VRAM_MIPS=0 turns the rule off. Auto's choice is filled when the card is known, and that function does not rewrite a Custom player's budget. On a Deck, Auto's tier is Minimum and the upscaler is the game's own. The played renderer is 23eb8116; the tip adds the measured rows. On a Deck OLED at Custom with no memory_budget line, the terrain arrays drop their top level and the long arrival frames are about half, with the ground not softer. Must be tested still asks for an AMD or Intel integrated GPU on Windows, at that PC's own resolution.

Custom with no preset behind it now trims the large textures where Auto would pick Minimum. I read head `02844b622`. It applies onto current main. The Windows integrated-GPU run it still names is open, so this is not an approval. `menu_memory_tier` uses `memory_budget` when it is set, otherwise the preset's, otherwise Auto's tier for this PC. The mip rule still requires an integrated GPU with 16 GB of RAM or less, or a driver budget of 4.5 GiB or less, and it still trims only at tier 1. A Low or higher preset keeps full-size textures. `RX_VK_LOW_VRAM_MIPS=0` turns the rule off. Auto's choice is filled when the card is known, and that function does not rewrite a Custom player's budget. On a Deck, Auto's tier is Minimum and the upscaler is the game's own. The played renderer is `23eb8116`; the tip adds the measured rows. On a Deck OLED at Custom with no `memory_budget` line, the terrain arrays drop their top level and the long arrival frames are about half, with the ground not softer. Must be tested still asks for an AMD or Intel integrated GPU on Windows, at that PC's own resolution.
Author
Contributor

@Beanstalk windows, amd or intel integrated: Custom with memory_budget removed from longshot_options.ini, Kokiri Forest and Hyrule Field, expecting the "top level(s) left out" lines and no visible blur on the ground at the PC's own resolution

@Beanstalk windows, amd or intel integrated: Custom with memory_budget removed from longshot_options.ini, Kokiri Forest and Hyrule Field, expecting the "top level(s) left out" lines and no visible blur on the ground at the PC's own resolution
Member

@zeldaootr only members of BigBeans can start the farm. One of them can approve this request by reacting 👍 to it or to this comment.

@zeldaootr only members of `BigBeans` can start the farm. One of them can approve this request by reacting 👍 to it or to this comment.
Owner

Brought up to the ready-for-review standard (#1454): the checklist's Everyone list has two new boxes, added here from what this PR's description and comments show (please check they match what you know).

  • Tested on my own PC: ticked: Testing's Tested: the author's own in-game run on a Steam Deck OLED, SteamOS 3.9.5, RADV.
  • Nothing gets worse that I know of: ticked: Measurements show standing fps unchanged on the Deck, and the softer textures on affected GPUs are named in Risks.
Brought up to the [ready-for-review standard](https://git.magicbean.dev/MagicBeanDev/Longshot/src/branch/main/CONTRIBUTING.md#ready-for-review-out-of-wip) (#1454): the checklist's Everyone list has two new boxes, added here from what this PR's description and comments show (please check they match what you know). - *Tested on my own PC*: ticked: Testing's Tested: the author's own in-game run on a Steam Deck OLED, SteamOS 3.9.5, RADV. - *Nothing gets worse that I know of*: ticked: Measurements show standing fps unchanged on the Deck, and the softer textures on affected GPUs are named in Risks.
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
Website / Website on Cloudflare (pull_request_target) Has been skipped
beanstalk/approval waiting for a BigBean's 👍 on the request
PR description / Description follows the template (pull_request_target) Successful in 9s
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 'vk-texture-trim-auto-tier:zeldaootr-vk-texture-trim-auto-tier'
git switch 'zeldaootr-vk-texture-trim-auto-tier'
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
5 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!1388
No description provided.