You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello! Thank you for your great work.
I have the following issue: I'm playing on a Ryzen 5 8600G with the integrated Radeon 760M graphics. At 2K resolution, my PC runs the game at 50–60 FPS. HOWEVER, once I enter a shrine/dungeon, the frame rate gradually drops (50, 48, 46, etc.) down to 30 FPS and stays locked there — it never goes back up. If I save, exit the game, and launch it again, the frame rate returns to 60 FPS until the next dungeon.
The exact same drop to 30 FPS also happens when Link gets a boost or during the item/rupee pickup animation (though not always). This issue was also present in the previous release (5.4). Dynamic resolution and frame generation are disabled in my settings.
Thanks for the detailed report. Staying at 30 until a restart sounds like the game deciding to drop to a 30 fps pace and never switching back, rather than the GPU running out of power, so we'd like to see what happens in the log.
This is an automatic summary of the LAS Recomp log files attached to this issue. It only reads the logs, so a person will still look at the details.
For a new report, please attach lasrecomp.log from LAS Recomp's data folder (it always holds the latest run; lasrecomp-backup-*.log there are the earlier runs).
Frame rate: 67 samples over 133 s: median 55.5 fps, lowest 29.2 fps, longest frame 252 ms; slowest areas: GopongaCave 30.0 fps, Field 56.4 fps
Slow frames: 2 [slow] lines; worst: [slow] frame 1426 50 ms in Field: 3 full texture hashes, 2 heap imports, 7 submissions, gpu wait 0 ms, render cpu 0 ms, game cpu 0 ms, qu...
New shader variants: 12 the shipped list lacks (12 pipelines, 0 compute)
Notable lines:
frame pacing switched to the game's 30 fps mode: [pace] frames don't fit 60 fps (22 of the last 60 over 16.2 ms busy or shown late, 22 by busy time, 0 by CPU time, median 13.0): holding ...
Frame rate: 56 samples over 110 s: median 57.5 fps, lowest 30.0 fps, longest frame 185 ms; slowest areas: GopongaCave 30.0 fps, Field 58.5 fps
Slow frames: 1 [slow] lines; worst: [slow] 6 more slow frames in the last minute, not logged (6 during loads)
New shader variants: 3 the shipped list lacks (3 pipelines, 0 compute)
Notable lines:
frame pacing switched to the game's 30 fps mode: [pace] frames don't fit 60 fps (21 of the last 60 over 16.2 ms busy or shown late, 21 by busy time, 0 by CPU time, median 13.1): holding ...
Thanks, the log shows what's happening in the dungeon. In the field your GPU keeps up at 60 fps. In Bottle Grotto, at 2560x1440 the Radeon 760M needs about 23 ms for each frame, and a 60 fps frame has to be under 16.7 ms. When frames don't fit, the game switches to its own 30 fps mode, which is steadier than a frame rate jumping between 40 and 60. The log says this directly:
[pace] 60 gameplay frames with clear CPU headroom (2.1 ms a frame at 60 on average), but the GPU takes 23.2 ms a frame: staying at 30
So in dungeons this is the integrated GPU's limit at 1440p, not a bug. To keep 60 there, either:
turn on Dynamic resolution, which lowers the render resolution only while the GPU can't keep up, or
set the render resolution to 1920x1080.
One part we can't see yet: in this log you quit while still in the dungeon, so it doesn't show the frame rate staying at 30 after you leave. If it still stays at 30 back in the field, could you attach a log where you go into a dungeon, wait for 30, then walk back out to the field and play there for a minute before quitting?
Then why is it that when I enter a dungeon and the frame rate drops to 30, if I save inside that dungeon, quit to the desktop, and load that save, it runs at around 60 FPS upon loading back into the same dungeon? And that same 60 FPS remains even after I leave the dungeon.
Good point, and that changes the picture. If the same dungeon runs at about 60 after a restart, the GPU can do it, and the switch back from 30 is what's failing.
Looking at the log again, the switch to 30 happened right as you entered Bottle Grotto, while it was still loading. After that, the check for going back to 60 measures how long the GPU takes per frame while the game runs at 30. An integrated GPU like the 760M lowers its clock speed when it only has to draw 30 frames a second, so each frame looks slower than it really is (23 ms here). The check never sees enough room, and it stays at 30 until a restart. That's on our side, and we'll look at fixing it.
To confirm it, could you attach one more lasrecomp.log from the case that works: load your save inside the dungeon after a restart, play there for a minute at 60, then quit? That gives us the GPU's real time per frame in the same place to compare.
Thanks, this one shows it clearly. Before the dungeon, the field runs at 58 to 60 fps. In Bottle Grotto it switches to 30 while the dungeon is still loading, and once you're back in the field it stays at 30 for the rest of the session, even though the same field ran at 60 a minute earlier. So it's the switch back to 60 that's broken, not your GPU. We're working on a fix and will post here when there's a build to try.
Until then, turning on Dynamic resolution should avoid it in most places, since it lowers the resolution for a moment instead of switching to 30.
Here is another example of a log from a different dungeon; in this case, no frame rate drop occurs, even though it is more densely populated with map objects, if that makes any difference.
Thanks, that helps too. In this log Bottle Grotto also loads slowly for its first second or two, but this time those slow frames fell inside the window where we ignore loading frames, so the switch to 30 never started, and the cave in the Mysterious Woods holds about 56 to 57. So whether it gets stuck depends on how the loading frames land, not on how busy the dungeon is. That matches what we're fixing.
When the game drops to 30 and your CPU has room to spare, it now tries 60 again after about 10 seconds. If 60 fits, it stays there. If not, it goes back to 30 and waits longer before the next try.
Unzip it into a new folder and keep your normal install as it is. If it offers to update, skip that while you test.
Could you enter Bottle Grotto a few times, play there for a minute, then walk back out to the field and play there for a minute? Then attach lasrecomp.log. The lines starting with [pace] show each try at 60.
@martinkuhl Thanks. The fix in the current test build is Windows-only for now. To check that your Android drop has the same cause, could you tell us which phone or tablet you're on and attach lasrecomp.log from the data folder, from a run where it drops to 30 and stays there? Phones can also drop to 30 when they heat up, which is a different cause, and the log tells the two apart.
• Log 1 (Beach): The frame rate drops to 30 FPS (it feels like this happens when crabs appear). If I step aside a little, the frame rate goes back up to 60 FPS. • Log 2 (Beach — loading from the frame drop spot): Loading a save in the exact same spot on the beach after the frame rate has dropped to 30 FPS keeps the frame rate around ±60 FPS. • Log 3 (Picking up items): Picking up a Piece of Heart. While the animation plays (Link looks at the screen with the Piece of Heart above his head), there is a brief drop to 30 FPS, after which the frame rate recovers. (The exact same thing used to happen at the beginning of the game and when picking up Rupees, for example, in the shop with the crane game in the starting town, though it stopped happening later). • Log 4 (Cave): That same cave. Upon entering the cave, the frame rate drops to 30 FPS just like before. If I run around for a bit, it tries to recover at some point, but then drops again. Also, upon exiting the cave, there are two possible scenarios: if I just run around the clearing and fight mobs, the frame rate does not recover; however, if a mob (the one that looks like a jar/pot, Like Like) eats me and then spits me out, the frame rate recovers to ±60 FPS. (My previous statement that loading a save inside the cave after a drop to 30 FPS fixes the frame rate turned out to be incorrect — after loading inside the cave, the frame rate still drops to 30 FPS). • Log 5 (1080p resolution): Here, just as you suggested earlier, I tried playing at a 1920x1080 resolution, and as you predicted, the frame rate drop in the cave does not occur at this resolution.
Activity
peiikai commentedon Nov 15, 2026
Thanks for the detailed report. Staying at 30 until a restart sounds like the game deciding to drop to a 30 fps pace and never switching back, rather than the GPU running out of power, so we'd like to see what happens in the log.
Could you:
lasrecomp.logfrom the data folder here.Also, which version of the AMD graphics driver are you on, and is 2K the render resolution in the settings or your monitor's resolution?
Lex83nick commentedon Nov 15, 2026
lasrecomp.log
2K is the render resolution in the game as well as the monitor's resolution.
github-actions commentedon Nov 15, 2026
This is an automatic summary of the LAS Recomp log files attached to this issue. It only reads the logs, so a person will still look at the details.
For a new report, please attach
lasrecomp.logfrom LAS Recomp's data folder (it always holds the latest run;lasrecomp-backup-*.logthere are the earlier runs).Newest log: lasrecomp.log in comment from 2026-11-15
v0.6.0 (zip)Windows 11 (10.0.26100, x64), AMD Ryzen 5 8600G w/ Radeon 760M Graphics 6 cores / 12 threads, 31.1 GB RAMRadeon 5(integrated), Vulkan 1.4.359, driverAMD proprietary driver 26.10.1 (LLPC)upscaler bilinear (default), resolution match (chosen), anti-aliasing smaa; window 2560x1440, fifoGopongaCave49.6 fps,Field56.5 fps[slow]lines; worst:[slow] 7 more slow frames in the last minute, not logged (7 during loads)Earlier log: lasrecomp.log in comment from 2026-11-15
v0.6.0 (zip)Windows 11 (10.0.26100, x64), AMD Ryzen 5 8600G w/ Radeon 760M Graphics 6 cores / 12 threads, 31.1 GB RAMRadeon 5(integrated), Vulkan 1.4.359, driverAMD proprietary driver 26.10.1 (LLPC)upscaler bilinear (default), resolution match (chosen), anti-aliasing smaa; window 2560x1440, fifoGopongaCave30.0 fps,Field56.4 fps[slow]lines; worst:[slow] frame 1426 50 ms in Field: 3 full texture hashes, 2 heap imports, 7 submissions, gpu wait 0 ms, render cpu 0 ms, game cpu 0 ms, qu...[pace] frames don't fit 60 fps (22 of the last 60 over 16.2 ms busy or shown late, 22 by busy time, 0 by CPU time, median 13.0): holding ...Earlier log: lasrecomp.log in comment from 2026-11-15
v0.6.0 (zip)Windows 11 (10.0.26100, x64), AMD Ryzen 5 8600G w/ Radeon 760M Graphics 6 cores / 12 threads, 31.1 GB RAMRadeon 5(integrated), Vulkan 1.4.359, driverAMD proprietary driver 26.10.1 (LLPC)upscaler bilinear (default), resolution match (chosen), anti-aliasing smaa; window 2560x1440, fifoGopongaCave30.0 fps,Field58.5 fps[slow]lines; worst:[slow] 6 more slow frames in the last minute, not logged (6 during loads)[pace] frames don't fit 60 fps (21 of the last 60 over 16.2 ms busy or shown late, 21 by busy time, 0 by CPU time, median 13.1): holding ...Shader variants the shipped list lacks (19)
peiikai commentedon Nov 15, 2026
Thanks, the log shows what's happening in the dungeon. In the field your GPU keeps up at 60 fps. In Bottle Grotto, at 2560x1440 the Radeon 760M needs about 23 ms for each frame, and a 60 fps frame has to be under 16.7 ms. When frames don't fit, the game switches to its own 30 fps mode, which is steadier than a frame rate jumping between 40 and 60. The log says this directly:
So in dungeons this is the integrated GPU's limit at 1440p, not a bug. To keep 60 there, either:
One part we can't see yet: in this log you quit while still in the dungeon, so it doesn't show the frame rate staying at 30 after you leave. If it still stays at 30 back in the field, could you attach a log where you go into a dungeon, wait for 30, then walk back out to the field and play there for a minute before quitting?
Lex83nick commentedon Nov 15, 2026
Then why is it that when I enter a dungeon and the frame rate drops to 30, if I save inside that dungeon, quit to the desktop, and load that save, it runs at around 60 FPS upon loading back into the same dungeon? And that same 60 FPS remains even after I leave the dungeon.
Lex83nick commentedon Nov 15, 2026
Log showing a frame rate drop inside the dungeon that fails to return to normal values upon exiting.
lasrecomp.log
peiikai commentedon Nov 15, 2026
Good point, and that changes the picture. If the same dungeon runs at about 60 after a restart, the GPU can do it, and the switch back from 30 is what's failing.
Looking at the log again, the switch to 30 happened right as you entered Bottle Grotto, while it was still loading. After that, the check for going back to 60 measures how long the GPU takes per frame while the game runs at 30. An integrated GPU like the 760M lowers its clock speed when it only has to draw 30 frames a second, so each frame looks slower than it really is (23 ms here). The check never sees enough room, and it stays at 30 until a restart. That's on our side, and we'll look at fixing it.
To confirm it, could you attach one more
lasrecomp.logfrom the case that works: load your save inside the dungeon after a restart, play there for a minute at 60, then quit? That gives us the GPU's real time per frame in the same place to compare.peiikai commentedon Nov 15, 2026
Thanks, this one shows it clearly. Before the dungeon, the field runs at 58 to 60 fps. In Bottle Grotto it switches to 30 while the dungeon is still loading, and once you're back in the field it stays at 30 for the rest of the session, even though the same field ran at 60 a minute earlier. So it's the switch back to 60 that's broken, not your GPU. We're working on a fix and will post here when there's a build to try.
Until then, turning on Dynamic resolution should avoid it in most places, since it lowers the resolution for a moment instead of switching to 30.
Lex83nick commentedon Nov 15, 2026
Here is another example of a log from a different dungeon; in this case, no frame rate drop occurs, even though it is more densely populated with map objects, if that makes any difference.
lasrecomp.log
peiikai commentedon Nov 15, 2026
Thanks, that helps too. In this log Bottle Grotto also loads slowly for its first second or two, but this time those slow frames fell inside the window where we ignore loading frames, so the switch to 30 never started, and the cave in the Mysterious Woods holds about 56 to 57. So whether it gets stuck depends on how the loading frames land, not on how busy the dungeon is. That matches what we're fixing.
peiikai commentedon Nov 15, 2026
Here's a test build with a fix: https://github.com/peiikai/LASRecomp/releases/tag/test-811-pace-hold
When the game drops to 30 and your CPU has room to spare, it now tries 60 again after about 10 seconds. If 60 fits, it stays there. If not, it goes back to 30 and waits longer before the next try.
Unzip it into a new folder and keep your normal install as it is. If it offers to update, skip that while you test.
Could you enter Bottle Grotto a few times, play there for a minute, then walk back out to the field and play there for a minute? Then attach
lasrecomp.log. The lines starting with[pace]show each try at 60.martinkuhl commentedon Nov 16, 2026
I have the same behavior on Android. Could you create a test build for the android to plattform?
peiikai commentedon Nov 16, 2026
@martinkuhl Thanks. The fix in the current test build is Windows-only for now. To check that your Android drop has the same cause, could you tell us which phone or tablet you're on and attach lasrecomp.log from the data folder, from a run where it drops to 30 and stays there? Phones can also drop to 30 when they heat up, which is a different cause, and the log tells the two apart.
martinkuhl commentedon Nov 16, 2026
I am using an OnePlus Pad2 with an Adrino 750. I will add the logs later.
Lex83nick commentedon Nov 16, 2026
• Log 1 (Beach): The frame rate drops to 30 FPS (it feels like this happens when crabs appear). If I step aside a little, the frame rate goes back up to 60 FPS.
• Log 2 (Beach — loading from the frame drop spot): Loading a save in the exact same spot on the beach after the frame rate has dropped to 30 FPS keeps the frame rate around ±60 FPS.
• Log 3 (Picking up items): Picking up a Piece of Heart. While the animation plays (Link looks at the screen with the Piece of Heart above his head), there is a brief drop to 30 FPS, after which the frame rate recovers. (The exact same thing used to happen at the beginning of the game and when picking up Rupees, for example, in the shop with the crane game in the starting town, though it stopped happening later).
• Log 4 (Cave): That same cave. Upon entering the cave, the frame rate drops to 30 FPS just like before. If I run around for a bit, it tries to recover at some point, but then drops again. Also, upon exiting the cave, there are two possible scenarios: if I just run around the clearing and fight mobs, the frame rate does not recover; however, if a mob (the one that looks like a jar/pot, Like Like) eats me and then spits me out, the frame rate recovers to ±60 FPS. (My previous statement that loading a save inside the cave after a drop to 30 FPS fixes the frame rate turned out to be incorrect — after loading inside the cave, the frame rate still drops to 30 FPS).
• Log 5 (1080p resolution): Here, just as you suggested earlier, I tried playing at a 1920x1080 resolution, and as you predicted, the frame rate drop in the cave does not occur at this resolution.
I hope I explained everything clearly enough.
1 lasrecomp.log
2 lasrecomp.log
3 lasrecomp.log
4 lasrecomp.log
5 lasrecomp.log