mirror of
https://github.com/tangerineturtle1/NX2navi.git
synced 2026-11-19 04:19:57 -04:00
FSR 3.1 was soft at Performance and Ultra Performance, most of all in motion. On a village save, while the camera turned at a steady rate (present screenshots every 0.4 s, the mean absolute Laplacian of the scene's luminance): FSR 3.1 Native AA 6.7, FSR 4 Performance 5.9 and Ultra Performance 5.4, FSR 3.1 Performance 4.0 and Ultra Performance 3.3. The library's own input checks found nothing wrong, and its tuning constants (velocity factor, accumulation per frame, shading change scale, behind the test switch NX2NAVI_FFX_KEYS) gave nothing or took detail away. Its own sharpening at 100 instead of the default 80 gave 5.0 and 4.1. Now the share of extra sharpening grows from none at three quarters of the output's width to all of it at half (vk_dlaa_fsr3_boost). FSR 3.1's own sharpness goes that share of the way to its maximum, and its picture gets a second RCAS pass (shaders/dlaa_sharpen.comp, AMD's FSR 1 header with the linear light taken through c / (1 + max c) and back), before the HUD is drawn. Both follow the sharpness slider; 0 turns them off, and NX2NAVI_FSR3_SHARPEN=0 leaves the second pass out. At RCAS's full strength the pass took Performance to 8.2, past Native AA, with grain on every surface, so it runs 1.5 stops weaker: Performance 5.7, Ultra Performance 4.7, Quality 5.2. 63.4 fps against 65.1 without the pass. The HDR picture is clean. FSR 4 is untouched. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
3.8 KiB
3.8 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.
Changed
- FSR 3.1 is sharper at Balanced, Performance and Ultra Performance. It was soft there, most of all while the camera moved: turning the camera at a steady rate, FSR 3.1 Performance kept 60 % of Native AA's fine detail and Ultra Performance 50 %, where FSR 4 keeps 89 and 81 %. Below a render scale of three quarters, FSR 3.1's own sharpening now goes towards its maximum and its picture gets a second, lighter sharpening pass before the HUD is drawn; both follow the Sharpness slider, and 0 turns them off. Performance now keeps 85 % and Ultra Performance 71 %, for about 0.2 ms a frame. FSR 4 and Native AA are unchanged.
- Debug menu: the free camera has no limits. It flies where it looks and goes through walls, objects and the ground; it used to keep its height and climb whenever anything in the lower part of the view came within three metres, a character or a rock it was flown towards included. Ground avoidance is now a switch in the free camera's section, off unless you turn it on: with it the camera stays a metre above fields and gentle hills, and objects and walls never push it.
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.