runtime/vk_ffx4.cpp loads amd_fidelityfx_loader_vk.dll from beside the executable and asks it which upscaler versions the device can run. Where a 4.x version is listed (Radeon RX 6000, RX 7000 and RX 9000 cards with AMD's driver 26.10.1 or newer) the menu's Upscaling row gains AMD FSR 4 Native AA, Quality, Balanced, Performance and Ultra Performance, and fsr4 = 1 runs it in FSR 3.1's place with the same inputs. Its contexts are made with that version asked for by its id and the provider is asked afterwards which version it runs, so no other upscaler can be shown under the name. When a context or a dispatch fails, FSR 3.1 makes the frame, and after three failures FSR 4 is off for the run. Each upscaler starts its history anew on the frame after a change from one to the other. The setting is off by default and the Linux build compiles stubs. On an RX 7900 XT (driver 26.10.1, 3440x1440, HDR) the library runs FSR 4.1.2: a context takes 54 ms to make and 217 MiB of video memory. Standing in Hyrule Field: Quality 47.8 fps where FSR 3.1 gives 51.5, Native AA 41.4. Screenshots of 601 consecutive frames standing, 801 during a camera sweep, 701 each in Kakariko and the graveyard, and 1,301 across changes between FSR 3.1 and FSR 4, their modes and off show no flicker that FSR 3.1 does not have, and it runs together with FSR 3.1 frame generation. The SDK's API headers are in runtime/third_party/ffx_sdk, unmodified, with the licence. tools/make_kit.py and tools/make_launcher.py take AMD's two signed libraries with --ffx4, and tools/make_game.py copies them beside the game when the kit has both. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
4.0 KiB
Draft notes for the release after 0.7.1. The version number is not decided yet.
Faster
- AMD cards: about a fifth more frames in open areas, and more even frame times. The game asks the video card
which objects are visible, about a hundred questions a frame in Hyrule Field, and waits for a frame to be finished
on the card before it lets the next one start. The answers were fetched one call at a time, on the thread that also
reports "finished", and on AMD's Windows driver each of those calls goes into the kernel: every frame was reported
finished about 4 ms late, with every thread of the game waiting. They are now fetched a few hundred at a time.
Standing in Hyrule Field on an RX 7900 XT (driver 26.10.1, 3440x1440, FSR): 53 fps instead of 45, and the longest
frame of a minute 46 ms instead of 55 (
oq_batch = 0innx2navi.inibrings the old readback back). - No more frames drawn one present late. The game signals from the CPU when a frame's data is written, and its
render thread submits the frame's commands without waiting for that signal. When the signal came a millisecond or
two after the submit call, in about every other frame in Hyrule Field, the frame was set aside and drawn at its
present, and frames of 23 and 15 ms took turns. The submit call now waits for the signal, 10 ms at most
(
gate_wait_ms): 54.5 fps instead of 53 in the same place and the longest frame 33 ms instead of 46; withvk_recorder = 1, which AMD cards do not have on by default, 58.6 fps.
New
- AMD FSR 4 upscaling on Radeon RX 6000, RX 7000 and RX 9000 cards (Windows, AMD's driver 26.10.1 or newer):
AMD's machine-learned upscaler, in the menu under Screen, Upscaling, as AMD FSR 4 Native AA, Quality,
Balanced, Performance and Ultra Performance (
fsr4 = 1innx2navi.ini). It keeps thin things whole that FSR 3.1 breaks up or smears when the camera moves: grass and leaves, Navi's wings, the edges of Link's hat. It is off until you choose it, because it costs more than FSR 3.1: standing in Hyrule Field on an RX 7900 XT at 3440x1440, 47 fps in Quality where FSR 3.1 gives 51, and 41 fps in Native AA; it takes about 220 MB of video memory. The setup brings AMD's two libraries for it (FSR SDK 2.4,amd_fidelityfx_loader_vk.dllandamd_fidelityfx_upscaler_vk.dll), which ask the driver whether the card can run FSR 4: the rows appear only where it can, and the log names the version (ffx4:). It works together with FSR 3.1 frame generation, and you can switch between FSR 3.1 and FSR 4 while playing. - Add to Steam in Customize Launcher (Windows): adds the game to your Steam library as The Legend of Zelda Ocarina of Time, with Navi as its icon and the title screen's artwork and logo. Starting it from Steam starts the game. Steam restarts once while it is added.
- Custom color scheme in Customize Launcher: pick your own background, panel and button colors on a color square with a hue bar, or type a hex code.
Fixed
-
Your own background picture in the launcher is no longer partly hidden under the top bar: it now starts right below it, and keeps its shape.
-
Black and white blocks on AMD RX 5000 and RX 6000 cards: on Navi and on Link next to her, on bright floors near her, and on the bright outdoors seen through a door or window from inside a house. Every float colour a shader writes is checked for NaN, so that one bad pixel cannot spread through the blur and bloom passes; those checks, and the game's own NaN tests in nearly nine of ten shaders, are float comparisons that a shader compiler may decide can never be true. The Windows driver for these cards uses AMD's older shader compiler (the log reads "AMD proprietary shader compiler"); with it each NaN test is now made on the bits of the number instead, which no compiler can drop. It is on by default only with that driver (
vk_nan_bits); the first start after the update compiles the pipelines again. Untested on those cards before this release: please report whether the blocks are gone.