docs(tested): RX 6800 XT runs of the mesh-only fallback on v3.0.0 #1716
No reviewers
Labels
No labels
area/accessibility
area/audio
area/input
area/install
area/menu
area/renderer
area/saves
area/tooling
area/upscaling
beanstalk: approved
beanstalk: failed
beanstalk: needs approval
beanstalk: running
beanstalk: tested
ci: approved
good first issue
gpu/amd
gpu/igpu
gpu/intel
gpu/nvidia
help wanted
kind
bug
kind
chore
kind
docs
kind
feature
kind
performance
kind
question
needs measurements
platform/linux
platform/macos
platform/steam-deck
platform/windows
preview
priority
critical
priority
high
priority
low
regression
risk
high
risk
low
risk
medium
status
blocked
status
confirmed
status
duplicate
status
invalid
status
needs-info
status
wontfix
ci: approved
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
MagicBeanDev/Longshot!1716
Loading…
Reference in a new issue
No description provided.
Delete branch "GrimVisage/Longshot:docs/tested-rdna2-mesh-only-6800xt"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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
docs/tested/, one per run.tests/test_tested_configurations.pypasses; the full suite's results are under Testing.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; main47430e81659 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 main47430e81; the branch was then rebased onto444f8e49(#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:
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
type(scope): description) of the status line's type.can't be run by hand is in Testing's Not testable by hand, with why.
in Risks.
main.python -I -B tests/run_all.pypasses (any failure that also fails onmainis named).third_party/untouched (a new folder with aPROVENANCE.mdinstead).When it applies
Assisted-by:/Co-Authored-By:trailers.docs/tested/for each new measured run (format indocs/tested-configurations.md).🤖 Generated with Claude Code
WIP: docs(tested): RX 6800 XT runs of the mesh-only fallback on v3.0.0to docs(tested): RX 6800 XT runs of the mesh-only fallback on v3.0.0Closing: #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.
Pull request closed