mirror of
https://github.com/valentderah/totk-pc-recomp.git
synced 2026-11-21 04:55:56 +00:00
The motion image FG read held the camera's motion alone (fg_motion called mv_pass without its object pass). The camera follows Link, so his pixels carried the world's motion and the interpolation drew him twice, with a smeared strip where he had been; NPCs and enemies did the same. fg_motion now runs mv_pass with the object pass (vk_mvobj_execute), and its gates follow vk_objmv_wanted: DLSS once NGX came up (vk_dlaa_available, as before) or FG following the scene with its objects (vk_fg_objects_on). vk_mvprev_frame keeps last frame's block tables for either, vk_usnap_begin makes the host copy for either and vk_usnap_bytes reads the copy that submission wrote (FG turns on and off live), and vk_dlaa_prev_camera answers whenever the scene is followed. FG is off with DLSS, so every DLSS gate evaluates as before. fg_objects = 0 keeps the camera's motion alone for comparisons. Measured on A (RX 9070, 7900X on 4 cores, 1080p, field, 60 s): 85.6 drawn with fg_objects = 0, 80.0 with 1 (about 0.8 ms a drawn frame on the replay thread, half of it the snapshot's host copy), object pass 0.035 ms GPU. Still grass gets no false motion (SDK debug view: the game vector field stays within 0.2 px), and grass does not break up while the camera turns. Validation: 0 errors. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>