feat(menu): add a 45 FPS game frame rate cap #1585

Open
SonnikBoom wants to merge 4 commits from SonnikBoom/Longshot:feat/45-fps-cap into main
First-time contributor

Type: feat · Risk: low · Tested on: CachyOS, RX 9070 XT · Needs: Windows in-game check

TL;DR

Players can choose 45 FPS under Graphics → Game frame rate cap. In two runs in Kokiri Forest, the game averaged 44.999 and 45.000 FPS at normal game speed. The 60 FPS choice averaged 60 FPS on both builds.

Breakdown

  • Who it helps: Players who want a cap between 30 and 60 FPS.
  • What was wrong: The cap selector jumped from 30 to 60 FPS.
  • What changes: One step up from 30 selects 45 FPS, with real-time game speed.
  • What does not change: The default is 60 FPS and existing saved cap IDs still select their original rates.
  • How it was checked: Two interleaved comparisons in Kokiri Forest, a one-step menu check, a restart check and the game-free suite.
  • What is still open: In-game testing on Windows and with V-Sync enabled.
  • Risk: Low. The low-cap path also handles in-game display intervals and game-clock stepping.

Why

The jump from 30 straight to 60 FPS leaves players without a 45 FPS option. A cap at 45 gives players who can sustain that rate another choice. The broader request for more cap options is #1079.

What changed

45 FPS sits between 30 and 60 in the selector. The host paces its own frames at that rate and keeps the game clock in real time, including with Game speed set to Per frame.

  • In gpu/vk/vk_menu.cpp, tx_fps_cap shows 45, set_row cycles the choices in FPS order, and menu_setting_set accepts the saved cap ID directly.
  • In host/nn_vi.c, fps_refresh resolves the menu selection or the per-run override. hos_vi_native_interval and realtime_step apply the sub-60 display period and game-clock stepping.
  • gpu/vk/fps_stats.h accepts 45 for the FPS display. The game-free checks cover cap mapping, stepping, the frame generation preset path and the counter.
  • The Graphics guide illustration was inspected against both UI-only builds. The 60 FPS default and the navigation shown there match the current menu. The manifest records the reviewed source inputs. The screenshots below are from the running game.

Measurements

Verdict: The 45 FPS cap averaged 45.00 FPS with a median interval of 22.22 ms and a 1.000× game clock. At the default 60 FPS cap, both builds averaged 60 FPS. The patch's p99 was 0.95 ms and 0.46 ms higher in the two matched 60 FPS pairs.

Hardware: Ryzen 7 9800X3D, 64 GB RAM, Radeon RX 9070 XT 16 GB, Mesa RADV 26.2.6, CachyOS kernel 7.3.4-1-cachyos, KDE Plasma 6.8.2 Wayland.

Scene: Kokiri Forest with the repository's Kokiri-start save, 1920×1080 game output, SDR, game's own upscaler, frame generation and V-Sync off, Game speed Per frame. The Wayland swapchain was 1600×900 for both members of pair 1 and 1280×720 for both members of pair 2.

Method: Both Linux Release builds used the same compiler, sysroot and compilation flags. On each launch, a 250-frame camera sweep warmed the scene before a 20-second standing sample. The order was main, patch, main, patch. On each patch run, a second standing sample followed the live switch from 60 to 45 FPS. HOS_PRESENT_TRACE provides host present-return intervals. HOS_FPS_LOG records game-clock speed. Physical display timing was outside this test. 0f529cc is the tested code revision. Later commits record this comparison and update the guide.

How to reproduce: Load Kokiri-start, set the options above, leave HOS_FPS_MAX unset and enable HOS_PRESENT_TRACE and HOS_FPS_LOG. Warm the scene, record 20 seconds at 60 FPS, then select 45 FPS on the patch build and record another 20 seconds.

Measure Before: main @ 430eef4 After: this PR @ 0f529cc (60 FPS) After: this PR @ 0f529cc (45 FPS)
FPS, pair 1 / pair 2 60.000 / 60.000 59.998 / 60.000 44.999 / 45.000
Median present interval, pair 1 / pair 2 16.662 / 16.667 ms 16.666 / 16.665 ms 22.223 / 22.215 ms
P99 present interval, pair 1 / pair 2 17.332 / 17.459 ms 18.277 / 17.921 ms 22.515 / 22.515 ms
Median FPS across runs 60.00 60.00 45.00
Median of the runs' median intervals 16.66 ms 16.67 ms 22.22 ms
Game-clock speed, all sampled readings 1.000× 1.000× 1.000×
main 1 at 60:  vi: game clock 3864.8: 60.00 a second of wall time (speed 1.000) at 60.0 fps; now_ns=24984702291352
patch 1 at 60: vi: game clock 3870.4: 60.00 a second of wall time (speed 1.000) at 60.0 fps; now_ns=25057533213891
patch 1 at 45: vi: game clock 5386.3: 60.00 a second of wall time (speed 1.000) at 45.0 fps; now_ns=25082816656768
main 2 at 60:  vi: game clock 3869.5: 60.00 a second of wall time (speed 1.000) at 60.0 fps; now_ns=25157673182162
patch 2 at 60: vi: game clock 3848.3: 60.00 a second of wall time (speed 1.000) at 60.0 fps; now_ns=25228797340695
patch 2 at 45: vi: game clock 5393.2: 60.00 a second of wall time (speed 1.000) at 45.0 fps; now_ns=25254563990904

Both captures show one Right press from 30 FPS on the same Graphics menu row. The capture size is 1280×720, with the same test save and graphics settings.

Before: main @ 430eef4, one step from 30 selects 60 FPS

After: this PR @ 0f529cc, one step from 30 selects 45 FPS

Flags and settings

45 FPS is an opt-in menu choice and per-run override.

Flag What it is Before this PR After this PR Effect Helps / doesn't help / untested Recommendation
Game frame rate cap Graphics menu row 30, 60 and higher choices. Default 60. Adds 45 between 30 and 60. Default 60. Applies a 45 FPS game-render cap in play. Tested with V-Sync and frame generation off. Select 45 when you want that cap.
frame_rate_cap Saved option in longshot_options.ini -1 for 30, 0 for 60, 1–6 for the higher choices. Adds -2 for 45. Restores 45 on startup when selected. Checked by relaunching the isolated test profile. Set through the menu.
HOS_FPS_MAX Per-run override 30, 60 and values from 61 to 1000. Also accepts 45. Takes precedence over the menu for that run. Covered by the host cap logic checks. Leave unset for normal play.

Testing

Tested: On CachyOS with the RX 9070 XT, loaded Kokiri Forest, selected 45 FPS in play and checked the host presents and game-clock rate. Pressing Right from 30 selected 45 in the patched Graphics menu. Restarting the test profile loaded 45 FPS and the live selector accepted 60, 30 and 45. The Longshot guide source check and the measured-configuration format check passed.

python -I -B tests/run_all.py on Linux reported 718 passed, 45 failed and 17 skipped on main, and 718 passed, 45 failed and 17 skipped on this branch.

45 checks failing on both commits
  • tests/test_bug_report.py
  • tests/test_bug_report_defaults.py
  • tests/test_capture_readback_visibility.py
  • tests/test_cpu_report.py
  • tests/test_crash_groups.py
  • tests/test_crash_record.py
  • tests/test_crt_options.py
  • tests/test_damage_debug_menu.py
  • tests/test_dev_packs.py
  • tests/test_display_startup_failure.py
  • tests/test_dlss_feature_size.py
  • tests/test_draw_stream_visibility.py
  • tests/test_failed_compile_keeps_objects.py
  • tests/test_fsr_image_retirement.py
  • tests/test_fsr_uniform_ownership.py
  • tests/test_guest_imported.py
  • tests/test_hardware_report.py
  • tests/test_hud_layout_row.py
  • tests/test_invalidate_quick.py
  • tests/test_invalidate_vcore.py
  • tests/test_libc_hooks.py
  • tests/test_linux_preflight.py
  • tests/test_linux_pressure.py
  • tests/test_linux_update.py
  • tests/test_log_open_failure.py
  • tests/test_mirror_budget.py
  • tests/test_missing_nup.py
  • tests/test_mods_size_table.py
  • tests/test_nonuniform_image_arrays.py
  • tests/test_parallel_init_order.py
  • tests/test_pending_guest_import.py
  • tests/test_pipeline_play_cache.py
  • tests/test_present_source_crop.py
  • tests/test_present_thread.py
  • tests/test_profiling_mode.py
  • tests/test_psychov35_fsr3_fg.py
  • tests/test_readback_timeout_source.py
  • tests/test_replay_write_order.py
  • tests/test_run_all_changed.py
  • tests/test_slow_frames.py
  • tests/test_staging_burst.py
  • tests/test_switch_table.py
  • tests/test_upscaler_rows.py
  • tests/test_vk_occlusion_queries.py
  • tests/test_walk_key.py

The Windows x64 cross-build with llvm-mingw 20261104 produced the host executable and Vulkan DLL from a build directory with a non-ASCII name.

Not tested: Windows gameplay, V-Sync on and frame generation on. The measurements cover standing gameplay in Kokiri Forest.

Must be tested:

  • Windows, any supported GPU: load a save, cycle 30 → 45 → 60 in Graphics, and relaunch with 45 selected, expecting it to persist and the game to run at real time near 45 FPS with frame generation off. Repeat with a display mode and V-Sync setting that can present at 45 FPS (by hand: check the selection and the game FPS counter).

Risks

What could break: Low-cap pacing, game speed or restoration of the prior timing preference on switching back to 60. At 60 FPS, the two short runs show a p99 increase of 0.95 ms and 0.46 ms with the same average FPS. The samples establish the cap behavior and quantify the observed tail difference. They are too short to identify its cause.

Turning it off: Choose 60 FPS in Graphics and clear any per-run HOS_FPS_MAX=45 override.

Compatibility: The existing save format, pipeline and shader-cache formats, renderer ABI and builder tooling apply to both builds. vk_api.h documents the existing option ID 53. The options file uses a new cap ID, -2, for 45. Select 60 before switching to an older build if you want that build to restore 60.

Issues

Fixes #1548.

See #1079.

Checklist

Everyone

  • One topic.
  • The title is a Conventional Commit (type(scope): description) of the status line's type.
  • Why gives the reason plainly and links the issues that fit (the tracker searched).
  • Tested on my own PC where it runs (in the game, for a change the game runs), as Testing's Tested says; what
    can't be run by hand is in Testing's Not testable by hand, with why.
  • Measurements has a verdict, or one line saying why there is nothing to measure.
  • Nothing gets worse that I know of: any cost (speed, latency, memory, a setup that worked before) is measured and
    in Risks.
  • Testing names what was tested, what wasn't, and what must still be tested, where and how.
  • Rebased on current main.
  • python -I -B tests/run_all.py passes (any failure that also fails on main is named).
  • No game files, dumps, build output or generated files.
  • third_party/ untouched (a new folder with a PROVENANCE.md instead).
  • The license is OK: GPL-3.0-or-later, nothing incompatible and nothing decompiled.

When it applies

  • AI assistance recorded with Assisted-by: / Co-Authored-By: trailers.
  • Numbers from the same PC, scene and settings, at least 2 interleaved runs each, the median reported.
  • Switches documented (docs/development.md; the README for a menu row) and shipped at their recommended value.
  • Screenshots of the same spot, captioned like the Measurements columns, for a change that shows on screen.
  • A file in docs/tested/ for each new measured run (format in docs/tested-configurations.md).
  • A check under tests/ that reads changed source updated in this PR, not weakened.
  • Host code builds on both Windows (llvm-mingw) and Linux, with UTF-8 paths.
  • Docs updated.
**Type:** feat · **Risk:** low · **Tested on:** CachyOS, RX 9070 XT · **Needs:** Windows in-game check ## TL;DR Players can choose 45 FPS under **Graphics → Game frame rate cap**. In two runs in Kokiri Forest, the game averaged 44.999 and 45.000 FPS at normal game speed. The 60 FPS choice averaged 60 FPS on both builds. ## Breakdown - **Who it helps:** Players who want a cap between 30 and 60 FPS. - **What was wrong:** The cap selector jumped from 30 to 60 FPS. - **What changes:** One step up from 30 selects 45 FPS, with real-time game speed. - **What does not change:** The default is 60 FPS and existing saved cap IDs still select their original rates. - **How it was checked:** Two interleaved comparisons in Kokiri Forest, a one-step menu check, a restart check and the game-free suite. - **What is still open:** In-game testing on Windows and with V-Sync enabled. - **Risk:** Low. The low-cap path also handles in-game display intervals and game-clock stepping. ## Why The jump from 30 straight to 60 FPS leaves players without a 45 FPS option. A cap at 45 gives players who can sustain that rate another choice. The broader request for more cap options is #1079. ## What changed 45 FPS sits between 30 and 60 in the selector. The host paces its own frames at that rate and keeps the game clock in real time, including with Game speed set to Per frame. - In `gpu/vk/vk_menu.cpp`, `tx_fps_cap` shows 45, `set_row` cycles the choices in FPS order, and `menu_setting_set` accepts the saved cap ID directly. - In `host/nn_vi.c`, `fps_refresh` resolves the menu selection or the per-run override. `hos_vi_native_interval` and `realtime_step` apply the sub-60 display period and game-clock stepping. - `gpu/vk/fps_stats.h` accepts 45 for the FPS display. The game-free checks cover cap mapping, stepping, the frame generation preset path and the counter. - The Graphics guide illustration was inspected against both UI-only builds. The 60 FPS default and the navigation shown there match the current menu. The manifest records the reviewed source inputs. The screenshots below are from the running game. ## Measurements **Verdict:** The 45 FPS cap averaged 45.00 FPS with a median interval of 22.22 ms and a 1.000× game clock. At the default 60 FPS cap, both builds averaged 60 FPS. The patch's p99 was 0.95 ms and 0.46 ms higher in the two matched 60 FPS pairs. Hardware: Ryzen 7 9800X3D, 64 GB RAM, Radeon RX 9070 XT 16 GB, Mesa RADV 26.2.6, CachyOS kernel `7.3.4-1-cachyos`, KDE Plasma 6.8.2 Wayland. Scene: Kokiri Forest with the repository's Kokiri-start save, 1920×1080 game output, SDR, game's own upscaler, frame generation and V-Sync off, Game speed Per frame. The Wayland swapchain was 1600×900 for both members of pair 1 and 1280×720 for both members of pair 2. Method: Both Linux Release builds used the same compiler, sysroot and compilation flags. On each launch, a 250-frame camera sweep warmed the scene before a 20-second standing sample. The order was main, patch, main, patch. On each patch run, a second standing sample followed the live switch from 60 to 45 FPS. `HOS_PRESENT_TRACE` provides host present-return intervals. `HOS_FPS_LOG` records game-clock speed. Physical display timing was outside this test. `0f529cc` is the tested code revision. Later commits record this comparison and update the guide. How to reproduce: Load Kokiri-start, set the options above, leave `HOS_FPS_MAX` unset and enable `HOS_PRESENT_TRACE` and `HOS_FPS_LOG`. Warm the scene, record 20 seconds at 60 FPS, then select 45 FPS on the patch build and record another 20 seconds. | Measure | Before: main @ 430eef4 | After: this PR @ 0f529cc (60 FPS) | After: this PR @ 0f529cc (45 FPS) | |---|---:|---:|---:| | FPS, pair 1 / pair 2 | 60.000 / 60.000 | 59.998 / 60.000 | 44.999 / 45.000 | | Median present interval, pair 1 / pair 2 | 16.662 / 16.667 ms | 16.666 / 16.665 ms | 22.223 / 22.215 ms | | P99 present interval, pair 1 / pair 2 | 17.332 / 17.459 ms | 18.277 / 17.921 ms | 22.515 / 22.515 ms | | Median FPS across runs | 60.00 | 60.00 | 45.00 | | Median of the runs' median intervals | 16.66 ms | 16.67 ms | 22.22 ms | | Game-clock speed, all sampled readings | 1.000× | 1.000× | 1.000× | ```text main 1 at 60: vi: game clock 3864.8: 60.00 a second of wall time (speed 1.000) at 60.0 fps; now_ns=24984702291352 patch 1 at 60: vi: game clock 3870.4: 60.00 a second of wall time (speed 1.000) at 60.0 fps; now_ns=25057533213891 patch 1 at 45: vi: game clock 5386.3: 60.00 a second of wall time (speed 1.000) at 45.0 fps; now_ns=25082816656768 main 2 at 60: vi: game clock 3869.5: 60.00 a second of wall time (speed 1.000) at 60.0 fps; now_ns=25157673182162 patch 2 at 60: vi: game clock 3848.3: 60.00 a second of wall time (speed 1.000) at 60.0 fps; now_ns=25228797340695 patch 2 at 45: vi: game clock 5393.2: 60.00 a second of wall time (speed 1.000) at 45.0 fps; now_ns=25254563990904 ``` Both captures show one Right press from 30 FPS on the same Graphics menu row. The capture size is 1280×720, with the same test save and graphics settings. ![Before: main @ 430eef4, one step from 30 selects 60 FPS](https://git.magicbean.dev/attachments/c23cd2ec-5c19-4841-99e2-0ec5780b7641) ![After: this PR @ 0f529cc, one step from 30 selects 45 FPS](https://git.magicbean.dev/attachments/db1e04a0-486d-48f6-81a6-a08187282cf7) ### Flags and settings 45 FPS is an opt-in menu choice and per-run override. | Flag | What it is | Before this PR | After this PR | Effect | Helps / doesn't help / untested | Recommendation | |---|---|---|---|---|---|---| | Game frame rate cap | Graphics menu row | 30, 60 and higher choices. Default 60. | Adds 45 between 30 and 60. Default 60. | Applies a 45 FPS game-render cap in play. | Tested with V-Sync and frame generation off. | Select 45 when you want that cap. | | `frame_rate_cap` | Saved option in `longshot_options.ini` | `-1` for 30, `0` for 60, `1`–`6` for the higher choices. | Adds `-2` for 45. | Restores 45 on startup when selected. | Checked by relaunching the isolated test profile. | Set through the menu. | | `HOS_FPS_MAX` | Per-run override | 30, 60 and values from 61 to 1000. | Also accepts 45. | Takes precedence over the menu for that run. | Covered by the host cap logic checks. | Leave unset for normal play. | ## Testing **Tested:** On CachyOS with the RX 9070 XT, loaded Kokiri Forest, selected 45 FPS in play and checked the host presents and game-clock rate. Pressing Right from 30 selected 45 in the patched Graphics menu. Restarting the test profile loaded 45 FPS and the live selector accepted 60, 30 and 45. The Longshot guide source check and the measured-configuration format check passed. `python -I -B tests/run_all.py` on Linux reported 718 passed, 45 failed and 17 skipped on main, and 718 passed, 45 failed and 17 skipped on this branch. <details> <summary>45 checks failing on both commits</summary> - `tests/test_bug_report.py` - `tests/test_bug_report_defaults.py` - `tests/test_capture_readback_visibility.py` - `tests/test_cpu_report.py` - `tests/test_crash_groups.py` - `tests/test_crash_record.py` - `tests/test_crt_options.py` - `tests/test_damage_debug_menu.py` - `tests/test_dev_packs.py` - `tests/test_display_startup_failure.py` - `tests/test_dlss_feature_size.py` - `tests/test_draw_stream_visibility.py` - `tests/test_failed_compile_keeps_objects.py` - `tests/test_fsr_image_retirement.py` - `tests/test_fsr_uniform_ownership.py` - `tests/test_guest_imported.py` - `tests/test_hardware_report.py` - `tests/test_hud_layout_row.py` - `tests/test_invalidate_quick.py` - `tests/test_invalidate_vcore.py` - `tests/test_libc_hooks.py` - `tests/test_linux_preflight.py` - `tests/test_linux_pressure.py` - `tests/test_linux_update.py` - `tests/test_log_open_failure.py` - `tests/test_mirror_budget.py` - `tests/test_missing_nup.py` - `tests/test_mods_size_table.py` - `tests/test_nonuniform_image_arrays.py` - `tests/test_parallel_init_order.py` - `tests/test_pending_guest_import.py` - `tests/test_pipeline_play_cache.py` - `tests/test_present_source_crop.py` - `tests/test_present_thread.py` - `tests/test_profiling_mode.py` - `tests/test_psychov35_fsr3_fg.py` - `tests/test_readback_timeout_source.py` - `tests/test_replay_write_order.py` - `tests/test_run_all_changed.py` - `tests/test_slow_frames.py` - `tests/test_staging_burst.py` - `tests/test_switch_table.py` - `tests/test_upscaler_rows.py` - `tests/test_vk_occlusion_queries.py` - `tests/test_walk_key.py` </details> The Windows x64 cross-build with llvm-mingw 20261104 produced the host executable and Vulkan DLL from a build directory with a non-ASCII name. **Not tested:** Windows gameplay, V-Sync on and frame generation on. The measurements cover standing gameplay in Kokiri Forest. **Must be tested:** - Windows, any supported GPU: load a save, cycle 30 → 45 → 60 in Graphics, and relaunch with 45 selected, expecting it to persist and the game to run at real time near 45 FPS with frame generation off. Repeat with a display mode and V-Sync setting that can present at 45 FPS (by hand: check the selection and the game FPS counter). ## Risks **What could break:** Low-cap pacing, game speed or restoration of the prior timing preference on switching back to 60. At 60 FPS, the two short runs show a p99 increase of 0.95 ms and 0.46 ms with the same average FPS. The samples establish the cap behavior and quantify the observed tail difference. They are too short to identify its cause. **Turning it off:** Choose 60 FPS in Graphics and clear any per-run `HOS_FPS_MAX=45` override. **Compatibility:** The existing save format, pipeline and shader-cache formats, renderer ABI and builder tooling apply to both builds. `vk_api.h` documents the existing option ID 53. The options file uses a new cap ID, `-2`, for 45. Select 60 before switching to an older build if you want that build to restore 60. ## Issues Fixes #1548. See #1079. ## Checklist ### Everyone - [x] One topic. - [x] The title is a Conventional Commit (`type(scope): description`) of the status line's type. - [x] Why gives the reason plainly and links the issues that fit (the tracker searched). - [x] Tested on my own PC where it runs (in the game, for a change the game runs), as Testing's Tested says; what can't be run by hand is in Testing's Not testable by hand, with why. - [x] Measurements has a verdict, or one line saying why there is nothing to measure. - [x] Nothing gets worse that I know of: any cost (speed, latency, memory, a setup that worked before) is measured and in Risks. - [x] Testing names what was tested, what wasn't, and what must still be tested, where and how. - [x] Rebased on current `main`. - [x] `python -I -B tests/run_all.py` passes (any failure that also fails on `main` is named). - [x] No game files, dumps, build output or generated files. - [x] `third_party/` untouched (a new folder with a `PROVENANCE.md` instead). - [x] The license is OK: GPL-3.0-or-later, nothing incompatible and nothing decompiled. ### When it applies - [x] AI assistance recorded with `Assisted-by:` / `Co-Authored-By:` trailers. - [x] Numbers from the same PC, scene and settings, at least 2 interleaved runs each, the median reported. - [x] Switches documented (docs/development.md; the README for a menu row) and shipped at their recommended value. - [x] Screenshots of the same spot, captioned like the Measurements columns, for a change that shows on screen. - [x] A file in `docs/tested/` for each new measured run (format in `docs/tested-configurations.md`). - [x] A check under `tests/` that reads changed source updated in this PR, not weakened. - [x] Host code builds on both Windows (llvm-mingw) and Linux, with UTF-8 paths. - [x] Docs updated.
Keep the existing saved cap IDs and apply real-time game speed at 45 FPS.

Assisted-by: OpenAI Codex
Co-Authored-By: Codex <[email protected]>
Assisted-by: OpenAI Codex
Co-Authored-By: Codex <[email protected]>
Assisted-by: OpenAI Codex
Co-Authored-By: Codex <[email protected]>
test(menu): cover the absolute frame generation setter
Some checks are pending
CI / Conventional Commit title (pull_request) Blocked by required conditions
CI / Python source checks (ubuntu-24.04, part 1/2) (pull_request) Blocked by required conditions
CI / Python source checks (ubuntu-24.04, part 2/2) (pull_request) Blocked by required conditions
CI / SPIR-V fixtures (global narrow load/store, direct surface atomics, F2I immediate) (pull_request) Blocked by required conditions
CI / Workflow lint (actionlint) (pull_request) Blocked by required conditions
Guide screenshots / Guide images and local UI source review (pull_request) Blocked by required conditions
Third-party parts / As their notes say (pull_request) Blocked by required conditions
Third-party parts / The same as upstream (pull_request) Blocked by required conditions
Website / Website on Cloudflare (pull_request) Blocked by required conditions
Website / Website on Cloudflare (pull_request_target) Has been skipped
PR description / Description follows the template (pull_request_target) Successful in 4s
5cb6e104b3
Assisted-by: OpenAI Codex
Co-Authored-By: Codex <[email protected]>
Author
First-time contributor

Tested in game: CachyOS (KDE Wayland), Radeon RX 9070 XT with Mesa RADV 26.2.6: in Kokiri Forest the 45 FPS cap measured 44.999 and 45.000 FPS at normal game speed. The test save loaded on restart with 45 FPS still selected.

Tested in game: CachyOS (KDE Wayland), Radeon RX 9070 XT with Mesa RADV 26.2.6: in Kokiri Forest the 45 FPS cap measured 44.999 and 45.000 FPS at normal game speed. The test save loaded on restart with 45 FPS still selected.
SonnikBoom changed title from WIP: feat(menu): add a 45 FPS game frame rate cap to feat(menu): add a 45 FPS game frame rate cap 2026-11-18 14:20:46 +00:00
Some checks are pending
CI / Conventional Commit title (pull_request) Blocked by required conditions
CI / Python source checks (ubuntu-24.04, part 1/2) (pull_request) Blocked by required conditions
CI / Python source checks (ubuntu-24.04, part 2/2) (pull_request) Blocked by required conditions
CI / SPIR-V fixtures (global narrow load/store, direct surface atomics, F2I immediate) (pull_request) Blocked by required conditions
CI / Workflow lint (actionlint) (pull_request) Blocked by required conditions
Guide screenshots / Guide images and local UI source review (pull_request) Blocked by required conditions
Third-party parts / As their notes say (pull_request) Blocked by required conditions
Third-party parts / The same as upstream (pull_request) Blocked by required conditions
Website / Website on Cloudflare (pull_request) Blocked by required conditions
Website / Website on Cloudflare (pull_request_target) Has been skipped
PR description / Description follows the template (pull_request_target) Successful in 4s
This pull request doesn't have enough approvals yet. 0 of 1 approvals granted.
Some workflows are waiting to be reviewed.
This branch is out-of-date with the base branch
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u 'feat/45-fps-cap:SonnikBoom-feat/45-fps-cap'
git switch 'SonnikBoom-feat/45-fps-cap'
Sign in to join this conversation.
No reviewers
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!1585
No description provided.