Keep the fast link's waits at 3 ms a pipeline and 6 ms a frame.

The 8 ms and 16 ms tried in their place left fewer draws out in a scripted walk, but in play a frame that takes 10 to 14 ms longer felt worse to the player than one that is left out, in two sessions on the same install. The wait stays counted once for each pipeline, and a frame that has left a draw out already still waits for nothing more.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
This commit is contained in:
chrg6
2026-11-12 08:49:26 -05:00
parent b5aea4808b
commit baad032500
5 changed files with 31 additions and 33 deletions

View File

@@ -161,9 +161,9 @@ of them.
What this step leaves for play, and the shared pipeline list. The step translates every shader's default variant
and the shader list's variants and builds each one's stage library or compute pipeline. A whole graphics pipeline
is built ahead at the start of a game folder that has drawn it before (`pipeline-keys.bin`) or whose release
listed it (below); a pipeline met for the first time is linked from its stage libraries in 2 to 8 ms, which its
first draw waits for (`pipe_link_draw_ms`, 8 ms from the pipeline's first miss; `runtime/vk_exec_draw.c`
`link_budget`), except a mesh
listed it (below); a pipeline met for the first time is linked from its stage libraries in 2 to 8 ms, of which its
first draw waits 3 (`pipe_link_draw_ms`, from the pipeline's first miss; `runtime/vk_exec_draw.c` `link_budget`),
except a mesh
pipeline, which has no libraries and compiles whole (0.2 to 1.1 s, its draws left out of the picture meanwhile),
and many of them on a first visit add up to hitches. `tools/pipeline_list.py merge` folds the `pipeline-keys.bin`
and `shader-answers.bin` of game folders that were played, and lists made before, into a pipeline list, with the