Files
NX2navi/runtime
epicmeme546 5833ad8e18 Hand frame generation only the depth, motion vectors and HUD-less picture of a current frame.
What an evaluation of the upscaler leaves for frame generation stayed marked fresh for as long as frame generation
was off, because only frame generation's own swapchain takes it. Among it is the game's depth target, which the
game replaces when the scene's size changes. Switching the upscaler off and on again with frame generation set, as
the menu's Upscaling row does on its way through its choices, handed that destroyed image to frame generation's
preparation at the first present afterwards, and AMD's Vulkan driver ended the process (amdvlk64.dll, exception
c0000409, reproduced three times on an RX 7900 XT with driver 26.10.1). vk_dlaa.c now drops these inputs when the
upscaler goes off or on, and never hands out any made more than four presents ago. The same switch in a test run
now plays on, with the upscaler off for 150 frames and frame generation back afterwards.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
2026-11-11 04:48:41 -05:00
..
2026-11-07 05:04:38 -05:00
2026-11-07 05:04:38 -05:00
2026-11-07 05:04:38 -05:00
2026-11-07 05:04:38 -05:00