Skip to content

FPS drops from 60 to 30 on 8600g (760m) #811

Open

Description

@Lex83nick

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.

Activity

  1. peiikai commented on Nov 15, 2026

    @peiikai
    Owner

    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:

    1. Use Beta 6 (v0.6.0): https://github.com/peiikai/LASRecomp/releases/tag/v0.6.0
    2. Start the game, go into a dungeon or shrine, and play until it's stuck at 30 fps for a minute or so.
    3. Quit, then attach lasrecomp.log from 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?

  2. Lex83nick commented on Nov 15, 2026

    @Lex83nick
    Author

    lasrecomp.log

    2K is the render resolution in the game as well as the monitor's resolution.

  3. github-actions commented on Nov 15, 2026

    @github-actions

    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).

    Newest log: lasrecomp.log in comment from 2026-11-15

    • Build: v0.6.0 (zip)
    • System: Windows 11 (10.0.26100, x64), AMD Ryzen 5 8600G w/ Radeon 760M Graphics 6 cores / 12 threads, 31.1 GB RAM
    • GPU: Radeon 5 (integrated), Vulkan 1.4.359, driver AMD proprietary driver 26.10.1 (LLPC)
    • Backend: Vulkan
    • Graphics settings: upscaler bilinear (default), resolution match (chosen), anti-aliasing smaa; window 2560x1440, fifo
    • How the run ended: clean exit (window closed)
    • Frame rate: 93 samples over 184 s: median 56.5 fps, lowest 49.1 fps, longest frame 179 ms; slowest areas: GopongaCave 49.6 fps, Field 56.5 fps
    • Slow frames: 2 [slow] lines; worst: [slow] 7 more slow frames in the last minute, not logged (7 during loads)
    • New shader variants: 17 the shipped list lacks (17 pipelines, 0 compute)

    Earlier log: lasrecomp.log in comment from 2026-11-15

    • Build: v0.6.0 (zip)
    • System: Windows 11 (10.0.26100, x64), AMD Ryzen 5 8600G w/ Radeon 760M Graphics 6 cores / 12 threads, 31.1 GB RAM
    • GPU: Radeon 5 (integrated), Vulkan 1.4.359, driver AMD proprietary driver 26.10.1 (LLPC)
    • Backend: Vulkan
    • Graphics settings: upscaler bilinear (default), resolution match (chosen), anti-aliasing smaa; window 2560x1440, fifo
    • How the run ended: clean exit (window closed)
    • 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 ...

    Earlier log: lasrecomp.log in comment from 2026-11-15

    • Build: v0.6.0 (zip)
    • System: Windows 11 (10.0.26100, x64), AMD Ryzen 5 8600G w/ Radeon 760M Graphics 6 cores / 12 threads, 31.1 GB RAM
    • GPU: Radeon 5 (integrated), Vulkan 1.4.359, driver AMD proprietary driver 26.10.1 (LLPC)
    • Backend: Vulkan
    • Graphics settings: upscaler bilinear (default), resolution match (chosen), anti-aliasing smaa; window 2560x1440, fifo
    • How the run ended: clean exit (window closed)
    • 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 ...
    Shader variants the shipped list lacks (19)
    G vs=0588f3c609c51453 fs=541c0577d3740fbe f=1 a=22,2800d,0,0,0,0,18069,0,0,20026 s=18/0,4/0 c=3f:3f d=35 n=1 m=f b=0 B= k=0 t=2 p=1
    G vs=06fb5c3ad910eeac fs=81d1175a634baaee f=1 a=16 s=8/0 c=3f:3f d=0 n=1 m=f b=1 B=0005060506010100 k=0 t=2 p=1
    G vs=15c4751302e32edc fs=72ccccf6e7eb13d7 f=1 a=29,20012,0,0,12e,22e,32e,42e s=14/0,10/1,10/1,10/1,10/1 c=3f:3f d=35 n=1 m=f b=1 B=0005060506010100 k=0 t=2 p=1
    G vs=19e669452cd929c0 fs=5650aa3f6be8c0f1 f=1 a=16 s=8/0 c=25:25 d=0 n=1 m=f b=0 B= k=0 t=2 p=1
    G vs=2e95b7f184a5448c fs=5a7215eea63c7884 f=1 a=29,20012,0,18025,12e,22e,32e,42e,52e s=14/0,10/1,10/1,10/1,10/1,10/1 c=3f:3f d=35 n=1 m=f b=1 B=0005020502010100 k=0 t=2 p=1
    G vs=5815588583081b5a fs=58cd23504c3b00f8 f=1 a=16 s=8/0 c=3f:3f d=35 n=1 m=f b=1 B=0005060506010100 k=0 t=2 p=1
    G vs=64c70480d5f858de fs=15ebc3ba726dac1c f=1 a=22,20012,0,12e,22e,32e,42e s=14/0,10/1,10/1,10/1,10/1 c=3f:3f d=35 n=1 m=f b=1 B=0005060506010100 k=0 t=2 p=1
    G vs=6a136b3c75b12e61 fs=624a6c14bd8f6964 f=1 a=2e,12e,22e,32e,42e,52e s=10/1,10/1,10/1,10/1,10/1,10/1 c=3f:3f d=35 n=1 m=f b=1 B=0005020502010100 k=0 t=2 p=1
    G vs=70aee9e607a12d6a fs=b73f5ec46c9a7ef1 f=1 a=2e,12e,22e,32e s=10/1,10/1,10/1,10/1 c=3f:3f d=35 n=1 m=f b=1 B=0005060506010100 k=0 t=2 p=1
    G vs=83a292104bbe7606 fs=3a611ee7a79d256a f=1 a=22,3000e,3000e,3000e,3000e,3000e,18069,0,0,20026 s=20/0 c=3f:3f d=35 n=1 m=f b=0 B= k=0 t=2 p=1
    G vs=b5539ce5007ace3c fs=d0f21ea0cf7ad5e2 f=1 a=16 s=8/0 c=25:25 d=0 n=1 m=f b=0 B= k=0 t=2 p=1
    G vs=b5539ce5007ace3c fs=d0f21ea0cf7ad5e2 f=1 a=16 s=8/0 c=3f:3f d=35 n=1 m=f b=1 B=0005020502010100 k=0 t=2 p=1
    G vs=b5aeb7773c99d0b6 fs=7a38a223de553ee5 f=1 a=2e,12e,22e,32e,42e s=10/1,10/1,10/1,10/1,10/1 c=3f:3f d=35 n=1 m=f b=1 B=0005060506010100 k=0 t=2 p=1
    G vs=c987eb85e3e904c7 fs=e5c651f0f6254832 f=1 a=22,28012,18069,20025,12e,22e,32e,42e s=18/0,10/1,10/1,10/1,10/1 c=3f:3f d=35 n=1 m=f b=1 B=0005060506010100 k=0 t=2 p=1
    G vs=f802a69a8f48f21c fs=bf15dc51e88d07b3 f=1 a=16 s=8/0 c=3f:3f d=35 n=1 m=f b=1 B=0005060506010100 k=0 t=2 p=1
    G vs=f802a69a8f48f21c fs=f05eae47afe1e998 f=1 a=16 s=8/0 c=3f:3f d=0 n=1 m=f b=1 B=0001030103010100 k=0 t=2 p=1
    G vs=f802a69a8f48f21c fs=f05eae47afe1e998 f=1 a=16 s=8/0 c=3f:3f d=0 n=1 m=f b=1 B=0005020502030300 k=0 t=2 p=1
    G vs=fa3a619ff3892317 fs=420fe19170c004e8 f=1 a=16 s=8/0 c=3f:3f d=35 n=1 m=f b=1 B=0001030103010100 k=0 t=2 p=1
    G vs=fa3a619ff3892317 fs=906d96db9480c46d f=1 a=16 s=8/0 c=3f:3f d=0 n=1 m=f b=1 B=0005060506010100 k=0 t=2 p=1
    
  4. added
    log: okNewest attached log ends with a clean exit
    log: new shadersAttached log has shader variants the shipped list lacks
    on Nov 15, 2026
  5. peiikai commented on Nov 15, 2026

    @peiikai
    Owner

    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?

  6. Lex83nick commented on Nov 15, 2026

    @Lex83nick
    Author

    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.

  7. Lex83nick commented on Nov 15, 2026

    @Lex83nick
    Author

    Log showing a frame rate drop inside the dungeon that fails to return to normal values upon exiting.

    lasrecomp.log

  8. peiikai commented on Nov 15, 2026

    @peiikai
    Owner

    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.

  9. added
    status: investigatingWe're working on it: the ball is in our court
    and removed on Nov 15, 2026
  10. peiikai commented on Nov 15, 2026

    @peiikai
    Owner

    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.

  11. Lex83nick commented on Nov 15, 2026

    @Lex83nick
    Author

    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

  12. peiikai commented on Nov 15, 2026

    @peiikai
    Owner

    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.

  13. peiikai commented on Nov 15, 2026

    @peiikai
    Owner

    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.

  14. added
    status: test build outA test build or branch is out; waiting for a tester's result
    and removed
    status: investigatingWe're working on it: the ball is in our court
    on Nov 15, 2026
  15. martinkuhl commented on Nov 16, 2026

    @martinkuhl

    I have the same behavior on Android. Could you create a test build for the android to plattform?

  16. peiikai commented on Nov 16, 2026

    @peiikai
    Owner

    @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.

  17. martinkuhl commented on Nov 16, 2026

    @martinkuhl

    I am using an OnePlus Pad2 with an Adrino 750. I will add the logs later.

  18. Lex83nick commented on Nov 16, 2026

    @Lex83nick
    Author

    • 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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    log: new shadersAttached log has shader variants the shipped list lackslog: okNewest attached log ends with a clean exitstatus: test build outA test build or branch is out; waiting for a tester's result

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions