Make the release 0.11.0: the release prepared and previewed as 0.10.2 takes this number, with its notes.

The user asked for the release to go out as 0.11.0. No final 0.10.2 was published: only the previews 0.10.2-rc1,
-rc3 and -rc4 carry that name, and the launcher counts 0.11.0 as newer than each of them, so testers are offered it
on either update channel.

VERSION holds 0.11.0 and the notes move to docs/releases/v0.11.0.md, with a line for those on a preview. Every line
that named 0.10.2 as the release in which something changed names 0.11.0 now: comments in the runtime, the two log
lines that give a version (the removed low-end GPU mode in cfg.c, the page generations in vk_memory.c),
nx2navi.ini.example, docs/building.md, the labels of tests/tex_release_check.c and a comment of
tests/audio_params_check.c. AUDIT.md names the release 0.11.0 throughout and records the earlier name and the
previews once, in its status line. Nothing else changes.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
This commit is contained in:
chrg6
2026-11-14 09:24:25 -05:00
parent 7432f7375c
commit 712568d4fb
13 changed files with 40 additions and 36 deletions

View File

@@ -919,7 +919,7 @@ A change to how nx2navi.ini and the environment are read (`runtime/cfg.c` `cfg_l
`cfg_bool`, `check_value`) passes `python tests\cfg_parse_check.py`, which builds `cfg.c` with stand-ins for what it
links with and loads scratch files: a comment after a value of a setting with a set of values is cut and logged once
with its line, free text, a value in double quotes and the environment keep theirs; switches written as words read as
0 or 1 through every reader; `low_end_gpu`, the switch of the low-end GPU mode that 0.10.2 removed, turns nothing on
0 or 1 through every reader; `low_end_gpu`, the switch of the low-end GPU mode that 0.11.0 removed, turns nothing on
and is named once in the log (`lowend_set`), and the mode's keys are read by themselves; values
outside their sets are logged with their line, at most 16 lines and a count; a full settings table logs one line at
load and one for the menu. The launcher's reader (`launcher/gameini.py`) has the same comment lines in

View File

@@ -1,9 +1,11 @@
## Install or update
- **Already have 0.6.0 or newer:** start the launcher; it offers 0.10.2, updates itself and keeps your saves and
- **Already have 0.6.0 or newer:** start the launcher; it offers 0.11.0, updates itself and keeps your saves and
settings. This update translates the game's code once more (for the ocarina recorder's fix) and prepares every shader
again with the fixed shader translator: a few minutes, once.
- **New install:** download **`NX2navi-Setup-0.10.2.exe`** below, put it next to your `.nup` dump of the game and start
- **On a 0.10.2 preview:** the same; the launcher offers 0.11.0 on either update channel. 0.10.2 was this release's
name while it was tested, and no final 0.10.2 follows.
- **New install:** download **`NX2navi-Setup-0.11.0.exe`** below, put it next to your `.nup` dump of the game and start
it. Windows SmartScreen warns on the first start because the setup is not signed: choose *More info* and *Run
anyway*. The launcher checks your game files, builds the game (10 to 25 minutes, once), prepares every shader and
starts it.
@@ -54,7 +56,7 @@ cards).
## Fixed
- **See-through ground** (issues #569 and #824). 0.10.0 and 0.10.1 shipped an older shader translator, whose shaders
could not reach the newest texture slots, so ground and walls could turn see-through after some play. 0.10.2 ships
could not reach the newest texture slots, so ground and walls could turn see-through after some play. 0.11.0 ships
the translator built from its own sources, prepares the shaders again with it, and no longer uses translations kept
from the old one. The release tools now refuse a translator that was not built from the release's sources.
- **AMD Radeon RX 5000 and 6000 cards losing the device** (the game ending with code 72): on AMD's driver these cards