mirror of
https://github.com/tangerineturtle1/NX2navi.git
synced 2026-11-20 16:49:58 -04:00
Bring the comments on frame generation, its restarts and RivaTuner Statistics Server's exit up to date.
vk_dlssg.c said frame_rate.c divides the frame limit by the multiplier, but the limit counts the frames the game draws and only a limit of display is divided (frame_rate.c limit_game_hz). vk_fg.cpp said FSR 3.1 frame generation applies after a restart, but FRAMEGEN is live (gfx_present.c window_settings_live makes the swapchain again; only a device made for DLSS Frame Generation waits for a restart, vk_fg_wanted), and that its two queues come from the graphics family, while vk_device.c create_device takes them from another family that can present where the graphics family has one queue. rtss_limit.c's header said the profile is put back "from every path that ends the process" and stays "until the next run changes it", and named only the setting and frame generation as keeping RTSS out: it now names the exits that skip the restore (a kill, the device-lost watchdog, a crash inside the crash handler), that the next run takes the leftover limit for the player's own, low latency, the read-only thread of a kept-out run, and the lookup on the worker. (rtss_limit_want's "both reasons need a restart" went with the change that starts the worker for a kept-out first want.) Comments only: the three files compile, and check_content passes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
@@ -11,8 +11,9 @@
|
||||
// Multi frame generation: NX2NAVI_FRAMEGEN_MULTIPLIER (2, 3 or 4, live) is how many frames the display gets per
|
||||
// rendered frame, so one, two or three generated ones. Streamline says how many this GPU and driver can generate
|
||||
// (numFramesToGenerateMax: one where only 2x runs, three on an RTX 50); a higher setting is clamped to it with a log
|
||||
// line. frame_rate.c divides the frame limit by the multiplier in effect (vk_dlssg_multiplier), so the display gets the
|
||||
// limit and the game renders a half, a third or a quarter of it.
|
||||
// line. The frame limit counts the frames the game draws and the generated ones come on top (frame_rate.c
|
||||
// limit_game_hz): 60 at 4x is 60 drawn and 240 shown. Only a limit of display is divided by the multiplier in effect
|
||||
// (vk_dlssg_multiplier), since a frame past the monitor's refresh is never seen.
|
||||
//
|
||||
// DLSS-G needs Reflex, whose low-latency mode paces the game (NX2NAVI_REFLEX, default 1; 0 off, 2 on with boost): the
|
||||
// game's frame sleeps in Reflex where it starts (its acquire of a window image), and each frame carries the latency
|
||||
|
||||
Reference in New Issue
Block a user