mirror of
https://github.com/tangerineturtle1/NX2navi.git
synced 2026-11-17 11:29:58 -04:00
Describe RivaTuner Statistics Server's hand-off, the pacer's fallbacks and rtss-profile.txt as they behave now.
docs/architecture.md said the pacer holds nothing while RTSS holds the limit, through movies and minimised windows, that the pacer stands aside once RTSS lists the process, that RTSS fails at 1.2 times the limit over six polls, and that a killed run leaves its limit for the next run to take as the player's. The one-limiter and RTSS paragraphs now name the pacer's fallbacks (before the first host present, a movie, 200 ms with no host present, a limiter seen letting frames through, any failure) and its 240 ceiling beside RTSS, the settle rule, a movie's profile, the proof RTSS must give before the pacer stands aside, the 1.05 rule over three new periods, the rounding down, and the state file with rtss_limit_crash. nx2navi.ini.example's rtss lines, README.md's frame generation item, docs/building.md's rtss_limit_check and frame_step_check paragraphs and rtss_limit.c's header follow, and the comments at main.c crash_handler's and dispatch.c fatal_end's rtss_limit_crash say when RTSS's library is still called there (no line in the state file, never on RTSS's own thread). No code changes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
@@ -123,8 +123,8 @@ static void fatal_end(int code, const char *fmt, va_list ap) {
|
||||
fs_save_crash_wait(); // a save the game already reported as done finishes first (bounded)
|
||||
prof_sampler_write(); // NX2NAVI_PROFILE: what was sampled until now, else a crash loses the whole profile
|
||||
// RivaTuner Statistics Server's profile goes back at the next start, from the line the run keeps for it in
|
||||
// rtss-profile.txt (rtss_limit.c rtss_limit_crash, as in main.c crash_handler): no call into RTSS's library here,
|
||||
// from any thread
|
||||
// rtss-profile.txt (rtss_limit.c rtss_limit_crash, as in main.c crash_handler), with no call into RTSS's library
|
||||
// here; only where that line could not be written is it put back now, and never from RTSS's own thread
|
||||
rtss_limit_crash();
|
||||
rt_rumble_stop_bounded(); // a controller on HD rumble: nothing renews or stops its vibration after the end
|
||||
// "frametime: at a fatal error" and the stutter map, the session's last period: after what a kill of the process
|
||||
|
||||
@@ -278,10 +278,10 @@ double frame_step_game_hz(void) {
|
||||
// frames only to LIMIT_FREE_MAX_HZ, the ceiling the game's code needs, so the two never stack, and it takes the limit
|
||||
// back once no picture went out for 200 ms (rtss_decide.h rtss_pace_period): a minimised window or a frame hold leaves
|
||||
// RTSS no present to hold. While a movie plays the pacer holds the movie's rate and keeps its slots whatever RTSS does.
|
||||
// NX2NAVI_RTSS=0 and frame generation (RTSS would count the generated frames) keep it
|
||||
// out, and so does a driver's low latency while it is in effect (vk_lowlat.c): the driver holds the limit where the
|
||||
// frame starts, and RTSS would hold the finished picture, the wait that mode is there to remove. RTSS gets the reason
|
||||
// (RTSS_OUT_*), for the log and for its check of a limit set in RTSS itself.
|
||||
// NX2NAVI_RTSS=0 and frame generation (RTSS would count the generated frames) keep it out, and so does a driver's low
|
||||
// latency while it is in effect (vk_lowlat.c): the driver holds the limit where the frame starts, and RTSS would hold
|
||||
// the finished picture, the wait that mode is there to remove. RTSS gets the reason (RTSS_OUT_*), for the log and for
|
||||
// its check of a limit set in RTSS itself.
|
||||
static double paced_hz; // the game frames a second the newest frame_step_cap_ns paces at (ocarina_step); 0: none
|
||||
static int movie_paced; // the movie rate the newest frame_step_cap_ns paces at (ocarina_step, frame_step_movie_hz); 0: none
|
||||
int frame_step_movie_hz(void) { return movie_paced; }
|
||||
|
||||
@@ -437,7 +437,8 @@ static void crash_handler(const PlatCrash *x) {
|
||||
kern_free_cores_note();
|
||||
fs_save_crash_wait(); // a save the game already reported as done finishes first (bounded; fs_host.c)
|
||||
// after the report: RivaTuner Statistics Server's profile goes back at the next start, from the line the run keeps
|
||||
// for it (rtss_limit.c rtss_limit_crash): no call into RTSS's library from a process that failed
|
||||
// for it in rtss-profile.txt (rtss_limit.c rtss_limit_crash), with no call into RTSS's library from a process that
|
||||
// failed; only where that line could not be written is it put back here, and never from RTSS's own thread
|
||||
rtss_limit_crash();
|
||||
rt_rumble_stop_bounded(); // a controller on HD rumble stops (dispatch.c: 300 ms at most, SDL may be the crash)
|
||||
fflush(stderr);
|
||||
|
||||
@@ -1,6 +1,7 @@
|
||||
// RivaTuner Statistics Server as the frame limiter (frame_rate.c frame_step_cap_ns): where RTSS is installed and running,
|
||||
// the frame limit goes into RTSS's profile for this executable and the game's own pacer holds no frames, so there is
|
||||
// one limiter. Anywhere else, or when any step fails, the game's own limiter works as it always did.
|
||||
// the frame limit goes into RTSS's profile for this executable and, while RTSS is seen holding the game to it, the
|
||||
// game's own pacer keeps only the 240-frame ceiling (rtss_decide.h rtss_pace_period), so there is one limiter.
|
||||
// Anywhere else, or when any step fails, the game's own limiter works as it always did.
|
||||
//
|
||||
// RTSS's hooks library (RTSSHooks64.dll in the folder its installer records under
|
||||
// HKLM\SOFTWARE\WOW6432Node\Unwinder\RTSS, InstallDir) exports the profile calls, loaded here at run time:
|
||||
|
||||
Reference in New Issue
Block a user