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:
chrg6
2026-11-12 09:00:37 -05:00
24 changed files with 1388 additions and 151 deletions

View File

@@ -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