mirror of
https://github.com/tangerineturtle1/NX2navi.git
synced 2026-11-19 19:29:57 -04:00
Generate frames with DLSS on Linux through NGX itself: 2x to 6x or dynamic, switched while the game runs.
DLSS Frame Generation went through Streamline, which only the Windows build has, so framegen = dlss did nothing on Linux. There it now calls NGX's frame generation feature directly (vk_dlaa.c vk_ngxfg_*), with the depth, motion vectors, jitter, camera and HUD-less picture the Streamline path gets. With it on, each frame is composed into an image of its own instead of a swapchain image, the generated frames are made at the end of the frame's command buffer, and a presenter thread shows them and then the rendered frame, each copied into a swapchain image it acquires itself, spaced over the time between rendered frames (gfx_present.c ng_*). fg_mult is the multiplier: 2 to 6, or dynamic for only the frames the display's refresh rate needs. NVIDIA's libnvidia-ngx-dlssg.so.<version> goes beside the game; it is not in the repository or any kit. Pull request #124 by spidercraft. Its base was the present path of 0.5, so it is ported by hand: - taken as written: the NGX calls and the presenter (the block is lifted from the pull request's diff); - wired again into present_image, create_swapchain, the output rate and the HUD-less picture as they are now, with every new branch behind vk_ngxfg_wanted, which is 0 in the Windows build: the code is compiled there and never reached; - added: frame generation's feature and parameters are released before NGX shuts down, the presenter's images, semaphores and command pool go when the device is released and are made again for a new one, and a failed submit on this path settles its fence without an acquire semaphore; - the menu: the Frame generation row follows the setting at once on Linux and says "after restart" only when the game started without DLSS upscaling; the multiplier row lists what the GPU allows and Dynamic; - the overlay row of the pull request it builds on (#123) is not part of this. It touches vk_dlaa.c, which another session is changing: one field in N, the FG state after it, one FN line, the instance extension query, the capability read in vk_dlaa_init, the release, and a block appended at the end. Known gap, as in the pull request: on this path fps_limit counts the frames the game draws. The Windows files compile without new warnings; nothing was run, and the Linux path is not compiled here. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
This commit is contained in:
@@ -387,6 +387,12 @@
|
||||
# With fps_limit unset it is the display's rate.
|
||||
# fsr3 takes effect at once, dlss (on or off) at the next start.
|
||||
# framegen = off
|
||||
# On Linux dlss runs through NVIDIA's NGX itself, without Streamline: it needs dlaa = 1 with DLSS when the game starts
|
||||
# and NVIDIA's libnvidia-ngx-dlssg.so.<version> (from NVIDIA's DLSS SDK repository) beside the game, then switches at
|
||||
# once, and its multiplier is fg_mult: 2 to 6 (above 2 needs an RTX 50 GPU) or dynamic, which generates only the frames
|
||||
# needed to reach the display's refresh rate at the rate the game draws. There fps_limit counts the frames the game
|
||||
# draws, and framegen_multiplier is not used.
|
||||
# fg_mult = 2
|
||||
# DLSS frame generation's multiplier: the frames on screen for each frame the game draws, 2, 3 or 4 (one, two or three
|
||||
# generated). 2 needs an RTX 40 GPU or newer, 3 and 4 an RTX 50 and a current driver. A value above what the GPU and
|
||||
# driver allow (Streamline reports it) is lowered to that, with a line in the log; the menu offers only what they allow.
|
||||
|
||||
Reference in New Issue
Block a user