Turn the settings for older graphics cards on with one key, low_end_gpu = 1, and leave them off without it.

Mesh shaders as compute, the texture that gets memory of its own, staged mirror uploads and the shorter wait for the GPU, widened write-watch queries, the video memory limits and reserve, early upload batches, the asynchronous replay, the hot-pool rule and the recording thread on AMD cards without mesh shaders were measured on a Radeon RX 580 and run on no other card. Each keeps what 0.9.1 did unless the key or its own setting says otherwise; the key gives the defaults the way the device profile does. The notes describe them as that option, hold main's two new entries in one Changed section, and list the white edges in towns as a known issue.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
This commit is contained in:
chrg6
2026-11-12 13:00:13 -05:00
parent 052c60dc0d
commit 2324a74602
10 changed files with 105 additions and 58 deletions

View File

@@ -11,24 +11,32 @@
**Requirements:** Windows 10 or 11; an x86-64 CPU with SSE4.2; 16 GB of RAM; about 30 GB free for the game and 1.5 GB
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` runs the game's mesh shaders as compute shaders (new in this release, see below).
`VK_EXT_mesh_shader` gets the mesh shader fallback as before, or runs the game's mesh shaders as compute shaders with
`low_end_gpu = 1` (new, see below).
## New
- **Grass and foliage on graphics cards without mesh shaders** (AMD before RDNA 2, such as the RX 400 and 500 series
and Vega; NVIDIA before the GTX 16 and RTX 20 series). The game draws its grass, moss and other foliage with mesh
shaders. On a card without them these now run as compute shaders, and what they make is drawn as ordinary
triangles. It is on by default on such a card and does nothing on any other; `mesh_emulation = 0` in nx2navi.ini
goes back to what 0.9.1 did there. Written and run on a Radeon RX 580 by Tobim6.
- **Video memory kept within what the card has free.** Textures and buffers are allocated within the budget the
driver reports for each memory heap, with 512 MB kept free (`vram_reserve_mb`), and a texture that does not fit the
first heap goes to the next one with room. A large batch of texture uploads is handed to the GPU early instead of
growing until a submit runs out of memory. By Tobim6.
- **A settings tab for older and slower 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 three settings that stay off unless you choose them: preparing frames on a thread of their own
(`replay_async`), keeping memory pools the game refills every frame in system memory (`mirror_hot`), and compiling
the game's code at -O2 at the next *Rebuild the Game* (`guest_opt = 2`, a build several times longer).
- **An option for older graphics cards: `low_end_gpu = 1` in nx2navi.ini.** It turns on a set of changes written by
Tobim6 and measured on a Radeon RX 580. They are off by default, because they were not run by us on other cards:
- Grass, moss and other foliage on cards without mesh shaders (AMD before RDNA 2, such as the RX 400 and 500 series
and Vega; NVIDIA before the GTX 16 and RTX 20 series): the game's mesh shaders run as compute shaders and what
they make is drawn as ordinary triangles.
- Video memory kept within what the driver reports free, with 512 MB in reserve, and a texture that does not fit
the first memory heap placed in the next one with room. Large batches of texture uploads go to the GPU early
instead of growing until a submit runs out of memory.
- Less waiting for the GPU: the game memory a submission needs is copied while the frame is recorded, and the game
goes on once a frame's first submission is handed over. On the RX 580 the replay's part of that wait went from
12 ms to 6.9, with the recording thread used on AMD cards without mesh shaders.
- Frames prepared on a thread of their own (this one can show a dark or flickering frame now and then), and memory
pools the game refills every frame kept in system memory.
- 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).
- **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
@@ -70,9 +78,6 @@ 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.
- **Teal splotches in the fog of Kokiri Forest.** The game puts its per-frame render targets over each other in
memory, and the fog read its volume after the bloom target had been drawn over it. A texture read in that state gets
memory of its own from then on. By Tobim6.
- **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
@@ -92,21 +97,12 @@ for the launcher; a GPU with Vulkan 1.3 and `VK_EXT_external_memory_host` (curre
## Changed
- **Draws and uploads wait less for the GPU.** The pages of game memory a submission needs are copied while the draw
replay records it, so the game's wait after a frame's first submission ends once the replay has handed it over instead
of when the GPU has run it; a submission whose results the game reads back is still waited for. The texture pool has
8 descriptor sets in turn instead of 4. By Tobim6.
- **The recording thread is used on AMD cards without mesh shaders** (RX 400 and 500, Vega, RX 5000). It stays off on
the newer AMD cards, where it lost the device. On a Radeon RX 580 the replay's part of the game's wait after a
frame's first submission went from 12 ms to 6.9. By Tobim6.
- **The flight recorder** (`flight = 1`, F8) keeps its pictures at 640x360 instead of 320x180 and notes texture slots
that lose their picture, what an upload read and slot registrations. A captured frame also lists the draws that were
rejected while it was prepared (by DeepDaddyTTV, pull request #501). New for reports: a key that dumps the next
frame (`dump_key`), the GPU's time per render pass (`pass_times = 1`) and, in a crash report, what the crashing
thread was building (by Tobim6).
## Changed
- **FSR 3.1 is sharper at Balanced, Performance and Ultra Performance.** It was soft there, most of all while the
camera moved: turning the camera at a steady rate, FSR 3.1 Performance kept 60 % of Native AA's fine detail and Ultra
Performance 50 %, where FSR 4 keeps 89 and 81 %. Below a render scale of three quarters, FSR 3.1's own sharpening now
@@ -129,8 +125,9 @@ 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.
- The changes for older cards (mesh shaders as compute, the video memory budgets, the shorter waits for the GPU) were
run by their author on a Radeon RX 580. Please report how they behave on other cards.
- 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.
- The first visit to an area after an install can still pause for a moment while its textures are decoded.