Copy a frame's uniform blocks at the submit call with the replay on its own thread, and say what that option can show.

With NX2NAVI_REPLAY_ASYNC the uniform snapshot was taken when the replay thread started recording a submission, up to a frame after the game submitted it. The game rewrites that memory without waiting for the GPU: in a graveyard the settings block of the shadow pass held another block's values in the frame its per-frame allocator moved on to the next stretch of memory, about every 364 frames. The submitting thread now takes the copy before it queues the submission (vk_usnap_take), and the replay thread takes it over and leaves out what GPU writes in flight touch (vk_usnap_begin adopt). A frame dump of such a frame shows the block as the game submitted it.

That frame still comes out dark with the option on: vertex, storage and index memory reaches the VRAM mirrors when the replay uses it, as late as the uniform blocks did, and the snapshot covers uniform bindings only. With the option off, 3,000 presents in a row were free of dark and odd frames in that graveyard and in a village; with it on, one frame in about 364 was dark. It gave 65.6 against 56.1 and 64.1 against 54.3 frames per second in those two places. The option stays off by default, and its menu text, the example settings file and the release notes now say that it can show a dark or flickering frame.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
This commit is contained in:
epicmeme546
2026-11-10 06:04:14 -05:00
parent d1bebd34cd
commit 7e23e7309b
6 changed files with 130 additions and 16 deletions

View File

@@ -27,6 +27,13 @@ Draft notes for the release after 0.6.1. The version number is not decided yet.
pass among them once its 50 ms were spent, and the frame was shown without it. Such a frame is no longer shown:
the previous picture stays for the frame or two it takes, while the game runs on (`frame_hold_ms`, 120 by default;
0 shows every frame as before).
- *GPU frame prep on its own thread* (`replay_async`, off by default): the shader constants of a frame are now
copied when the game hands the frame over, not when the other thread gets to it up to a frame later, by which time
the game had sometimes reused that memory (a shadow pass got another block's values about every 364 frames in one
graveyard). The option can still show a dark or flickering frame: vertex, storage and index data are read late in
the same way, and this game rewrites them without waiting for the GPU. In that graveyard and a village, 3,000
frames in a row were clean with the option off, against a dark frame about every 364 with it on. The menu says so
now. It gave 15 to 18 percent more frames per second in those two places.
- The performance overlay's VRAM line counted every program on the graphics card as if it were the game. It now
shows the game's own share beside it (*game 6.8 GB* of 10.4 GB in use, in one measurement).
- Textures out of view for 11 seconds at 165 fps (30 seconds were meant) could show a blank stand-in for a few frames