fix(menu): distinguish game and generated frame rates #1659

Merged

bronze-ff merged 1 commit from fix/clarify-game-fps-cap into main

2026-11-10 12:47:53 +00:00

bronze-ff commented

2026-11-10 12:38:21 +00:00

(Migrated from github.com)

Summary

Addresses the confusing setting name reported in #1650. Rename Frame rate cap to Game frame rate cap and explain that generated frames are additional. The README shows how 60 rendered FPS with fixed 2x can produce up to 120 output FPS and describes Auto's existing refresh-rate target.

The menu continues reading and writing frame_rate_cap, which the host reads at startup. The change is to the label, help, and documentation. It does not add an output limiter.

Validation

The updated menu fixture fails on the old label and passes with the new label, the existing INI key, and the help text.
Five related tests passed with LLVM-MinGW on Windows and GCC/G++ on Linux: frame-generation presets, audio output, stick dead zone, rumble, and upscaler rows. The Vulkan menu translation unit passed a Windows syntax check.

## Summary Addresses the confusing setting name reported in #1650. Rename **Frame rate cap** to **Game frame rate cap** and explain that generated frames are additional. The README shows how 60 rendered FPS with fixed 2x can produce up to 120 output FPS and describes Auto's existing refresh-rate target. The menu continues reading and writing `frame_rate_cap`, which the host reads at startup. The change is to the label, help, and documentation. It does not add an output limiter. ## Validation - The updated menu fixture fails on the old label and passes with the new label, the existing INI key, and the help text. - Five related tests passed with LLVM-MinGW on Windows and GCC/G++ on Linux: frame-generation presets, audio output, stick dead zone, rumble, and upscaler rows. The Vulkan menu translation unit passed a Windows syntax check.