mirror of
https://github.com/tangerineturtle1/NX2navi.git
synced 2026-11-20 01:49:59 -04:00
Say in docs/architecture.md when a crash still calls into RivaTuner Statistics Server, and list the new state-file checks in docs/building.md.
The review found that docs/architecture.md said the ends of a crash and a fatal error make no call into RTSS's library, while rtss_limit.c rtss_limit_crash puts the profile back as an orderly exit does where the state file could not be written. The text now says that, that it never runs from RTSS's own thread, that the line takes each later value before the profile does, and that a state file that cannot be read is left with the other executables' lines. Its "one limiter" and README.md claims were corrected with the movie and unproven-hold fixes, and nx2navi.ini.example with the kept-out restore. docs/building.md's description of tests/rtss_limit_check.py now names the checks added since: the previous written value, a kill inside a save, put backs that do not land, an unreadable state file and a crash on RTSS's own thread. No behaviour changes. Checks that passed: tools/check_content.py --staged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
@@ -493,13 +493,16 @@ hold (given up after 30 s, a minimised window not counted), no picture going out
|
||||
reasons, a want that must stay two polls and low latency switching at every poll, a movie at 144, 60 and 40, a closed
|
||||
run, a hooks library that does not load, and two limiters. It also checks the pacer's period beside RTSS
|
||||
(`rtss_pace_period`), the limit's rounding without a denominator, and the state file `rtss-profile.txt`: its lines,
|
||||
its rewrite and what a start does with a line a run that did not close left. Statically, a crash and a fatal error
|
||||
its rewrite and what a start does with a line a run that did not close left, the value written before the newest one
|
||||
included. Statically, a crash and a fatal error
|
||||
(`main.c` `crash_handler`, `dispatch.c` `fatal_end`) go through `rtss_limit_crash`. On Windows it also builds the real
|
||||
`rtss_limit.c` against a fake RTSS (its registry key, hooks library, profile files and shared memory) and runs each
|
||||
scenario in a process of its own, among them a want after the exit's restore and one the worker read before it, a
|
||||
worker polling without pause while the want switches, the registry and file calls a present must not make, and a run
|
||||
killed while RTSS held its limit followed by the next start, each in a process of its own (a next start with a limit,
|
||||
with frame generation on and with `NX2NAVI_RTSS=0`). No GPU, no RTSS, no game files.
|
||||
with frame generation on and with `NX2NAVI_RTSS=0`, and a run killed inside the save of its second limit), put backs
|
||||
that do not land, a state file that does not read, and a crash on RTSS's own thread with no line in the file. No GPU,
|
||||
no RTSS, no game files.
|
||||
|
||||
A change to how the mixer applies volumes (`runtime/audio_mixer.c` `accumulate_ramp`, the voice and splitter paths
|
||||
of `audio_mixer_render`) or to what it owes the device after a stall (`ring_pull`, `audio_mixer_owed`) passes
|
||||
|
||||
Reference in New Issue
Block a user