From 2150458a0144895db871f5f8d90ab800e5c4380d Mon Sep 17 00:00:00 2001 From: chrg6 Date: Fri, 13 Nov 2026 17:53:23 -0500 Subject: [PATCH] Pass the unlimited frame rate's RivaTuner Statistics Server want as it is. The review found that frame_rate.c frame_step_cap_ns's unlimited branch handed rtss_limit_want "rtss_out ? rtss_out : 0", which is rtss_out itself: a kept-out reason (RTSS_OUT_*), or 0, which clears RTSS's limit. It now passes rtss_out, and the comment says what each value does. Same want, same code: frame_rate.c compiles, check_content passes. Co-Authored-By: Claude Opus 5.5 --- runtime/frame_rate.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/runtime/frame_rate.c b/runtime/frame_rate.c index f91f65ed..933d3105 100644 --- a/runtime/frame_rate.c +++ b/runtime/frame_rate.c @@ -309,8 +309,8 @@ uint64_t frame_step_cap_ns(void) { else rt_log("frame rate: the movie ended: the frame limit again"); } } - if (limit_hz == -2 && !movie_hz && !frame_free_running()) { // unlimited: the pacer does not hold frames, and - rtss_limit_want(rtss_out ? rtss_out : 0); // RTSS's limit is cleared + if (limit_hz == -2 && !movie_hz && !frame_free_running()) { // unlimited: the pacer does not hold frames + rtss_limit_want(rtss_out); // kept out (RTSS_OUT_*), or 0: RTSS's limit is cleared paced_hz = 0; return 0; }