mirror of
https://github.com/tangerineturtle1/NX2navi.git
synced 2026-11-16 18:09: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:
@@ -1,12 +1,15 @@
|
||||
// Frame generation with AMD FSR 3.1 (NX2NAVI_FRAMEGEN = fsr3; applies after a restart): AMD's frame generation
|
||||
// swapchain (amd_fidelityfx_vk.dll, vk_ffx.cpp loads it) takes the place of gfx_present.c's swapchain. Every frame
|
||||
// the game presents, the swapchain presents a generated frame between it and the one before, on its own present
|
||||
// queue and pacing threads, so the screen shows twice the game's frame rate.
|
||||
// Frame generation with AMD FSR 3.1 (NX2NAVI_FRAMEGEN = fsr3, live: gfx_present.c window_settings_live makes the
|
||||
// swapchain again; a run whose device was made for DLSS Frame Generation waits for a restart, vk_fg_wanted): AMD's
|
||||
// frame generation swapchain (amd_fidelityfx_vk.dll, vk_ffx.cpp loads it) takes the place of gfx_present.c's
|
||||
// swapchain. Every frame the game presents, the swapchain presents a generated frame between it and the one before, on
|
||||
// its own present queue and pacing threads, so the screen shows twice the game's frame rate.
|
||||
//
|
||||
// The generated frame is built from the presented picture and the scene's depth and camera motion vectors, which
|
||||
// vk_dlaa.c makes for DLSS and FSR 3.1 upscaling, and without an upscaler for frame generation alone (vk_dlaa.c
|
||||
// fg_only_frame: the same pass at the scene's size, no jitter). The HUD is kept out through the picture without it
|
||||
// (vk_dlaa.c hudless); the menu is not generated, since generation pauses while it is open. The device creates two more queues of the graphics family for it (vk_device.c, vk_fg_queue_count).
|
||||
// (vk_dlaa.c hudless); the menu is not generated, since generation pauses while it is open. The device creates two more
|
||||
// queues for it (vk_device.c create_device, vk_fg_queue_count): of the graphics family where it has them, else of
|
||||
// another family that can present.
|
||||
#ifdef _WIN32
|
||||
#include <windows.h>
|
||||
#endif
|
||||
|
||||
Reference in New Issue
Block a user