Fullscreen + frame generation: output capped at 60 fps on a 280 Hz monitor (game drops to ~30 fps with 2x, 20 fps with 3x) #755

Closed
opened 2026-11-08 20:00:37 +00:00 by AlvaroSBernucci · 1 comment
AlvaroSBernucci commented 2026-11-08 20:00:37 +00:00 (Migrated from github.com)

Hookshot version

v2.0.3 (also seen on v2.0.2)

What kind of problem

Performance

What happened

With frame generation on, fullscreen caps the output at 60 fps although the monitor runs at 280 Hz, so the game's own rate drops to 60 ÷ the multiplier. Windowed mode has no such cap.

Same spot in Kokiri Forest, v2.0.3 (game rate from the FPS counter and hookshot_log.txt):

Mode Frame generation Shown Game
Windowed Off – ~41
Fullscreen Off – ~41
Windowed 2x – ~40
Fullscreen 2x 60 29–31
Fullscreen 3x 60 20

Fullscreen with 3x (v2.0.3):

vk: frame interpolation: 0 frames shown on time, 300 late (over 2 ms); shown apart: <7 ms 0, 7-9 0, 9-12 0, 12-17 299, 17-25 1, over 25 0

Windowed with 3x, light screen (v2.0.2):

vk: frame interpolation: 870 frames shown on time, 3 late (over 2 ms); shown apart: <7 ms 849, 7-9 17, 9-12 3, 12-17 0, 17-25 2, over 25 2

So in fullscreen each present appears to take ~16.7 ms. With 3x, a game frame then takes 3 × 16.7 = 50 ms, which is exactly the 20.0 fps I see. Frame pacing Off made no difference (v2.0.2).

What I checked:

  • The swapchain is immediate (log).
  • The driver's Wait for Vertical Refresh is at its default (VSyncControl=1, off unless the application specifies).
  • No Radeon Chill or FRTC, and no Adrenalin profile for hookshot.exe.

Expected: fullscreen as fast as windowed.

Where in the game

Kokiri Forest, standing still. Also on the pause screen (v2.0.2, 3x): 60 fps windowed against 20.0 fullscreen.

How often

Always, as soon as fullscreen (F11 or the menu) is on together with frame generation.

Graphics card and driver version

AMD Radeon RX 7600 8 GB, driver 32.0.32015.7029 (Vulkan 1.4). Monitors: 2560x1440 @ 280 Hz (primary, DisplayPort), 1920x1080 @ 144 Hz, 1920x1080 @ 60 Hz.

CPU, RAM and operating system

Ryzen 7 5700X, 48 GB DDR4, Windows 11 Pro 23H2.

Changes from the defaults

  • Insert menu as it is now: Frame generation 2x (varied for the test), Frame pacing On, Resolution 100%, Upscaling Lanczos, Sharpness 50%, Handheld profile On.
  • hookshot_env.txt: HOS_NO_RENDERER_WAIT=1 (for the black screen in #120) and HOS_PRESENT_NOWAIT=1. The second was only there in the v2.0.3 runs; the v2.0.2 runs had only the first.

Other software hooked into the game

No ReShade, shader-cache tools or frame-generation injectors.

hookshot_log.txt

The relevant lines are above. I can attach the full log if it helps.

Before you send it

  • I'm on the newest release, or the problem is still there on it.
  • I searched the open issues for this problem.
  • I'm not attaching game files, keys, hookshot.exe, the .bin caches or saves.
### Hookshot version v2.0.3 (also seen on v2.0.2) ### What kind of problem Performance ### What happened With frame generation on, fullscreen caps the output at 60 fps although the monitor runs at 280 Hz, so the game's own rate drops to 60 ÷ the multiplier. Windowed mode has no such cap. Same spot in Kokiri Forest, v2.0.3 (game rate from the FPS counter and `hookshot_log.txt`): | Mode | Frame generation | Shown | Game | |---|---|---|---| | Windowed | Off | – | ~41 | | Fullscreen | Off | – | ~41 | | Windowed | 2x | – | ~40 | | Fullscreen | 2x | 60 | 29–31 | | Fullscreen | 3x | 60 | 20 | Fullscreen with 3x (v2.0.3): ``` vk: frame interpolation: 0 frames shown on time, 300 late (over 2 ms); shown apart: <7 ms 0, 7-9 0, 9-12 0, 12-17 299, 17-25 1, over 25 0 ``` Windowed with 3x, light screen (v2.0.2): ``` vk: frame interpolation: 870 frames shown on time, 3 late (over 2 ms); shown apart: <7 ms 849, 7-9 17, 9-12 3, 12-17 0, 17-25 2, over 25 2 ``` So in fullscreen each present appears to take ~16.7 ms. With 3x, a game frame then takes 3 × 16.7 = 50 ms, which is exactly the 20.0 fps I see. Frame pacing Off made no difference (v2.0.2). What I checked: - The swapchain is `immediate` (log). - The driver's Wait for Vertical Refresh is at its default (`VSyncControl=1`, off unless the application specifies). - No Radeon Chill or FRTC, and no Adrenalin profile for hookshot.exe. Expected: fullscreen as fast as windowed. ### Where in the game Kokiri Forest, standing still. Also on the pause screen (v2.0.2, 3x): 60 fps windowed against 20.0 fullscreen. ### How often Always, as soon as fullscreen (F11 or the menu) is on together with frame generation. ### Graphics card and driver version AMD Radeon RX 7600 8 GB, driver 32.0.32015.7029 (Vulkan 1.4). Monitors: 2560x1440 @ 280 Hz (primary, DisplayPort), 1920x1080 @ 144 Hz, 1920x1080 @ 60 Hz. ### CPU, RAM and operating system Ryzen 7 5700X, 48 GB DDR4, Windows 11 Pro 23H2. ### Changes from the defaults - Insert menu as it is now: Frame generation 2x (varied for the test), Frame pacing On, Resolution 100%, Upscaling Lanczos, Sharpness 50%, Handheld profile On. - `hookshot_env.txt`: `HOS_NO_RENDERER_WAIT=1` (for the black screen in #120) and `HOS_PRESENT_NOWAIT=1`. The second was only there in the v2.0.3 runs; the v2.0.2 runs had only the first. ### Other software hooked into the game No ReShade, shader-cache tools or frame-generation injectors. ### hookshot_log.txt The relevant lines are above. I can attach the full log if it helps. ### Before you send it - [x] I'm on the newest release, or the problem is still there on it. - [x] I searched the open issues for this problem. - [x] I'm not attaching game files, keys, hookshot.exe, the .bin caches or saves.
NotRexed commented 2026-11-10 01:59:10 +00:00 (Migrated from github.com)

Closing this v2.0.3 report: frame generation and presentation have changed a lot since (frame pacing, the present path, frame generation Auto). If fullscreen with frame generation still caps at 60 on v2.0.11, please reopen with a hookshot_log.txt from that version.

Closing this v2.0.3 report: frame generation and presentation have changed a lot since (frame pacing, the present path, frame generation Auto). If fullscreen with frame generation still caps at 60 on v2.0.11, please reopen with a hookshot_log.txt from that version.
Commenting is not possible because the repository is archived.
No milestone
No assignees
1 participant
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/Hookshot#755
No description provided.