Say where the boot's list of compute shaders comes from: mostly the shader preparation, not play.

An installed copy's warm list has 42,344 variants, 42,142 of them from shader-prepared.bin, and its 4,066 compute shaders are what the boot kept pipelines for. The comments and the settings text said the list grew with the play history; a copy with prepared shaders held the 2.3 GiB from its first boot. Comments, docs and the ini text only.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
(cherry picked from commit ea984fe05b995c5dad1e0f49c5f44de9ee8f19b2)
This commit is contained in:
chrg6
2026-11-10 03:29:15 -05:00
parent 1567ff8df4
commit 1b9016896a
4 changed files with 16 additions and 14 deletions

View File

@@ -106,8 +106,8 @@
# lib_prebuild_threads = 2
# How many compute pipelines the start builds and keeps: those of the compute shaders the game used most recently.
# Every other known one is built into the pipeline cache and released again, and made from the cache when the game
# first uses it (well under a millisecond). all: the start keeps every compute shader the game ever used, as versions up
# to 0.6.1 did; with a long play history that held more than 2 GB of video memory. 0: none are kept.
# first uses it (well under a millisecond). all: the start keeps the pipeline of every known compute shader, as
# versions up to 0.6.1 did, which held more than 2 GB of video memory. 0: none are kept.
# compute_keep = 512
# 1: very large compute shaders that no cache holds are built on one background thread after the start. 0: each is
# built when the game first uses it, which can hold that frame for a second or two.