WIP: docs(tested): RX 7700 XT on CachyOS, Hookshot v2.2.0-rc.1 and Longshot v3.0.0-rc.3 in Kokiri Forest #240
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
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
MagicBeanDev/Longshot!240
Loading…
Reference in a new issue
No description provided.
Delete branch "mynameismawky/Longshot:docs/tested-config-rx7700xt"
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?
Why
Linux on AMD has the fewest measured runs in tested configurations. This adds two runs on an RX 7700 XT (RADV), the
first on this card: Hookshot v2.2.0-rc.1 and Longshot v3.0.0-rc.3 in the same scene. Longshot ran about 16-18% slower
there, and FSR 3.1 Quality no longer reaches the 60 fps cap.
What changed
docs/tested-configurations.md, one per build. The v2.2.0-rc.1 row was first opened asNotRexed/Hookshot#3014 before that repository went away.
Flags and settings
None.
Measurements
These are tested-configuration rows, not a code change: the two builds are compared to each other, not main against
this PR.
Baseline: Hookshot v2.2.0-rc.1 @
4aee2365Builds: both the release AppImages; Hookshot run on 2026-11-12, Longshot on 2026-11-13
Hardware: RX 7700 XT 12 GB, Mesa RADV 26.2.6, Core i7-14700KF, 64 GB, CachyOS (kernel 7.3.3), COSMIC Wayland
Scene: Kokiri Forest, standing still; 2560x1440 fullscreen output, the default 60 fps cap, mesh shaders Automatic
(the compute path); upscaler Off, then AMD FSR 3.1 at 100%, then FSR 3.1 Quality (1707x960), in one session
Method: about 30 s or more per setting, one run each; fps from
longshot_log.txt/hookshot_log.txt"N presents, X fps"lines, the slowest frame and VRAM from the "status: 600 frames" lines
How to reproduce: build each release's AppImage, set Output resolution to 2560x1440, stand still in Kokiri Forest and
switch the upscaler from the Insert menu
4aee23650c74253dThe comparison is approximate. I stood near the same spot in Kokiri Forest, but not exactly on it (about 2,800
draws a frame against about 2,600). Longshot's build also started from fresh options, and Auto (this PC) put the card in
tier 4; I didn't run Longshot with Hookshot's defaults to separate the two. Each setting ran once, not in interleaved
pairs. The gap holds across all three upscaler settings, so it is in the game's drawing rather than the upscaler.
Testing
Tested: both builds in the game on this PC, as above: past the opening cutscene on v2.2.0-rc.1, and a loaded save in
Kokiri Forest on v3.0.0-rc.3. No device lost on either; 10-14 programs failed in play on v2.2.0-rc.1 and 10-11 on
v3.0.0-rc.3, with nothing visibly wrong.
python -I -B tests/run_all.py: 457 passed, 2 failed, 66 skipped; the twofailures (
test_display_pointer.py,test_bake_portability.py) fail onmain1ef93e79without this change too.Not tested: where the slowdown comes from (Longshot's code or the Auto (this PC) tier 4 settings), and the same
exact position on both builds.
Needs other testers:
expecting the same ~16% drop if it is not specific to this PC (request to open)
Screenshots
Nothing on screen: documentation only.
Risk and rollback
None: documentation only.
Reviewer notes
The second row is the one worth a look: a slowdown on Linux AMD between the two releases, though only measured
approximately.
Issues
See NotRexed/Hookshot#3014 (the earlier PR for the first row, gone with that repository).
Checklist
For everyone
type(scope): description).main.python -I -B tests/run_all.pyrun and passing (any failure that also fails onmainis named above).third_party/untouched (a new folder with aPROVENANCE.mdinstead).If applicable
Assisted-by:/Co-Authored-By:trailers.docs/tested-configurations.mdfor each measured run.🤖 Generated with Claude Code
WIP: docs(tested): RX 7700 XT on CachyOS, Hookshot v2.2.0-rc.1 and Longshot v3.0.0-rc.3 in Kokiri Forestto docs(tested): RX 7700 XT on CachyOS, Hookshot v2.2.0-rc.1 and Longshot v3.0.0-rc.3 in Kokiri ForestThis conflicts with
mainindocs/tested-configurations.md: the table is frozen now (#96, and later), and new runs go in one file each underdocs/tested/(format indocs/tested/README.md), so the two rows need to become run files. Please rebase onto currentmain.Thanks for the RX 7700 XT run, the numbers are worth keeping.
docs/tested-configurations.mdis frozen since #96, so new rows can't go in there. Could you move this run into its own file underdocs/tested/(the format is indocs/tested-configurations.md) and push that here instead?Brought up to the ready-for-review standard (#1454): this description doesn't use the pull request template, which
pr readyand the description check require. Please fill it in, including the checklist's new Tested on my own PC box: where you ran the change yourself and what you saw. This goes back to WIP until then;pr readyit again once it passes.docs(tested): RX 7700 XT on CachyOS, Hookshot v2.2.0-rc.1 and Longshot v3.0.0-rc.3 in Kokiri Forestto WIP: docs(tested): RX 7700 XT on CachyOS, Hookshot v2.2.0-rc.1 and Longshot v3.0.0-rc.3 in Kokiri ForestView 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.