Make the frame limit count the frames the game draws, with frame generation on top.

The limit counted the frames on screen, so the game was paced at the limit over frame generation's multiplier: 60 at 4x drew 15 frames a second, and each step up of the multiplier took drawn frames away. Now a limit of 60 at 4x is 60 drawn and 240 shown. Only the display choice still counts the screen's frames, since a frame past the monitor's refresh is never seen, and with no limit set the default is 60 drawn rather than the monitor's rate.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
This commit is contained in:
chrg6
2026-11-10 11:48:24 -05:00
parent d4cf889a91
commit 63c7d3cb74
8 changed files with 66 additions and 65 deletions

View File

@@ -336,8 +336,7 @@ int ov_movie_live(void); // ov_movie2.c: a mov
int frame_limit_adjustable(void); // the frame limit setting changes the rate (always)
int frame_free_running(void); // no fps60/realtime patch set: the game steps by the clock
double frame_step_limit_hz(void); // the frame rate the limit gives (overlay); 0 unknown
double frame_step_game_hz(void); // ... over frame generation's factor: the game's rate
int frame_limit_follows_display(void); // no limit set and frame generation in use: the display's rate
double frame_step_game_hz(void); // the rate the game draws at under the limit; 0 unknown
// rtss_limit.c: RivaTuner Statistics Server takes the frame limit where it runs
void rtss_limit_want(int64_t mhz); // the pacer's limit in millihertz: >0, 0 none, -1 keep RTSS out
int rtss_limit_active(void); // RTSS limits to the wanted rate: the pacer holds no frames