Say what RivaTuner Statistics Server does with a movie at the default limit of 60, where the profile keeps the limit.

The review found that rtss_decide.h rtss_target writes no limit only while a movie runs faster than the play limit, so
at the default limit of 60 a 60 fps movie leaves 60 in RTSS's profile and RTSS holds the movie beside the game's pacer.
Its comment said RTSS at the movie's rate would space out the frames that catch up after a late frame, and README.md
("one limiter at a time") and docs/architecture.md read as if every movie under RTSS were the pacer's alone. The
approved rule writes nothing to the profile at movies when the limit is 60 or more, so the code stays: rtss_target's
and rtss_pace_period's comments now say that at the movie's own rate RTSS keeps holding it and that whether its
limiter lets the frames that catch up through is not measured, README.md drops "one limiter at a time", and
docs/architecture.md lists the movie at 60 among the exceptions to one limiter. tests/rtss_limit_check.c pins a movie
at 60 under a limit of 60: no write, the profile keeps 60, held again after it.

No behaviour changes. Checks that passed: tests/rtss_limit_check.py, tools/check_content.py --staged.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
chrg6
2026-11-13 19:40:16 -05:00
parent 80b96a748d
commit ad84e0a1c0
4 changed files with 33 additions and 14 deletions

View File

@@ -38,10 +38,10 @@ Report problems as issues, following [CONTRIBUTING.md](CONTRIBUTING.md).
display; in a window of another shape than the picture, frames are generated inside the picture only, so the black
bars stay clean. The frame limit counts the frames the game draws, and frame generation adds its
frames on top of it. The frame limit can also be
handed to RivaTuner Statistics Server, which then limits the game in its place: one limiter at a time, and the
game takes the limit back while a movie plays, while it is minimised and whenever RivaTuner is not seen holding it;
where frame generation or low latency keeps it out, the game says when a limit set in RivaTuner itself holds the
game as well
handed to RivaTuner Statistics Server, which then limits the game in its place once it is seen holding the game;
the game paces movies itself, and takes the limit back while it is minimised and whenever RivaTuner is not seen
holding it; where frame generation or low latency keeps it out, the game says when a limit set in RivaTuner itself
holds the game as well
- HDR on HDR displays, two kinds: the game's scene tone mapped to the display's peak, matched to the game's mid grey and tone, with true blacks, or the game's own native HDR; peak, game and HUD brightness in the menu
- The game's known shaders prepared when the game is built, and the pipelines met in play built again in the
background at each start, so play rarely stops to compile them; a shader or pipeline met for the first time can