Files
NX2navi/docs/releases/v0.9.2.md
epicmeme546 2495391dd7 Fill the scene's outer rows and columns in every jittered frame, and take only turns of 30 degrees a frame for camera cuts.
A player's clip at Ultra Performance still showed the sky's colour in the last row of about half the frames. In those frames the fill, done only after a jitter to the left or up, had not run. The outermost row and column on each side of the light target and the depth are now filled from their neighbours whenever the frame was jittered, whatever the jitter's direction. A copied border pixel is nothing anyone sees.

A quick swing of the camera around Link turns it 11 to 18 degrees and moves it 0.9 to 1.4 m a frame. That was taken for a cut, and nine frames in a row started a new history, which showed the scene at its render size, blocky at the smaller modes. A cut now needs a move of 5 m or a turn of 30 degrees with a move.

Hyrule Field, FSR 4 Ultra Performance, present screenshots: standing still and on grass while running, the bottom edge matched the rows above it. Over water a bright bottom edge remains in a fifth of the moving shots, and none with the jitter off: the water reads the scene before the fill. The 0.9.2 notes list it as a known issue, with the frame rates and FSR's GPU times measured for the Ultra Performance question.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-12 10:22:00 -05:00

2.0 KiB

Fixed

  • 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.
  • The light line at the bottom or right edge with FSR or DLSS, still seen in some frames. The scene's outermost rows and columns are now filled from the ones next to them in every frame the upscaler gets, not only after the scene moved up or to the left.
  • A blocky picture for a moment whenever the camera swung quickly with FSR or DLSS. A fast swing of the camera around Link (11 to 18 degrees a frame) was taken for a cut to a new view, and the upscaler threw away what it had built up at every frame of the swing; at Ultra Performance that showed the scene at a third of the picture's size. 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 coarser while they move: the upscaler gets only the camera's motion for them, not their own, so it can keep less of what it built up there.
  • Over water, a bright line can still show at the very bottom of the picture now and then with FSR or DLSS: the water reads the scene before its last row is filled.
  • 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.