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

@@ -126,11 +126,11 @@
# pipe_skip_steady = 1
# How many milliseconds the draws of one frame may wait, in all, for a missing pipeline to be linked from the shader
# libraries in the graphics driver's cache before they are dropped (0 to 100; 0: dropped at once, as before).
# pipe_link_ms = 16
# pipe_link_ms = 6
# How many milliseconds one missing pipeline is waited for, counted from the first draw that needed it (1 to 50).
# With its shader libraries in the driver's cache a pipeline takes 3 to 8 ms; one that takes longer is being
# compiled, and its draws are left out of the frames until it is ready.
# pipe_link_draw_ms = 8
# With its shader libraries in the driver's cache a pipeline takes 2 to 8 ms; what is not ready by then is left out
# of the frames until it is. A longer wait leaves fewer draws out and makes those frames longer.
# pipe_link_draw_ms = 3
# When a draw finds its pipeline missing, the rest of the commands the game submitted with it are read ahead and the
# shader libraries of every other pipeline they will need are built at once on background threads, so the later draws
# find theirs ready instead of waiting one after another or being left out of a frame. 0: off, as before.