Merge remote-tracking branch 'nx2navi/main' into ra-all-test

This commit is contained in:
chrg6
2026-11-12 11:23:49 -05:00
9 changed files with 214 additions and 81 deletions

31
docs/releases/v0.9.2.md Normal file
View File

@@ -0,0 +1,31 @@
## 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.