mirror of
https://github.com/tangerineturtle1/NX2navi.git
synced 2026-11-18 09:09:56 -04:00
Replay workers take their occlusion query slots in the order of the stream.
The chunks of a parallel group took query slots from the ring as they recorded, so the slots of the group's chunks interleaved. The completion thread reads and resets slots in runs that follow the ring, and with interleaved slots it made four times the result calls and a reset per slot: the wait after a frame's first submission ended 3.5 ms after the GPU had run it instead of 0.6 ms, and the replay time the workers saved went into that wait (44 fps with 3 workers as without). The front pass now gives each chunk a block of slots, as many as its draws that count samples and render, in the order of the stream; a segment's slots are taken in ring order. Standing in Hyrule Field, 3 workers: 49.8 fps against 43.7 with the workers off. NX2NAVI_GPU_TIMELINE=<frame> writes four frames from that present on to the log: each replay, each timed part's submit and GPU run, the waits for the GPU and the workers' groups, so a run shows whether the GPU waits for the replay, a wait, or the CPU behind one. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
@@ -536,6 +536,7 @@ void gfx_exit_log(void) {
|
||||
|
||||
static void vk_be_present(const tex_t *t, const int crop[4], uint64_t at_ns) {
|
||||
vk_sync_start();
|
||||
gfx_tl_present();
|
||||
vk_dlssg_game_present();
|
||||
if (!gfx_replay_async()) {
|
||||
uint64_t frame = __atomic_add_fetch(&gfx_counters.frames, 1, __ATOMIC_RELAXED);
|
||||
|
||||
Reference in New Issue
Block a user