mirror of
https://github.com/tangerineturtle1/NX2navi.git
synced 2026-11-18 13:09:57 -04:00
Describe the frame pacer, the one-limiter rule and RivaTuner Statistics Server as they behave now.
docs/architecture.md mentioned the pacer only inside its low latency paragraph and RTSS nowhere. It now has the pacer (the limit counting drawn frames, the 240 ceiling, movie rates, the slots and their catch-up, the present thread's wait and pace_smooth, the acquire's waits, the step snapped to the paced rate), the one-limiter rule as the goal with the exceptions that stand today (pace_smooth under RTSS, DLSS Frame Generation's Reflex beside the pacer, no limit at all from the pacer while RTSS holds it through movies and windows with no present, a limit set in RTSS itself while RTSS is kept out), RTSS's part (the lookup on its thread, the profile write and read-back, when the pacer stands aside and when it keeps the limit, the kept-out runs that only read RTSS's settings, the restore on orderly exits and what a kill leaves), and how to measure pacing (the present and perf traces, perf_summary, PresentMon as the reference, the runtime's own hitches). The changes that wait for approval are not described as done. nx2navi.ini.example's rtss paragraph adds low latency, and the second limiter a limit set in RTSS itself makes with rtss = 0, frame generation or low latency, which the log and the settings menu now point out. README.md's frame generation item ends its sentence on RTSS with what it does and the same note. Docs only; check_content passes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
@@ -25,9 +25,13 @@
|
||||
# fps_limit = 60
|
||||
# Where RivaTuner Statistics Server is installed and running, the limit goes into its profile for the game's
|
||||
# executable and RTSS does the limiting instead of the game; closing the game puts back what the profile held.
|
||||
# Changing that profile needs the game run as administrator (RTSS keeps its profiles under Program Files); without
|
||||
# it, or with frame generation on, the game limits by itself, and also when RTSS's own frame counter shows the game
|
||||
# well past the limit (RTSS then hooks the game without holding it back). rtss = 0 always leaves it to the game.
|
||||
# Changing that profile needs the game run as administrator (RTSS keeps its profiles under Program Files). Without it
|
||||
# the game limits by itself, as it does with frame generation on (RTSS would count the generated frames) and for the
|
||||
# rest of the run when RTSS's own frame counter shows the game well past the limit (RTSS then hooks the game without
|
||||
# holding it back); with low latency on, the driver holds the limit. rtss = 0 always leaves it to the game. With
|
||||
# rtss = 0, frame generation or low latency, a limit set in RTSS itself (its global profile or the game's, a frame time
|
||||
# limit or scanline sync) limits the game a second time: the log and the settings menu say so, and setting it to 0 in
|
||||
# RTSS leaves one limiter.
|
||||
# rtss = 1
|
||||
# 1: asks RTSS's EnumProfiles whether the game's profile exists, instead of looking for its file. EnumProfiles crashes
|
||||
# the game (RTSS keeps a pointer of the game's in 32 bits); only for testing an RTSS that fixed it.
|
||||
|
||||
Reference in New Issue
Block a user