mirror of
https://github.com/tangerineturtle1/NX2navi.git
synced 2026-11-17 11:29:58 -04:00
Let the game go on while the GPU runs the end of the last frame, with tail_early = 1.
The game waits each frame until the GPU has finished the frame before. In Hyrule Field with FSR 4 the last of that work is one part of 4.7 ms, the temporal upscaler and the interface drawn after it, then 1.4 ms of write-backs, and what the game reads of the frame is done before the upscaler runs. With NX2NAVI_TAIL_EARLY the replay records that tail into a command buffer of its own, and when it hands the CPU nothing but timestamps, writes no pool memory but inline uniform updates of mirrored blocks and reads no guest memory late, the write-backs go to the queue before it with the executed timeline's signal. The game's waits end there, and the GPU runs the tail while the next frame is prepared. The GPU's commands are the same; a tail that fails a test goes as before. Off by default. RX 7900 XT, Ryzen 7 5800X3D, 3440x1440, FSR 4 Native AA, one batch, replay workers off: 50.7 against 42.5 fps standing and 56.0 against 45.9 along the field route; with FSR 3.1, 51.8 against 47.8 and 54.9 against 52.3. With three replay workers, FSR 4, standing: 63.5 against 49.4. The screenshots matched those without it standing, along the route and through warps to five areas, with no black frame outside the loading screens of both. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
This commit is contained in:
19
docs/releases/v0.9.3.md
Normal file
19
docs/releases/v0.9.3.md
Normal file
@@ -0,0 +1,19 @@
|
||||
## 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.
|
||||
|
||||
## 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 *Replay workers (experimental)*: 0 to 8, after a restart.
|
||||
Reference in New Issue
Block a user