mirror of
https://github.com/tangerineturtle1/NX2navi.git
synced 2026-11-18 00:29:58 -04:00
F8 now always writes a folder under logs/captures: the area, Link's position and rotation, the camera of the frame on screen and the game's own, the presented frame as a PNG, frame times around the press, the machine, the settings that differ from the defaults, the end of the log, the save, and the game's flags and texts. A note on screen names the capture. The flight recorder's F8 dump goes into the capture's folder. NX2NAVI_CAPTURE_REPLAY starts a run on a capture's settings, teleports to its area, walks Link to where he stood and puts the free camera where the camera was; tools/capture_run.py prepares the profile from the capture's save, runs it and compares the two captures. docs/bug-capture.md has the files and the steps. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
55 lines
5.0 KiB
Markdown
55 lines
5.0 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
|
|
|
|
- **Experimental: co-op through Steam** (the menu's new Co-op tab; off by default; `coop_steam = 1` in nx2navi.ini). Up to
|
|
four players, each in their own game and save, meet in a room: *Create a room* gives a room ID to pass on, *Join a
|
|
room* takes one, and *Invite a friend* sends a Steam invite. Nobody forwards a port and nobody runs a server: rooms
|
|
are Steam lobbies and the games talk through Steam's network. NX2navi signs in to Steam as its test app, so Steam
|
|
shows you as playing Spacewar. In a room you see the other players' names where their Link stands (with DLSS, FSR
|
|
or TAA on), you can chat, and progress is shared: story, chests, doors, items and songs count for everyone, while
|
|
small keys, rupees, ammunition and hearts stay each player's own. Your save is copied to `coop-backup` in the
|
|
profile folder before anything of a room reaches it. It needs Steam running and one Steam game from 2021 or later
|
|
installed: co-op uses Steam's library file, `steam_api64.dll`, which NX2navi may not ship, so the launcher copies
|
|
it beside the game from your own Steam library when it starts the game. Not
|
|
yet: the other players as a Link model, shared enemies, and invites that start the game for a friend who has it
|
|
closed. Everyone needs the same NX2navi version. `docs/coop.md` has the details and how to go back to a save.
|
|
|
|
- **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 co-op beta of 0.8.0 is replaced.** It shared story progress through a relay a player had to run, with a
|
|
forwarded port, and never showed the other players. Its relay, its rules and pools, its settings and its hidden tab
|
|
are gone; lines of it left in an nx2navi.ini do nothing (its `coop = 1` does not turn the new co-op on), and a bug report still keeps their values out. See "New".
|