Note the lazy write-back's default on AMD RX 5000 and 6000 cards, the settings-file lines and the fatal summary in the draft release notes, and the new checks in the build guide.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
This commit is contained in:
chrg6
2026-11-10 15:14:43 -05:00
parent 11050fb0d3
commit d83f01acb3
2 changed files with 30 additions and 0 deletions

View File

@@ -336,6 +336,16 @@ A change to what the library warm logs when the driver's cache of stage librarie
`runtime/vk_pipeline.c` `lw_main`) passes `python tests\warm_hint_check.py`, which builds the header alone and checks
the added text by GPU vendor and by why the cache was cold. No game files.
A change to where the lazy write-back is on by default (`runtime/wb_lazy_choice.h`, `runtime/vk_memory.c`
`vk_mem_lazy_decide`) passes `python tests\wb_lazy_check.py`, which builds the header alone and checks the choice and
its reason by platform, by GPU driver and by what the player set. No game files, no GPU.
A change to what writes `nx2navi.ini` outside the game (`launcher/gameini.py`, `installer/ini.py`, `tools/make_game.py`,
`launcher/updater.py`) passes the settings-file tests of `tests\launcher_test.py` (`PlayerIniTest`, and the tests named
`..._settings_file` of `BackgroundUpdateTest` and `MakeGameTest`): a player's file with lines that are no settings of
the game comes through an update and a rebuild byte for byte. The game's own writer, the settings menu, is checked by
`--probe-cfg` with the same lines.
A change to the mouse camera's stick deflection (`runtime/input_map.c` `input_mouse_stick`) passes
`python tests\mouse_stick_check.py`, which builds that file with the rest of the runtime stubbed and checks the
deflection at each camera speed: a slow movement is divided by the factor, a fast flick reaches full tilt. No game

View File

@@ -33,3 +33,23 @@ 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.
- 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 RX 5000 and RX 6000 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). None of us has one of these cards, their Windows driver is a branch of its own,
and one report from an RX 6600 lost its video device a few minutes into play with it on. We found no fault in the
code and cannot say it was the cause, so until someone has run it there the old copy-back at the end of every GPU
submission is the default with that driver; open areas run slower for it, as they did in 0.7.0. `wb_lazy = 1` in
`nx2navi.ini` turns it on: if you try it, tell us whether the game stays up, with the log. NVIDIA cards and AMD's
RX 7000 and RX 9000 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.