Correct what a review of this intake's commits found.

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)
This commit is contained in:
chrg6
2026-11-10 23:47:11 -05:00
parent fc1a50f0db
commit 420aef041a
21 changed files with 87 additions and 53 deletions

View File

@@ -160,8 +160,9 @@ beside the game.
driver keeps the prepared shaders' libraries in that cache, and a smaller limit drops the oldest as new ones come in
(a 2048 MB cache could not hold them): every start then builds them again in the background, and play stutters, with
some things missing for a few frames, until that is done. The log's `library warm` lines say when this happens.
- With 16 GB of RAM, give Windows a fixed page file of at least 32 GB (System, About, Advanced system settings,
Performance Settings, Advanced, Virtual memory: Custom size, then restart). Windows counts the game's video memory
- With 16 GB of RAM, give Windows a fixed page file whose initial size is at least 32 GB (System, About, Advanced
system settings, Performance Settings, Advanced, Virtual memory: untick the automatic management, Custom size with
an initial size of 32768 MB or more, Set, then restart). Windows counts the game's video memory
against RAM plus page file, and a page file Windows sizes itself grows too slowly for Hyrule Field: the game then
lets textures go and the ground can flash white or black. The log says `system commit low` when this happens.
- **Screen** in the menu has Texture filtering (anisotropic, up to 16x, at once), Texture detail (Reduced and Low

View File

@@ -33,13 +33,14 @@ Draft notes for the release after 0.7.1. The version number is not decided yet.
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 5000 and RX 6000 cards: the game no longer ends (code 71) when an enemy is killed. The Windows driver for
these cards faults when it links a burst of new pipelines from shader libraries, which is what the first kill of a
session asks for; players with an RX 6700 XT and an RX 5700 XT had it at every kill, and one of them found that
`gpl = 0` stops it. That is now the default with this driver (the log reads "gpl no ... off by default on AMD's
driver for RDNA 1 and 2"). The price: a pipeline the game needs for the first time is built whole while its draw
waits, so a new area hitches more on these cards. `gpl = 1` in `nx2navi.ini` turns the libraries back on. A
contributor's change, checked on their card; none of us has such a card.
- 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).