Show the low-end GPU mode's settings under its switch in the Game tab, and read them only while the mode is on.

The settings had a tab of their own; they are rows of the Game tab now, listed under the switch once the mode is on after a restart, and the tab is gone. With the mode off every one of them reads as unset, whatever nx2navi.ini or the environment says, so nothing of the mode acts unless a player turned it on; the build reads guest_opt the same way. The notes describe that, and take the white edges in towns and the dropped textures from the known issues to the fixes.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
This commit is contained in:
chrg6
2026-11-12 13:59:43 -05:00
parent 857d22fe4f
commit 26f3dc47ec
10 changed files with 174 additions and 140 deletions

View File

@@ -33,11 +33,10 @@ for the launcher; a GPU with Vulkan 1.3 and `VK_EXT_external_memory_host` (curre
- A texture the game reads after another image was drawn over its memory gets memory of its own, which removed
teal splotches from the fog of Kokiri Forest on that card.
Each of these also has a key of its own, listed with `low_end_gpu` in nx2navi.ini.example.
- **A settings tab for those cards**, *Lama patches*, by Tobim6: how many released textures are kept, the video
memory reserve, the upload batch size, mesh shader emulation, foliage detail (`foliage = full`, `reduced` or
`off`) and compiling the game's code at -O2 at the next *Rebuild the Game* (`guest_opt = 2`, a build several times
longer).
While the mode is on, the Game tab lists its settings underneath the switch: the video memory limit and reserve,
the upload batch size, mesh shader emulation and its memory, foliage detail (`foliage = full`, `reduced` or `off`)
and compiling the game's code at -O2 at the next *Rebuild the Game* (`guest_opt = 2`, a build several times
longer). With the mode off none of them is read, also when nx2navi.ini sets one.
- **Link's own motion for DLSS, FSR 3.1 and frame generation** (`selective_motion = 1` in nx2navi.ini, off by
default): Link and the equipment attached to him are drawn a second time with last frame's pose, so the upscaler
gets their real motion in fast turns, attacks and jumps instead of an estimate. It has not been played by us yet. By
@@ -79,6 +78,15 @@ for the launcher; a GPU with Vulkan 1.3 and `VK_EXT_external_memory_host` (curre
the same memory in another format. That texture was dropped every 600 frames as overwritten although the game still
read it, and the frame that dropped it made it again from the scene's raw bits: in a player's recording one frame at
a sixth of its brightness. A texture that is still read is kept now.
- **Kerb, stair and wall-top edges drawn white for one frame in towns.** In a town the game registers a round of 30
to 60 sharper textures every four or five frames, from another of its threads, while the frame before is still
being drawn. Each registration took effect at once and changed the texture slots under that frame, and some of its
surfaces were drawn untextured, twice four frames apart. A registration now takes effect between two submissions,
in the order the game made it.
- **Textures going plain for a moment after the game let go of them.** A texture the game has finalized stays on
screen until the game puts another in its place. Nothing looked such a texture up any more, so it counted as unused
and was dropped once the kept textures passed their size limit, although every frame still drew with it. One that
was drawn with lately is kept now.
- **The game hanging with the draw replay on several cores.** Two replay threads could wait for each other at the
end of a render pass, each holding the lock the other needed. By leonardochappuis (pull request #697).
- **Lines drawn one pixel wide whatever width the game set.** The width is passed on now where the card supports wide
@@ -126,8 +134,6 @@ for the launcher; a GPU with Vulkan 1.3 and `VK_EXT_external_memory_host` (curre
Performance and 3.9 ms at Native AA on a Radeon RX 7900 XT (FSR 3.1: 0.5 ms). Measured standing in Hyrule Field at
3416x1440: FSR 4 Native AA 52 fps, Quality 53, Ultra Performance 55; FSR 3.1 Native AA 55, Ultra Performance 66;
without an upscaler 70.
- In towns, the edges of kerbs, stairs and wall tops can be drawn white for one frame when the game brings in a
batch of sharper textures. Its cause is not found yet.
- `low_end_gpu = 1` was run by its author on a Radeon RX 580, not by us. Please report how it behaves on your card.
- FSR 4, its frame generation and the AMD-only fixes were not run by us on the cards they are for before this
release.