mirror of
https://github.com/tangerineturtle1/NX2navi.git
synced 2026-11-17 09:19:58 -04:00
A second reading of the commits taken in from pull requests found these, each traced in the code: - heap_lazy: the camera speed's search read the whole heap, which with the setting on committed every page and undid what it saves; a scan now steps over the pages the lazy heap never committed (mem_untouched_run). tests/frame_step_check.py and tests/save_share_check.py no longer linked (frame_rate.c and fs_host.c call the new memory functions; the second also missed mem_probing before); both pass again. The settings text says that with the setting on a PC out of commit ends the game in play, not at start, and the census comment is back over its own function. - Pipeline libraries on AMD's older Windows driver: the condition is the driver for RDNA 2 and older (RX 400 to RX 6000), not RX 5000 and RX 6000 only, and the texts named a price the code does not have. With libraries off a new pipeline is built by a worker while its draw is left out, and the start waits for every recorded pipeline instead of 20 s at most. The texts say so, and that the finding is one player's on one card. The menu strings nothing shows are as they were. - Page file hint: it comes only when Windows sizes every page file, and it names the initial size and the automatic management that must be unticked first. - Frame generation note: it keeps "needs an RTX 40 or newer" for the players it is right for and points the others to the log; the bridge's line says it is Streamline's general support check. - Comments and settings texts that still described the old behaviour: the process commit bound, the wait with shadow storage, the scratch's least size, the action prompt under auto. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> (cherry picked from commit 19f03aa01b26d6e17fb5fc70ad987aa8c68e8225)
66 lines
5.7 KiB
Markdown
66 lines
5.7 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.
|
|
|
|
## New
|
|
|
|
- **Add to Steam** in Customize Launcher (Windows): the game joins your Steam library as *The Legend of Zelda Ocarina
|
|
of Time*, with Navi as its icon, the title screen's moonlit field as its background and cover, and the game's logo,
|
|
all made from your own game files when you select the row. Playing it from Steam starts the game straight away,
|
|
without the launcher. Steam closes for a moment while the shortcut is written and starts again with it.
|
|
|
|
## Fixed
|
|
|
|
- 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.
|