Files
NX2navi/docs/releases/v0.9.3.md
epicmeme546 cb5965d14e Name the Testing rows of the performance settings in plain words and make two of them switches.
The rows are now CPU helper threads, Helpers work ahead, Helpers take small jobs and Start next frame early, each
with a short description of what it does and what it gained. Helpers work ahead and Helpers take small jobs are
switches: on writes replay_pipe = 4 and replay_small = 16, the values measured best, and another value set in
nx2navi.ini shows as on and stays.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
2026-11-13 00:24:38 -05:00

2.6 KiB

Faster

  • Experimental: the next frame no longer waits for the end of the last one's graphics work (tail_early = 1 in nx2navi.ini, off by default; contributed by epicmeme546). The game waits each frame until the graphics card has finished the frame before. The last of that work is the upscaler (FSR 4, FSR 3.1 or DLSS) and the interface drawn after it, and nothing the game reads comes out of it. With the setting on, the copies of what the card wrote for the game go before that last stretch and the game goes on once they are there, so the card finishes the picture while the next frame is already being prepared. The card runs the same work as before. On an RX 7900 XT with a Ryzen 7 5800X3D at 3440x1440, FSR 4 Native AA, Hyrule Field: 50.7 instead of 42.5 fps standing and 56.0 instead of 45.9 along a route; with replay_workers = 3 as well, 63.5 instead of 49.4 standing. With FSR 3.1, whose pass is shorter, 51.8 instead of 47.8 standing. Its pictures matched standing, along the route and through warps to five areas, but it is new: leave it off to play, and report what you see if you try it. It does nothing without one of those upscalers, and nothing yet on NVIDIA and Intel cards, where the lazy write-back is on.
  • Experimental: the replay workers take more of a frame off the game's render thread (replay_pipe and replay_small in nx2navi.ini, both 0 by default, both with replay_workers; contributed by epicmeme546). With replay_pipe = N, 1 to 4, the thread goes on past up to N groups of draws its workers still record. With replay_small = N as well, a group of N draws or more that is too small to share out goes whole to one worker. On the same PC standing in Kokiri Forest, with tail_early = 1: 60.5 fps with 3 workers alone, 62.2 with 5 workers and replay_pipe = 4, 63.2 with replay_small = 16 added, against 45.4 with all four settings off. The pictures matched there and through warps to five areas.

Changed

  • The draw replay on several CPU cores is off by default again (replay_workers = 0). With three workers on by default in 0.9.1 and 0.9.2 some players' games ended with a lost graphics device; the cause is not found yet. The settings menu has it under Game, Testing, as CPU helper threads (experimental): 0 to 8, after a restart.
  • The other experimental performance settings have rows there too, each a switch: Helpers work ahead (on is replay_pipe = 4), Helpers take small jobs (on is replay_small = 16) and Start next frame early (tail_early). A row whose setting does nothing without another one is greyed out and says which it needs.