Files
NX2navi/docs/releases/v0.9.3.md
epicmeme546 f5da269add Remove the experimental co-op through Steam.
This takes back the three commits that added it (cd2f9f1, e60677e, a01910d): its runtime layer and Steam binding, the Co-op tab and what it drew over the game, the launcher's copy of Steam's library file, its settings, tests and docs. The tree is as it was before them, with the bug capture that came after kept: its note on screen no longer makes room for co-op's lines, and dbg_area, which the co-op had brought and the capture uses, stays.

The four settings of that co-op join the retired names, so a settings file that still has them logs no unknown key. A steam_api64.dll that the launcher put beside the game is left where it is: nothing loads it any more.

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

43 lines
3.7 KiB
Markdown

## 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.
## New
- **F8 saves a bug capture.** When you see something wrong, press F8: the game writes where Link stands, the area,
the camera, the picture on screen, your settings, the frame times around the press, the end of the log and your
save into one folder under `logs\captures`, and a note on screen gives the capture its number. Telling us "capture
3" is then enough: a test run starts at that place with that camera and those settings
(`python tools/capture_run.py 3`, `docs/bug-capture.md`) instead of somewhere else on another save. Until now F8
did something only with the flight recorder on (`flight = 1`); its F8 dump now goes into the capture's folder.
## 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**: *Helpers work ahead* (`replay_pipe`, 0 to 4),
*Helpers take small jobs* (`replay_small`, 0 to 64) and *Start next frame early* (`tail_early`). A row whose setting
does nothing without another one is greyed out and says which it needs.
- **The hidden co-op beta is gone.** The co-op of 0.8.0 (shown only with `coop_beta = 1`) shared story progress
through a relay a player had to run and never showed the other players. Its code, its settings (the `[coop]` section
of nx2navi.ini), its relay script and its menu tab are removed; lines of it left in an nx2navi.ini do nothing, and a
bug report still keeps their values out. A new co-op is being built in its place.