Game: Severe FPS drop walking around Hyrule Market on Windows with RX 9060 XT #1153

Open
opened 2026-11-16 15:45:35 +00:00 by BeanIssues · 5 comments
Collaborator

Reported on a DM to the bot on Discord from planglima

Longshot version

v3.0.0-rc.5 (release candidate), from the attached log.

What kind of problem

Low FPS / performance.

What happened and steps to reproduce

The reporter says they never reach 60 FPS. After trying suggested graphics settings, they walked around Hyrule Market and still had low FPS. The log has a minimum sample of 18 FPS and finishes at 31.4 FPS average.

Where in the game

Hyrule Market, walking around.

How often

Not specified.

Graphics card and driver version

AMD Radeon RX 9060 XT 16 GB. Driver version not provided.

CPU, RAM and operating system

Intel Xeon E5-2680 v4, 64 GB RAM. Windows version not provided.

Graphics settings

Screenshots show 2560×1440 output, Docked profile, upscaler Off, render resolution 100%, frame generation Off, frame pacing On, 60 FPS cap, AMD Anti-Lag 2 On, fullscreen On, V-Sync Auto, CRT filter Off, and HDR Off. Reporter says they placed a longshot_env.txt containing the requested lines, but the screenshot only shows the file listing, not the contents. The attached log has no detailed performance measurements.

What is still needed

A measured capture with HOS_FPS_LOG=1, HOS_THREAD_TIMES=5, RX_VK_PASS_TIMING=1 and RX_VK_SLOW_LOG=50 active, and a Bug report made while slow; confirmation of the settings in that measured run, AMD driver version, Windows version, and whether it happens every time. Follow the performance guide: restart after setting the environment file, walk in the Market for 60–90 seconds, then provide the Bug report folder and log.

longshot_log.txt

Attached log: FPS samples minimum 18, median 60, maximum 240; final reported average 31.4 FPS. It lacks HOS_THREAD_TIMES / RX_VK_PASS_TIMING detailed measurements.

Screenshots

Screenshots show graphics settings and that longshot_env.txt exists in the game's image folder; they do not show its contents.

Longshot#996 reports a Market performance hit on different hardware, platform and conditions; this report is distinct (Windows, AMD RX 9060 XT, general walking around the Market, without the same specific spot/trigger established).

What the reporter expected

They expected to reach 60 FPS while playing; the Market walk remains well below that.

Reported on a DM to the bot on Discord from `planglima` ### Longshot version v3.0.0-rc.5 (release candidate), from the attached log. ### What kind of problem Low FPS / performance. ### What happened and steps to reproduce The reporter says they never reach 60 FPS. After trying suggested graphics settings, they walked around Hyrule Market and still had low FPS. The log has a minimum sample of 18 FPS and finishes at 31.4 FPS average. ### Where in the game Hyrule Market, walking around. ### How often Not specified. ### Graphics card and driver version AMD Radeon RX 9060 XT 16 GB. Driver version not provided. ### CPU, RAM and operating system Intel Xeon E5-2680 v4, 64 GB RAM. Windows version not provided. ### Graphics settings Screenshots show 2560×1440 output, Docked profile, upscaler Off, render resolution 100%, frame generation Off, frame pacing On, 60 FPS cap, AMD Anti-Lag 2 On, fullscreen On, V-Sync Auto, CRT filter Off, and HDR Off. Reporter says they placed a `longshot_env.txt` containing the requested lines, but the screenshot only shows the file listing, not the contents. The attached log has no detailed performance measurements. ### What is still needed A measured capture with HOS_FPS_LOG=1, HOS_THREAD_TIMES=5, RX_VK_PASS_TIMING=1 and RX_VK_SLOW_LOG=50 active, and a Bug report made while slow; confirmation of the settings in that measured run, AMD driver version, Windows version, and whether it happens every time. Follow the performance guide: restart after setting the environment file, walk in the Market for 60–90 seconds, then provide the Bug report folder and log. ### longshot_log.txt Attached log: FPS samples minimum 18, median 60, maximum 240; final reported average 31.4 FPS. It lacks HOS_THREAD_TIMES / RX_VK_PASS_TIMING detailed measurements. ### Screenshots Screenshots show graphics settings and that `longshot_env.txt` exists in the game's `image` folder; they do not show its contents. ### Related issue Longshot#996 reports a Market performance hit on different hardware, platform and conditions; this report is distinct (Windows, AMD RX 9060 XT, general walking around the Market, without the same specific spot/trigger established). ### What the reporter expected They expected to reach 60 FPS while playing; the Market walk remains well below that.
Author
Collaborator

Files from the Discord report:

Files from the Discord report: - [longshot_log.txt](https://git.magicbean.dev/attachments/97d2daff-2fe5-4f7e-b2b4-07f88f033136) - [image.png](https://git.magicbean.dev/attachments/4161250d-1ce0-47b8-abec-3e01eeafb445) - [image.png](https://git.magicbean.dev/attachments/2a75fcf8-1de3-4f4c-8d10-7e09187db808) - [image.png](https://git.magicbean.dev/attachments/dd970480-b159-4291-9b58-72e01a877c9c)
Author
Collaborator

From a DM to the bot on Discord from planglima:

Follow-up from the reporter: a gameplay performance-overlay screenshot shows 22 FPS / 51.8 ms and identifies Longshot v3.0.0-rc.5, AMD Radeon RX 9060 XT, and AMD proprietary driver 26.10.1 (LLPC). It shows Xeon E5-2680 v4. Graphics screenshots show AMD FSR 4 at 75% render resolution (1920×1080), 2560×1440 output, frame generation Off, frame pacing On, 60 FPS cap, Anti-Lag 2 On, fullscreen On, V-Sync Auto, CRT filter Off, HDR Off. The newly attached log contains detailed renderer timings and confirms sustained slow frames, ending at 22.4 FPS over the last 5 seconds. Windows version and whether this is the requested controlled 60–90 second Hyrule Market measurement/Bug report remain unconfirmed.

From a DM to the bot on Discord from `planglima`: Follow-up from the reporter: a gameplay performance-overlay screenshot shows 22 FPS / 51.8 ms and identifies Longshot v3.0.0-rc.5, AMD Radeon RX 9060 XT, and AMD proprietary driver 26.10.1 (LLPC). It shows Xeon E5-2680 v4. Graphics screenshots show AMD FSR 4 at 75% render resolution (1920×1080), 2560×1440 output, frame generation Off, frame pacing On, 60 FPS cap, Anti-Lag 2 On, fullscreen On, V-Sync Auto, CRT filter Off, HDR Off. The newly attached log contains detailed renderer timings and confirms sustained slow frames, ending at 22.4 FPS over the last 5 seconds. Windows version and whether this is the requested controlled 60–90 second Hyrule Market measurement/Bug report remain unconfirmed.
Author
Collaborator

From a DM to the bot on Discord from planglima:

Follow-up screenshots confirm Windows 10 Pro 22H2 (OS build 19045.6466) and show settings: 2560×1440, upscaler Off, 100% render resolution, frame generation Off, frame pacing On, 60 FPS cap, Anti-Lag 2 On, fullscreen On, V-Sync Auto, CRT filter Off, HDR Off. The new detailed renderer log ends at 22.2 FPS over its last 5 seconds (22.4 FPS final summary), with overall samples min 22 / median 150 / max 243. Final replay timing: submit 36.07 ms, draw 16.89 ms, descriptors 6.35 ms, commands 4.92 ms, memory sync 4.63 ms; reported GPU time 13.7 ms/frame. The prior update described FSR 4 at 75%, which differs from these screenshots; please confirm what settings were active during this log. Also still unconfirmed whether it was the requested controlled 60–90 second Market run/Bug report and how often it happens. Add the follow-up longshot_log.txt and screenshots from Discord message 1571915865832816711.

From a DM to the bot on Discord from `planglima`: Follow-up screenshots confirm Windows 10 Pro 22H2 (OS build 19045.6466) and show settings: 2560×1440, upscaler Off, 100% render resolution, frame generation Off, frame pacing On, 60 FPS cap, Anti-Lag 2 On, fullscreen On, V-Sync Auto, CRT filter Off, HDR Off. The new detailed renderer log ends at 22.2 FPS over its last 5 seconds (22.4 FPS final summary), with overall samples min 22 / median 150 / max 243. Final replay timing: submit 36.07 ms, draw 16.89 ms, descriptors 6.35 ms, commands 4.92 ms, memory sync 4.63 ms; reported GPU time 13.7 ms/frame. The prior update described FSR 4 at 75%, which differs from these screenshots; please confirm what settings were active during this log. Also still unconfirmed whether it was the requested controlled 60–90 second Market run/Bug report and how often it happens. Add the follow-up longshot_log.txt and screenshots from Discord message 1571915865832816711.
Author
Collaborator

From a DM to the bot on Discord from planglima:

Reporter confirms the detailed log was recorded during the requested 60–90 second Hyrule Market walk and that active settings were AMD FSR 4 at 75% render resolution. This resolves the prior discrepancy with screenshots showing upscaling Off/100%. Driver and Windows versions were already reported; frequency remains unspecified.

From a DM to the bot on Discord from `planglima`: Reporter confirms the detailed log was recorded during the requested 60–90 second Hyrule Market walk and that active settings were AMD FSR 4 at 75% render resolution. This resolves the prior discrepancy with screenshots showing upscaling Off/100%. Driver and Windows versions were already reported; frequency remains unspecified.
Author
Collaborator

From a DM to the bot on Discord from planglima:

Reporter confirms the slowdown happens very often, especially near crowds or in the morning.

From a DM to the bot on Discord from `planglima`: Reporter confirms the slowdown happens very often, especially near crowds or in the morning.
Sign in to join this conversation.
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#1153
No description provided.