mirror of
https://github.com/tangerineturtle1/NX2navi.git
synced 2026-11-18 06:59:57 -04:00
151 lines
14 KiB
Markdown
151 lines
14 KiB
Markdown
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 = 0` in `nx2navi.ini` brings 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; with
|
|
`vk_recorder = 1`, which AMD cards do not have on by default, 58.6 fps.
|
|
- **Fewer hitches in the seconds after entering an area.** Memory the game has not written for a while is
|
|
write-protected in 2 MiB pieces, so that it need not be checked for changes every frame. Protecting a piece takes
|
|
microseconds as a rule, but 8 to 17 ms each in the seconds after an area has loaded, and up to 32 pieces were
|
|
protected in one go: frames of 50 to 90 ms, in clusters for some 20 seconds after Kakariko, the Market or the
|
|
Graveyard came up. The work now stops after a millisecond a pass and waits when a piece was slow. Walking from
|
|
Kakariko into Hyrule Field on an RTX 5090, the time lost to such calls after the load went from 1,374 ms to 115 ms
|
|
and a 78 ms frame is gone (`freeze_budget_us = 0` in `nx2navi.ini` brings the old behaviour back).
|
|
- **A long stall at some area loads is gone.** When the game gave back a block of video memory, it waited until the
|
|
card had finished everything queued, the new area's texture uploads included: 418 ms in one frame on entering
|
|
Kokiri Forest. It now waits only for the game's own work (`pool_fini_idle = 1` brings the old wait back).
|
|
- **More frames on NVIDIA cards than 0.7.1** in the places measured on an RTX 5090 at 1440p: Kakariko 145 to 149 fps
|
|
instead of 119, the Market 177 instead of 147, Hyrule Field by day 109 instead of 91.
|
|
|
|
## 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 = 1` in `nx2navi.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.dll` and
|
|
`amd_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.
|
|
- **Frame generation from AMD's newer library, to try**: in the menu under Screen, Frame generation, as *AMD FSR 4
|
|
library* with its version, a choice of its own after *AMD FSR 3.1* (`fsr4_fg = 1` in `nx2navi.ini`). Choosing it
|
|
sets Upscaling to FSR 4 as well, which it needs. The frames are then generated by the library FSR 4 comes with (FSR
|
|
SDK 2.4, `amd_fidelityfx_framegeneration_vk.dll`) instead of the FSR 3.1 library. It picks the version for your
|
|
card: on a Radeon RX 9000 with Windows 11 that is AMD's machine-learned FSR Frame Generation 4, **which nobody has
|
|
tested in this game yet**; on every other card it is version 3.1.6, which on an RX 7900 XT runs at the same frame
|
|
rate as before and showed clean frames in a fast camera turn. It is off unless you set it, and when it fails the FSR
|
|
3.1 library takes over. Please report how it looks on an RX 9000.
|
|
- **A debug menu for testing** (off by default: Game tab, *Debug menu (F9)*, or `debug_menu = 1` in `nx2navi.ini`). F9
|
|
opens a panel on the left edge, in the performance overlay's look, with the game in view beside it. It has five
|
|
tabs. *Flags*: the game's 11,292 on/off flags with a search box, about 2,250 of them by name (the names are found in
|
|
your own game's event files; the rest show their hash), each switched with a click through the game's own function,
|
|
with the last changes listed to put back. *Teleport*: every area of the game with its named start positions, 415
|
|
places read from your own game's files, with a search box and buttons for the warp songs' pads, both sides of the
|
|
loading zones and the boss rooms. A click takes Link there through the game's own change of area, as a door or a
|
|
warp song does, so the area loads as in play, a first visit's cutscene plays and a boss room starts its fight.
|
|
*Cutscenes*: the game's 653 event scripts by name (cutscenes, conversations, scripted moments), each started with a
|
|
click as if its trigger had fired. The game takes a teleport or an event only while Link stands free: not during a
|
|
cutscene or a conversation, and not while he swims. *World*: Link's position, the game's speed from 0.05x to 8x,
|
|
and a free camera. With it on, the game draws from a camera of your own, in play and in cutscenes: close the menu
|
|
and the left stick moves it, the right stick turns it, ZR and ZL raise and lower it, R makes it faster and L slower,
|
|
while Link stands; or leave it where it is and play on with the pad. It works inside the game's own camera
|
|
update, so the game draws, culls and loads detail for what the camera sees. *Memory*: a search of the game's memory
|
|
for a number (1, 2 or 4 bytes, or a float), narrowed down by equals, changed, unchanged, went up or went down, with
|
|
a value to set at a place or to hold there. Changing flags or memory, teleporting and starting events can break a save, and the game saves by itself
|
|
after a change of area, so keep a copy first.
|
|
- **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.
|
|
- **Co-op over the internet, to try** (off by default; the Co-op tab of the menu). Players in a room share progress by
|
|
the room's rules. It needs a relay server you or a friend run: the game has no address built in.
|
|
- **A fallback for video cards without mesh shaders.** The game draws part of the world with mesh shaders; on a card
|
|
without them those draws are now run as compute passes and an ordinary draw (`mesh_fallback = auto`). It draws the
|
|
same picture in our test of the path itself and runs slower than real mesh shaders. **Nobody has played with it on
|
|
such a card yet**: please report how it looks.
|
|
- **A new HDR tone mapping**, the default with HDR on (`hdr_tonemap` in `nx2navi.ini` chooses between it, the one
|
|
before and the game's own).
|
|
- **The menu opens when the controller in use disconnects** and no other is connected, where the game played on with
|
|
nothing pressed.
|
|
|
|
## Fixed
|
|
|
|
- A crash with frame generation (AMD FSR 3.1) set: switching Upscaling to a choice without FSR or DLSS and back, which
|
|
the Upscaling row does on its way through its choices, ended the game in AMD's driver. Frame generation was handed
|
|
the depth picture of the last frame before the switch, which the game had replaced by then.
|
|
- Frame generation never generates a frame from a picture with the HUD in it any more: a frame for which the picture
|
|
without the HUD is missing is shown as it is, so the HUD cannot be warped along with the scene behind it. On screen
|
|
the item button stayed pixel for pixel in place through a fast camera turn, with both frame generation libraries.
|
|
- 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.
|
|
- A black picture for one frame, now and then, mostly with FSR upscaling. The game looks textures up that it has
|
|
released; past 2,048 of those the oldest was dropped although the game still drew with it every frame.
|
|
- Pale or see-through patches of ground in Hyrule Field and at Lon Lon Ranch, and Link's hair missing after hours of
|
|
play: textures no shader had sampled for a while were given up under memory pressure and did not come back, and a
|
|
second description of the same texture memory started empty. The first no longer happens, and the second is filled
|
|
from the texture's memory.
|
|
- White flickering spots with DLSS or DLAA: the upscaler's history was thrown away whenever the game moved its render
|
|
targets, 26 times in a run through Kakariko; it is now kept.
|
|
- The game ending with a lost video device about two seconds after loading a save in Hyrule Field at night
|
|
(8 times in 23 loads on an RTX 5090, none in 25 since).
|
|
- A dark frame at the Market's gate: a new shadow map started with what the memory under it held before.
|
|
- A lost video device now ends the game at once with exit code 72 and its report, where threads could go on using the
|
|
device.
|
|
- A pipeline cache file over its size limit was thrown away at every start and never replaced, so every start built
|
|
its pipelines again.
|
|
- The setup's check of free disk space counts shaders it has already prepared, and a failed build is reported as
|
|
such.
|
|
|
|
- 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.
|
|
- AMD RX 6000 and older cards: the game should no longer end (code 71) when an enemy is killed. A player with an
|
|
RX 6700 XT had it at every kill since 0.5 and found that `gpl = 0` (no graphics pipeline libraries) stops it; a
|
|
player with an RX 5700 XT reported the same ending. That is now the default with AMD's Windows driver for these
|
|
cards (the log reads "gpl no ... off by default on AMD's driver for RDNA 2 and older"). The price: a pipeline the
|
|
game needs for the first time is built whole while its draw is left out, so new things can appear some frames
|
|
late, and the start waits until every pipeline of earlier sessions is built instead of 20 seconds at most.
|
|
`gpl = 1` in `nx2navi.ini` turns the libraries back on. One player's finding on one card; none of us has such a
|
|
card, so please report whether the game stays up.
|
|
- The older installer's last step no longer writes `nx2navi.ini` again as a whole to set the language: it changes the
|
|
`lang` line and keeps every other byte (it turned Windows line ends into Unix ones and dropped a byte order mark).
|
|
|
|
## Changed
|
|
|
|
- **AMD cards: the faster copy-back of 0.7.1 is off by default again.** 0.7.1 turned it on for every card on Windows
|
|
(what the game's shaders write is copied back from the video card once, and then only when the game's CPU code
|
|
touches it). Since then two reports from AMD cards had the game end in play: an RX 6600 lost its video device a
|
|
few minutes in with it on, and a player whose game ended in fights played for hours with it off. We found no fault
|
|
in the code and cannot say it was the cause, and none of us has played a fight on an AMD card with it on. Until
|
|
someone has, the old copy-back at the end of every GPU submission is the default with AMD's Windows driver; open
|
|
areas run slower for it, as they did in 0.7.0. The RX 7900 XT figures under *Faster* come from builds that had it
|
|
on by default. `wb_lazy = 1` in `nx2navi.ini` turns it on: if you try it, play a few fights and tell us whether the
|
|
game stays up, with the log. NVIDIA cards keep it on. The log says which is in effect and why ("mem: lazy
|
|
write-back ...").
|
|
- **A line in `nx2navi.ini` that is no setting of this version is pointed out.** Such a line does nothing; the game
|
|
only wrote "unknown key" into its log. The log now lists them in one line at the start, beside a line with every
|
|
setting the file does set, and the settings menu shows them in its bottom row. An update or a rebuild never rewrites
|
|
`nx2navi.ini`, and the menu keeps such lines when it saves, so nothing has to be added again after an update.
|
|
- When the game ends with a fatal error or a crash, the end of the log names the video card, its driver, the memory
|
|
mode, whether the lazy write-back was on (with its armed ranges, its fetches so far and one in progress) and the
|
|
texture detail, so a report that holds only the last lines of a log still says them.
|