docs(tested): RX 6800 XT runs of the mesh-only fallback on v3.0.0 #1716

Closed
GrimVisage wants to merge 1 commit from GrimVisage/Longshot:docs/tested-rdna2-mesh-only-6800xt into main
Contributor

Type: docs · Risk: low · Tested on: Windows 11, RX 6800 XT · Needs: none

TL;DR

On RX 6800 XT cards on Windows, the game used to hang a few minutes in at Saria's stump in Kokiri Forest. #1650 fixed that and shipped in v3.0.0. This PR records the RX 6800 XT retest that #1650 asked for. Two runs on v3.0.0 with default settings, one with a fresh shader cache and one warm, had no hang, no device loss and full foliage.

Breakdown

  • Who it helps: anyone checking whether RX 6000 cards on Windows have been tested on v3.0.0.
  • What was wrong: nothing in the code; #1650's hardware retest wasn't recorded in the tested-configurations catalogue.
  • What changes: two rows in docs/tested/, one per run.
  • What does not change: the game, the frozen table, every other docs file.
  • How it was checked: tests/test_tested_configurations.py passes; the full suite's results are under Testing.
  • What is still open: #1239's reporter retesting on their own PC (asked on the issue).
  • Risk: low: two docs rows.

Why

#1650's Must be tested item was a Windows RX 6800 XT run of the patched build at the #1239 camera spot, with a warm-cache repeat and frame time and VRAM. That run is done (results comment: #1650 (comment)), and docs/tested/ is where a measured run goes (CONTRIBUTING.md, docs/workflow.md).

What changed

Two run files, following docs/tested/README.md:

  • docs/tested/2026-11-18-rdna2-mesh-only-fallback-grimvisage-run01.md: cold program cache.
  • docs/tested/2026-11-18-rdna2-mesh-only-fallback-grimvisage-run02.md: warm program cache.

Measurements

Nothing to measure: docs only. No game code, build, loading, cache, memory or tool changes, so frame time, build time and size, load time, RAM and VRAM can't be affected. The runs' own numbers are in the rows and in the #1650 comment linked above, with the log lines.

Flags and settings

None

Testing

Tested: on main 444f8e49 (this branch's base): python -I -B tests/test_tested_configurations.py: OK. python -I -B tests/run_all.py (Linux, no Vulkan headers here): this branch 663 passed, 39 failed, 123 skipped; main 47430e81 659 passed, 43 failed, 123 skipped. The same 37 fail on both: test_bug_report_defaults, test_capture_read_once, test_crt_options, test_damage_debug_menu, test_dev_packs, test_discover, test_display_startup_failure, test_dlss_feature_size, test_failed_compile_keeps_objects, test_guest_imported, test_high_fps_fixes, test_host_guest_writes, test_hud_layout_row, test_invalidate_quick, test_libc_hooks, test_lift_lookups, test_link_skip, test_linux_pressure, test_linux_update, test_log_open_failure, test_missing_nup, test_mods_size_table, test_pending_guest_import, test_pipeline_play_cache, test_prepare_cache_save, test_present_thread, test_profiling_mode, test_psychov35_fsr3_fg, test_readback_timeout_source, test_run_all_changed, test_slow_frames, test_song_note_cue, test_switch_table, test_upscaler_rows, test_vcore_escape, test_walk_key, test_walk. Six more failed on only one side under the parallel run (test_display_pointer here; test_bug_report, test_control, test_crash_groups, test_hardware_report, test_perf_report on main): each passed when run alone, on both trees. The branch only adds two docs rows. That full run was on main 47430e81; the branch was then rebased onto 444f8e49 (#1689, #1701, #1715, none touching these files) and the tested-configurations check run again: OK.

Not tested: nothing in the game: the PR changes no game files.

Must be tested:

  • None

Risks

What could break: nothing in the game; the catalogue page gains two rows.

Turning it off: revert the commit.

Compatibility: Nothing changes.

Issues

See #1239
See #1650

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

🤖 Generated with Claude Code

**Type:** docs · **Risk:** low · **Tested on:** Windows 11, RX 6800 XT · **Needs:** none ## TL;DR On RX 6800 XT cards on Windows, the game used to hang a few minutes in at Saria's stump in Kokiri Forest. #1650 fixed that and shipped in v3.0.0. This PR records the RX 6800 XT retest that #1650 asked for. Two runs on v3.0.0 with default settings, one with a fresh shader cache and one warm, had no hang, no device loss and full foliage. ## Breakdown - **Who it helps:** anyone checking whether RX 6000 cards on Windows have been tested on v3.0.0. - **What was wrong:** nothing in the code; #1650's hardware retest wasn't recorded in the tested-configurations catalogue. - **What changes:** two rows in `docs/tested/`, one per run. - **What does not change:** the game, the frozen table, every other docs file. - **How it was checked:** `tests/test_tested_configurations.py` passes; the full suite's results are under Testing. - **What is still open:** #1239's reporter retesting on their own PC (asked on the issue). - **Risk:** low: two docs rows. ## Why #1650's Must be tested item was a Windows RX 6800 XT run of the patched build at the #1239 camera spot, with a warm-cache repeat and frame time and VRAM. That run is done (results comment: https://git.magicbean.dev/MagicBeanDev/Longshot/pulls/1650#issuecomment-52658), and `docs/tested/` is where a measured run goes (CONTRIBUTING.md, docs/workflow.md). ## What changed Two run files, following docs/tested/README.md: - `docs/tested/2026-11-18-rdna2-mesh-only-fallback-grimvisage-run01.md`: cold program cache. - `docs/tested/2026-11-18-rdna2-mesh-only-fallback-grimvisage-run02.md`: warm program cache. ## Measurements Nothing to measure: docs only. No game code, build, loading, cache, memory or tool changes, so frame time, build time and size, load time, RAM and VRAM can't be affected. The runs' own numbers are in the rows and in the #1650 comment linked above, with the log lines. ### Flags and settings None ## Testing **Tested:** on main 444f8e49 (this branch's base): `python -I -B tests/test_tested_configurations.py`: OK. `python -I -B tests/run_all.py` (Linux, no Vulkan headers here): this branch 663 passed, 39 failed, 123 skipped; main 47430e81 659 passed, 43 failed, 123 skipped. The same 37 fail on both: test_bug_report_defaults, test_capture_read_once, test_crt_options, test_damage_debug_menu, test_dev_packs, test_discover, test_display_startup_failure, test_dlss_feature_size, test_failed_compile_keeps_objects, test_guest_imported, test_high_fps_fixes, test_host_guest_writes, test_hud_layout_row, test_invalidate_quick, test_libc_hooks, test_lift_lookups, test_link_skip, test_linux_pressure, test_linux_update, test_log_open_failure, test_missing_nup, test_mods_size_table, test_pending_guest_import, test_pipeline_play_cache, test_prepare_cache_save, test_present_thread, test_profiling_mode, test_psychov35_fsr3_fg, test_readback_timeout_source, test_run_all_changed, test_slow_frames, test_song_note_cue, test_switch_table, test_upscaler_rows, test_vcore_escape, test_walk_key, test_walk. Six more failed on only one side under the parallel run (test_display_pointer here; test_bug_report, test_control, test_crash_groups, test_hardware_report, test_perf_report on main): each passed when run alone, on both trees. The branch only adds two docs rows. That full run was on main 47430e81; the branch was then rebased onto 444f8e49 (#1689, #1701, #1715, none touching these files) and the tested-configurations check run again: OK. **Not tested:** nothing in the game: the PR changes no game files. **Must be tested:** - None ## Risks **What could break:** nothing in the game; the catalogue page gains two rows. **Turning it off:** revert the commit. **Compatibility:** Nothing changes. ## Issues See #1239 See #1650 ## 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] A file in `docs/tested/` for each new measured run (format in `docs/tested-configurations.md`). - [x] Docs updated. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
docs(tested): RX 6800 XT runs of the mesh-only fallback on v3.0.0
Some checks failed
Website / Website on Cloudflare (pull_request_target) Has been skipped
PR description / Description follows the template (pull_request_target) Successful in 10s
CI / Conventional Commit title (pull_request) Has been cancelled
CI / Python source checks (ubuntu-24.04, part 1/2) (pull_request) Has been cancelled
CI / Python source checks (ubuntu-24.04, part 2/2) (pull_request) Has been cancelled
CI / SPIR-V fixtures (global narrow load/store, direct surface atomics, F2I immediate) (pull_request) Has been cancelled
CI / Workflow lint (actionlint) (pull_request) Has been cancelled
Guide screenshots / Guide images and local UI source review (pull_request) Has been cancelled
Third-party parts / As their notes say (pull_request) Has been cancelled
Third-party parts / The same as upstream (pull_request) Has been cancelled
Website / Website on Cloudflare (pull_request) Has been cancelled
738e9e91d5
Two runs on Windows 11, RX 6800 XT, AMD 26.10.1, at Saria's stump in Kokiri
Forest (the #1239 spot) with default mesh settings: one with a cold program
cache, one warm. No device loss and no hang; the foliage drew.

See #1239, #1650.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
GrimVisage changed title from WIP: docs(tested): RX 6800 XT runs of the mesh-only fallback on v3.0.0 to docs(tested): RX 6800 XT runs of the mesh-only fallback on v3.0.0 2026-11-19 06:41:35 +00:00
Author
Contributor

Closing: #1802 removed the tested-configurations catalogue (docs/tested/), so these run files have nowhere to go. The runs stay on record in this PR's description and comments, and the files in its diff.

Closing: #1802 removed the tested-configurations catalogue (docs/tested/), so these run files have nowhere to go. The runs stay on record in this PR's description and comments, and the files in its diff.
GrimVisage closed this pull request 2026-11-20 02:22:25 +00:00
Some checks failed
Website / Website on Cloudflare (pull_request_target) Has been skipped
PR description / Description follows the template (pull_request_target) Successful in 10s
CI / Conventional Commit title (pull_request) Has been cancelled
CI / Python source checks (ubuntu-24.04, part 1/2) (pull_request) Has been cancelled
CI / Python source checks (ubuntu-24.04, part 2/2) (pull_request) Has been cancelled
CI / SPIR-V fixtures (global narrow load/store, direct surface atomics, F2I immediate) (pull_request) Has been cancelled
CI / Workflow lint (actionlint) (pull_request) Has been cancelled
Guide screenshots / Guide images and local UI source review (pull_request) Has been cancelled
Third-party parts / As their notes say (pull_request) Has been cancelled
Third-party parts / The same as upstream (pull_request) Has been cancelled
Website / Website on Cloudflare (pull_request) Has been cancelled

Pull request closed

Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
MagicBeanDev/Longshot!1716
No description provided.