Game: FPS drops and remains around 25 after boss and Goron king cutscene #812

New issue

Open

opened 2026-11-15 13:47:21 +00:00 by BeanIssues · 2 comments

BeanIssues commented

2026-11-15 13:47:21 +00:00

Collaborator

Reported by sagsywagsy on Discord

Longshot version

v3.0.0-rc.4 (source b784a40c)

Channel

Release candidate

What happened

The game ran at a relatively smooth 50 FPS before defeating the boss. After the Goron king cutscene, the game reached a maximum of about 25 FPS everywhere. Please investigate why performance remains reduced after the cutscene.

Where in the game

After defeating the boss and the Goron king cutscene. The bug report's current map is KakarikoVillage_Child (child).

How often

It continued everywhere after the cutscene.

Graphics card and driver version

AMD Radeon RX 6650 XT, AMD proprietary driver 25.10.30.02 (AMD proprietary shader compiler).

CPU, RAM and operating system

AMD Ryzen 5 3600 (12 threads), 32 GB, Windows 10 (build 19045). The user clarified that Windows 10 was used; the earlier Windows 11 message was a mistake.

Settings

Notable changes: AMD Anti-Lag 2 on, fullscreen on, anisotropic filtering Game's, threaded rendering off, sampler cache on. 1920x1080, Docked profile, render resolution 100%, frame pacing on, game speed real time. See report for full settings.

Logs and screenshots

Bug report includes longshot_log.txt (current run, 1.1 MB) and longshot_log.1.txt (previous run, 6.6 MB); report.txt is also attached. The support attachment reader could not inspect the current log due to its size; please review the attached files.

Reported by [sagsywagsy on Discord](https://discord.com/channels/1569849200047427645/1571519113069600779/1571521705900380210) ### Longshot version v3.0.0-rc.4 (source b784a40c) ### Channel Release candidate ### What happened The game ran at a relatively smooth 50 FPS before defeating the boss. After the Goron king cutscene, the game reached a maximum of about 25 FPS everywhere. Please investigate why performance remains reduced after the cutscene. ### Where in the game After defeating the boss and the Goron king cutscene. The bug report's current map is KakarikoVillage_Child (child). ### How often It continued everywhere after the cutscene. ### Graphics card and driver version AMD Radeon RX 6650 XT, AMD proprietary driver 25.10.30.02 (AMD proprietary shader compiler). ### CPU, RAM and operating system AMD Ryzen 5 3600 (12 threads), 32 GB, Windows 10 (build 19045). The user clarified that Windows 10 was used; the earlier Windows 11 message was a mistake. ### Settings Notable changes: AMD Anti-Lag 2 on, fullscreen on, anisotropic filtering Game's, threaded rendering off, sampler cache on. 1920x1080, Docked profile, render resolution 100%, frame pacing on, game speed real time. See report for full settings. ### Logs and screenshots Bug report includes longshot_log.txt (current run, 1.1 MB) and longshot_log.1.txt (previous run, 6.6 MB); report.txt is also attached. The support attachment reader could not inspect the current log due to its size; please review the attached files.

report.txt

4.5 KiB

longshot_log.txt

1.1 MiB

longshot_log.1.txt

6.6 MiB

BeanIssues added the

labels

2026-11-15 13:47:21 +00:00

BeanIssues commented

2026-11-15 13:47:28 +00:00

Author

Collaborator

Files from the Discord report:

Files from the Discord report: - [report.txt](https://git.magicbean.dev/attachments/cfbb42d3-6edb-4790-88bf-9624e08ee66f) - [longshot_log.txt](https://git.magicbean.dev/attachments/70381bb5-1df5-4c9e-9f25-9b305454a088) - [longshot_log.1.txt](https://git.magicbean.dev/attachments/2bcc3ad5-b9f2-4d8a-8f25-84a8111a8e1b)

BeanIssues commented

2026-11-15 13:48:28 +00:00

Author

Collaborator

Updated with more from sagsywagsy on Discord: Clarified that the affected run used Windows 10; the earlier Windows 11 message was a mistake.

Updated with more from [sagsywagsy on Discord](https://discord.com/channels/1569849200047427645/1571519113069600779/1571522152866517047): Clarified that the affected run used Windows 10; the earlier Windows 11 message was a mistake.