mirror of
https://github.com/tangerineturtle1/NX2navi.git
synced 2026-11-19 12:59:58 -04:00
Offer FSR 3.1 in the Screen tab only where its library can load.
On Linux the Screen tab listed the five FSR 3.1 upscaling modes and AMD's frame generation, but only the Windows build loads amd_fidelityfx_vk.dll: a player who picked a mode got the scene at the mode's share of the picture with nothing to scale it back up. vk_ffx_available answers from the load's result once it ran, and before that from the library file being there, so the menu can ask every frame. Where it says no, the menu lists neither, a mode that is still set shows "in use: off", the scene keeps the game's own share (vk_dlaa_fsr3), frame generation keeps the plain swapchain with one log line, and the texts name what does run. Pull request #371 by mooki000, taken as it is; two hunks merged by hand (vk_fg_wanted, which now also stays off after a failure, and a README line that had gained Texture filtering). It touches vk_dlaa.c, which another session is changing: vk_dlaa_fsr3 gains the availability test and one log text changes. On Windows the menu changes only where the DLL is missing. The Windows files compile; nothing was run. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
This commit is contained in:
@@ -8,7 +8,7 @@
|
||||
#define DLAA_SCENE_MIN_W 320u
|
||||
|
||||
int vk_dlaa_wanted(void); // the setting is on (the device may still lack DLSS)
|
||||
int vk_dlaa_fsr3(void);
|
||||
int vk_dlaa_fsr3(void); // the setting is on and its upscaler is AMD FSR 3.1, which loads
|
||||
int vk_dlaa_needs_restart(void); // the menu's upscaler cannot start in this run
|
||||
// Frame generation (vk_fg.cpp): the depth and motion vectors of the frame DLSS or FSR 3.1 last ran on, with its jitter
|
||||
// and whether its history reset; 1 once per evaluation (0: none since the last call). The images stay valid until the
|
||||
|
||||
Reference in New Issue
Block a user