mirror of
https://github.com/tangerineturtle1/NX2navi.git
synced 2026-11-18 09:09:56 -04:00
Merge main into the 0.9.1 release: the launcher's Mods screen, the anti-aliasing choices beside FSR and DLSS, and the scene's last row and column filled before an upscaler reads it.
The 0.9.1 notes keep the release branch's text and take main's sections: New, the edge line under Fixed, and Changed. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
This commit is contained in:
@@ -195,7 +195,9 @@ keeps per-core data without locks and relies on that, so the host models it (`ru
|
||||
composite (edges, blending weights, composition into the scene target as square-rooted RGB9E5 words). `off`, `fxaa`
|
||||
and `smaa` leave out the first two and replace the composition with `shaders/aa_post.comp` or SMAA at its Ultra preset
|
||||
(`shaders/smaa_*.comp`); the game's passes are known by a hash of their guest code (`vk_exec_draw.c` `aa_dispatch`).
|
||||
`taa` is DLSS or FSR 3.1 at the scene's size; while either runs, the game's SMAA stays.
|
||||
`taa` is DLSS or FSR at the scene's size with the game's SMAA. While DLSS or FSR runs (`dlaa`, any mode), the other
|
||||
values still choose the pass: in the native modes it smooths the upscaler's picture after the bloom, in the scaling
|
||||
modes it runs on the scene before the upscaler scales it.
|
||||
- HDR (`vk_hdr.c`): the game tonemaps its scene into a float target, upscales it, draws the HUD into a second float
|
||||
target and copies that into the 8-bit sRGB window texture it presents. With `NX2NAVI_HDR=1` the tonemap shader gets
|
||||
the function of `shaders/hdr_tonemap.frag` spliced in where its SDR curve clamps each channel, so the float picture
|
||||
|
||||
@@ -88,7 +88,9 @@ identity (`NX2navi.Launcher`), so the taskbar groups and pins it under NX2navi r
|
||||
Screens (`launcher/ui/app.py`): first run (dump, install folder, Desktop Shortcut, Check for Updates at Start,
|
||||
Update Channel, Begin Installation); the steps of an install, update or rebuild with their progress, the build log's
|
||||
last lines and Cancel, and after a failure Try Again and Copy Report; home (Play, Updates, Game Folder, Saves,
|
||||
Rebuild the Game, Customize Launcher, Settings); customize (Color Scheme, with Custom Background Color, Panel Color and
|
||||
Mods, Rebuild the Game, Customize Launcher, Settings); mods (Open Mods Folder, Add a Mod, Add a Mod Folder, one On/Off
|
||||
row for each mod, More Mods when they fill more than a page, Load Order, Back); load order (each mod with its place,
|
||||
left and right to move it); customize (Color Scheme, with Custom Background Color, Panel Color and
|
||||
Button Color, Background, with a picture set Background Dimming and Remove Background, Animations, Sounds, Add to Steam on
|
||||
Windows, Back); the colour picker (Hue, Saturation, Brightness, Hex Code, Reset, Done); saves (Export Save, Add Log and Settings, Export To, Import a Save, Import a Save Folder,
|
||||
Open Saves Folder, Back); settings (update check, Install Updates Automatically, Hide Launcher While Playing, Keep
|
||||
@@ -344,6 +346,38 @@ copies the current save to `saves/backup <date time>` and makes the import the s
|
||||
(`runtime/fs_host.c` `import_pending`), and the menu says where the old save went. An import in the launcher replaces
|
||||
one still waiting from the menu.
|
||||
|
||||
## Mods
|
||||
|
||||
Mods (home, under Saves; `launcher/mods.py`) is where the player puts the mods they download. The game reads the game
|
||||
folder's `mods` folder (`runtime/mods.c`; `mods_dir` in nx2navi.ini names another): one folder per mod, holding a
|
||||
`romfs` folder with the game files it replaces, an `exefs` folder with code patches (`.ips`, `.pchtxt`) or a `cheats`
|
||||
folder, either at its top or in the Atmosphere layout (`atmosphere/contents/0400486024DEC000/romfs` and the others
|
||||
`tools/mod_files.py` lists).
|
||||
|
||||
A mod goes in as it came. Play first puts the folder in order (`mods.prepare`): an archive (`.zip`, and `.7z` or
|
||||
`.rar` through Windows' own `tar`, which reads them on Windows 10 and 11) is unpacked into a folder of its name unless
|
||||
that folder is there already, and the archive stays; a mod folder whose files sit one or more folders down (an archive
|
||||
that held the mod's own folder) gets them moved up; a `romfs`, `romfslite`, `exefs` or `cheats` folder put straight into
|
||||
the mods folder becomes a mod of its own, *Unnamed mod*. An archive that would write outside its folder is refused.
|
||||
Nothing is deleted. Add a Mod and Add a Mod Folder do the same for an archive or folder the player picks, which is
|
||||
unpacked or copied into the mods folder under a free name; Open Mods Folder opens it.
|
||||
|
||||
Each mod has an On/Off row; its description says what it changes (how many game files, code patches, cheats), which
|
||||
other mod changes the same files and which of the two wins, and why the game leaves it off when it does: a code module
|
||||
(`subsdk*`), a download with options to pick from (several folders that each hold a mod), a mod for another game or
|
||||
another version, or nothing the game reads. Load Order sets which mod wins a file two of them change: the higher one.
|
||||
The switches and the order are the game's own settings, `mods_disabled` and `mods_order` in nx2navi.ini, written as the
|
||||
game writes them; they apply at the game's next start, so they wait while it runs.
|
||||
|
||||
**Mods that change the game's code.** The game is lifted from the console's code ahead of time, so code cheats and
|
||||
ExeFS patches cannot be applied while it runs: the build turns them into patch sets of the lifted code
|
||||
(`tools/cheats.py`, `tools/exefs_patches.py`) that the game switches on with their mod, and the Cheats tab of the
|
||||
game's menu switches each cheat. The lift step's key names those files, so a build lifts and compiles again when they
|
||||
change (only the changed parts compile, and the shaders stay prepared), and `build-cache/mod-code.json` records the
|
||||
files it took up. When an enabled mod brings code no build has seen, Play builds the game again first (a few minutes;
|
||||
the home's Mods row says "Build Waiting") and starts it after. A Play from Steam then opens the window for that build.
|
||||
Code mods are built from the game folder's own `mods` folder only.
|
||||
|
||||
## Importing a save folder
|
||||
|
||||
Import a Save Folder (Saves) makes another save the game's own. A save put into the game folder's `saves` folder (its
|
||||
|
||||
@@ -15,6 +15,16 @@
|
||||
for the launcher; a GPU with Vulkan 1.3 and `VK_EXT_external_memory_host` (current NVIDIA and AMD cards). A GPU without
|
||||
`VK_EXT_mesh_shader` gets the mesh shader fallback, untested on such a card.
|
||||
|
||||
## New
|
||||
|
||||
- **Mods in the launcher.** Mods, on the launcher's home screen, opens the mods folder and adds a mod you downloaded,
|
||||
as its .zip, .7z or .rar file or its folder; one put into the mods folder by hand works as well. Before the game
|
||||
starts, the launcher unpacks archives and moves a mod's files to where the game looks for them when they sit a folder
|
||||
or two down. Each mod has an On/Off switch and says what it changes, which other mod changes the same files and
|
||||
which of them wins, and why the game cannot use it when it cannot; Load Order sets which mod wins. A mod with code
|
||||
patches or code cheats is built into the game before it starts, which takes a few minutes the first time: the
|
||||
launcher's own build left those out until now.
|
||||
|
||||
## Faster
|
||||
|
||||
- **A new install no longer builds its pipelines while you play.** A release now carries a list of the graphics
|
||||
@@ -76,6 +86,22 @@ for the launcher; a GPU with Vulkan 1.3 and `VK_EXT_external_memory_host` (curre
|
||||
us. Why the distance comes out negative is not known yet.
|
||||
- **The launcher run from the source with an older Python** stopped at *Gather Build Tools* with nothing but "No
|
||||
module named 'zstandard'". It now says so on its first screen, with the command that installs what is missing.
|
||||
- **A flickering light line along the bottom and right edges of the picture with FSR 4, FSR 3.1 or DLSS.** To let the
|
||||
upscaler build a smoother picture, the scene is drawn moved by a fraction of a pixel, a little differently each frame.
|
||||
When it moved up or to the left, AMD's driver left the last row or column of the scene undrawn, the fog's colour stayed
|
||||
there, and the upscaler blended it into the edge. That row or column is now filled from the one next to it before the
|
||||
upscaler reads the scene.
|
||||
|
||||
## Changed
|
||||
|
||||
- **The Anti-aliasing setting works with FSR 4, FSR 3.1 and DLSS.** Choosing Game SMAA, Off, FXAA or SMAA (Ultra) with
|
||||
one of them on under Upscaling used to switch the upscaler off and leave the picture to bilinear scaling. Now the
|
||||
upscaler stays, its TAA keeps running, and the chosen pass runs along with it (the row says "plus TAA from
|
||||
Upscaling"): *Off* leaves the edges to the TAA alone, *SMAA (Ultra)* smooths what the TAA leaves. Picking FSR or DLSS
|
||||
under Upscaling keeps the Anti-aliasing choice too, and the row's TAA entry now sets FSR 4 where it runs, no longer
|
||||
FSR 3.1 in its place.
|
||||
- **The performance overlay shows the anti-aliasing** under Upscaling, as *TAA + SMAA (Ultra)* and the like while FSR
|
||||
or DLSS runs.
|
||||
|
||||
## Known issues
|
||||
|
||||
|
||||
Reference in New Issue
Block a user