mirror of
https://github.com/tangerineturtle1/NX2navi.git
synced 2026-11-17 13:39:58 -04:00
Merge branch 'claude/pipeline-stutter-110e1b' into test-all-fixes
# Conflicts: # docs/building.md
This commit is contained in:
@@ -131,7 +131,12 @@ keeps per-core data without locks and relies on that, so the host models it (`ru
|
||||
ring of Vulkan `{x, y, z}` records filled on the GPU.
|
||||
- Pipelines: `VK_EXT_graphics_pipeline_library` where the driver has it: stage libraries compiled ahead, a fast link
|
||||
at a new state, an optimised pipeline replacing it from a background thread. A draw whose pipeline is not ready is
|
||||
skipped when one of its pass's targets was rendered in the previous frame, and waits otherwise. Three things keep
|
||||
skipped when its pass is one the game renders frame after frame: one of its targets was rendered in the last few
|
||||
frames, or in eight frames or more at any time, which keeps the first frame after a loading screen from reading as
|
||||
all new (`runtime/vk_target_frames.h`). A draw into a target rendered for the first time, and a full-screen draw,
|
||||
wait instead, from one pool of 50 ms a presented frame (`pipe_frame_wait_ms`; `runtime/vk_exec_draw.c`
|
||||
`prepare_draw_ex`, `frame_wait`); what is not ready when the pool is spent is skipped and built on a worker, so no
|
||||
frame waits for pipelines much longer than that. Three things keep
|
||||
that short on a first visit (`runtime/vk_pipeline.c`): a pipeline whose fragment shader reads a target of its own
|
||||
pass is fast-linked like any other, the feedback loop flags being part of the fragment output library alone
|
||||
(`gpl_feedback`); the library workers also link the pipelines of skipped draws, so a burst of new materials is
|
||||
|
||||
@@ -334,6 +334,12 @@ A change to the mouse camera's stick deflection (`runtime/input_map.c` `input_mo
|
||||
deflection at each camera speed: a slow movement is divided by the factor, a fast flick reaches full tilt. No game
|
||||
files.
|
||||
|
||||
A change to which render passes count as drawn frame after frame (`runtime/vk_target_frames.h`: a draw into one is
|
||||
skipped while its pipeline builds, a draw into any other waits) passes `python tests\target_frames_check.py`, which
|
||||
builds the header alone and replays an area change after a loading screen from a player's log: the scene, probe and
|
||||
half-resolution passes are per-frame again at once, a lookup table, a volume's slices and an icon capture still wait,
|
||||
and an image taken over by another texture starts without the history of the one before. No GPU, no game files.
|
||||
|
||||
The lifter (`recomp/`) and the CPU headers (`runtime/cpu.h`, `runtime/simd.h`) are checked against Unicorn. Every lifter
|
||||
change passes these, all run with `.venv`:
|
||||
|
||||
|
||||
@@ -31,7 +31,7 @@ cards).
|
||||
left the draw out while one thread linked it. Now the rest of the submission is read ahead and the pipelines it
|
||||
will need are queued at once, several threads link them, and pipelines whose shader reads a target of its own pass
|
||||
are linked the fast way like the others. Walking into Kokiri Forest for the first time, the worst frame went from
|
||||
434 ms to 44 ms in one measurement each, with no frame over 50 ms.
|
||||
434 ms to 89 ms and the frames over 50 ms from 5 to 3, in one measurement each.
|
||||
|
||||
## New
|
||||
|
||||
|
||||
Reference in New Issue
Block a user