The FPS cap does not appear to be working correctly #1650

Closed

opened 2026-11-10 12:10:16 +00:00 by Angeluz01 · 2 comments

Angeluz01 commented

2026-11-10 12:10:16 +00:00

(Migrated from github.com)

The idea

The FPS cap does not appear to be working correctly. I set the frame rate limit to 60 FPS, but the game still runs at 120 FPS when using Frame Generation ×2. It should be running at 30 FPS internally, with Frame Generation ×2 producing a 60 FPS output, not 120 FPS.

This is especially important for users playing on TVs that only support V-Sync and do not have G-SYNC or VRR. A functioning FPS cap is necessary to maintain smooth frame pacing and prevent unnecessary frame generation

Anything else

No response

### The idea The FPS cap does not appear to be working correctly. I set the frame rate limit to 60 FPS, but the game still runs at 120 FPS when using Frame Generation ×2. It should be running at 30 FPS internally, with Frame Generation ×2 producing a 60 FPS output, not 120 FPS. This is especially important for users playing on TVs that only support V-Sync and do not have G-SYNC or VRR. A functioning FPS cap is necessary to maintain smooth frame pacing and prevent unnecessary frame generation ### Anything else _No response_

gabrielfnatic1542-commits commented

2026-11-10 17:38:45 +00:00

(Migrated from github.com)

Same here on an AMD RX 6750 XT.

Setting Game frame rate cap to 60 in the Insert/F1 Graphics menu does not keep FPS at 60. The cap should be respected whether Frame generation is on or off: if I set 60, FPS should stay at 60. With Frame generation enabled it currently goes above the cap (the ×2 path produces 120 instead of staying at the selected limit).

Happy to test a fix on this GPU.

Same here on an AMD RX 6750 XT. Setting Game frame rate cap to 60 in the Insert/F1 Graphics menu does not keep FPS at 60. The cap should be respected whether Frame generation is on or off: if I set 60, FPS should stay at 60. With Frame generation enabled it currently goes above the cap (the ×2 path produces 120 instead of staying at the selected limit). Happy to test a fix on this GPU.

NotRexed commented

2026-11-11 21:23:17 +00:00

(Migrated from github.com)

Thanks for the report. Reports of the same problem are now collected in #2510, which lists this one with your details and links back here, so one fix closes them together and the open list stays readable. Follow #2510 for the fix, and add new details there (or here). If this turns out to be a separate problem it will be reopened.

Commenting is not possible because the repository is archived.