v2.0.11: ~11-15 fps in-game on RX 6700 XT, GPU time ~60-100 ms a frame (v2.0.6: 6-12 ms) #1278
Labels
No labels
accessibility
autorelease: pending
autorelease: tagged
bug
dependencies
documentation
duplicate
enhancement
github_actions
good first issue
help wanted
invalid
question
testing wanted
wontfix
No milestone
No assignees
1 participant
Due date
No due date set.
Dependencies
No dependencies set
Reference
MagicBeanDev/Hookshot#1278
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
Hookshot version
v2.0.11
What kind of problem
Low fps or stutter
What happened
Since updating from v2.0.6, gameplay runs at a steady 11-15 fps (Death
Mountain Trail, Kakariko Village, and the pause menu). The title screen and
loading screens still run at 60. On v2.0.6 the same areas ran at 40-60 fps.
In the logs, the GPU itself is the slow part: "GPU time" is 60-100 ms a frame
in play on v2.0.11, against 6-12 ms on v2.0.6. The "memory sync" in slow
submits (30-70 ms) is the main thread waiting on that GPU work.
Things I tried, each made no difference:
Attached:
the separate Kakariko -> Death Mountain Trail crash I'm reporting on its own)
Possibly related, from the v2.0.7-v2.0.11 changes:
04675cf(BC images getSTORAGE on AMD, so the game's BC encoders now run there) and the AMD BC
encoder PR #1052.
Where in the game
Death Mountain/Kokoriko Village
How often
Every time
Graphics card and driver version
AMD Radeon RX 6700 XT (12 GB), Vulkan 1.4, Windows, 2560x1440
CPU, RAM and operating system
AMD Ryzen 5 7500F, Windows 11 Home
Changes from the defaults
No response
Other software hooked into the game
No, nothing hooked in
hookshot_log.txt
C_v2.0.11_ASTC_RGBA8.txt
D_v2.0.6_for_comparison.txt
A_v2.0.11_default.txt
B_v2.0.11_WB_DIFF_0.txt
Screenshots or video
No response
Before you send it
Thanks for the careful A/B logs (v2.0.11 GPU time 60-100 ms a frame against 6-12 ms on v2.0.6, unchanged by RX_VK_WB_DIFF=0 or RX_VK_ASTC_RGBA8=1). Linking this to the FPS tracker #995 and AMD rendering #1006; the BC-encoder lead (
04675cf/ #1052) is a good one to check.Thanks for the report. Reports of the same problem are now collected in #995, which lists this one with your details and links back here, so one fix closes them together and the open list stays readable. Follow #995 for the fix, and add new details there (or here). If this turns out to be a separate problem it will be reopened.