Files
NX2navi/docs/releases/v0.9.2.md
epicmeme546 322d7c0933 Run DLSS or FSR where the game's own upscaler runs, and fill a jittered pass's edge rows as soon as it ends.
With the HUD hidden the screen showed the scene at its render size instead of the upscaler's picture. The upscaler ran at the pass after the game's own upscaler, taken for the pass the HUD is drawn into. Without a HUD the game draws no such pass: the next one is the frame's last, which encodes the stand-in's scaled scene into the 8-bit output. The upscaler's picture went into that target and the last draw drew over it. A player's save with the HUD off showed blocks of render pixels, a picture jumping by a render pixel between frames, and the undrawn edge row in white, at every FSR mode and at Native AA; every test save until now had the HUD on. vk_dlaa_upscaler now runs the upscaler right after the stand-in of the game's upscaler wrote its output image, and puts the picture there (NX2NAVI_DLAA_AT_UPSCALER=0: as before).

The edge fill moves to the end of each pass that took the jitter (vk_dlaa_pass_end), for the pass's colour targets and depth, in one copy of eight regions per image. Filled only before the upscaler, the undrawn row had already been read by the water, the bloom and the anti-aliasing pass.

On a copy of the player's save (HUD off), FSR 4 Ultra Performance, world slowed to 1/20, present screenshots 0.25 s apart: the picture moves 0.00 to 0.02 px between shots (old placement: a jump of one render pixel in 5 of 20), the change on edges is 1.9 against 16.9, and no shot has the white row (half had it, with HDR on). Native AA, Performance with HDR, and FSR 3.1 are steady and clean as well; the save with the HUD on is unchanged. A run through a stream: 0 of 106 shots with a bright bottom edge (20 of 102). Frame rate 58.3 fps against 58.6.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
2026-11-12 11:14:16 -05:00

2.7 KiB

Fixed

  • FSR and DLSS showed a blocky, shaking picture with the HUD hidden. The upscaler's picture was put where the game draws its HUD. With the HUD off the game skips that step, and the frame's last step then drew the game's own plainly scaled scene over it: the screen showed the scene at its render size (a third of the picture at Ultra Performance) in visible blocks, shaking by up to one render pixel from frame to frame, with a white line along the bottom or right edge in about half the frames, while the upscaler's work was thrown away. Native AA was affected as well as the scaling modes. The upscaler now runs where the game's own upscaler does, HUD or not. On a save with the HUD off at FSR 4 Ultra Performance: fine detail is back, the picture moves 0.02 pixels between screenshots of a still view instead of jumping by 3, and no screenshot has the white line (half had it).
  • A crash after switching FSR modes. One FSR context served every mode, with another render size at each switch, and the first frame after a switch from Quality to Native AA could end the game inside AMD's driver. Each render size now gets a context of its own, as AMD's own sample makes them, and the one before goes a few frames later (a mode switch takes about 50 ms more); with dynamic resolution on, one context made for changing sizes takes every step.
  • Bright patches along the bottom edge over water, and a light line at the edge, with FSR or DLSS. To let the upscaler build a smoother picture the scene is drawn moved by a fraction of a pixel, and AMD's driver then leaves the last row or column undrawn. Those are now filled from their neighbours as soon as each step of the scene is drawn, before the water, the bloom or the upscaler read them.
  • A new start for the upscaler at every frame of a quick camera swing. A fast swing of the camera around Link (11 to 18 degrees a frame) was taken for a cut to a new view. Only a jump of the camera or a turn of 30 degrees or more in one frame counts as a cut now.

Known issues

  • At FSR's and DLSS's smaller modes, Link and other characters look a little coarser while they move: the upscaler gets only the camera's motion for them, not their own.
  • Ultra Performance gains little frame rate over Quality with FSR 4. Most of a frame is the replay of the game's draws on the CPU, which does not shrink with the render size, and FSR 4 itself takes 3.1 ms of the GPU's time at Ultra Performance and 3.9 ms at Native AA on a Radeon RX 7900 XT (FSR 3.1: 0.5 ms). Measured standing in Hyrule Field at 3416x1440: FSR 4 Native AA 52 fps, Quality 53, Ultra Performance 55; FSR 3.1 Native AA 55, Ultra Performance 66; without an upscaler 70.