Create FSR 3.1's pipelines through the pipeline caches kept across runs, so a context is not compiled again at every start the driver's own cache does not serve.

The library creates its pipelines itself and names no pipeline cache. It is now handed pipeline creates of the runtime's in the place of the device's two, and a create without a cache is asked of the pipeline cache first and compiled into the play cache otherwise. ffx_pipe_cache = 0 turns it off. --probe-ffx-cache makes one upscaling context without a window or the game and says where its pipelines came from, and tests/ffx_cache_check.py runs it.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
This commit is contained in:
chrg6
2026-11-11 05:22:56 -05:00
parent b55d2eb3e1
commit d073d80e70
11 changed files with 292 additions and 7 deletions

View File

@@ -180,6 +180,10 @@
# pipeline_cache_play = 1
# The size (MB) at which pipeline-cache-play.bin is folded into pipeline-cache.bin at a start.
# pipeline_cache_play_mb = 64
# 1: the pipelines FSR 3.1 makes for upscaling and frame generation are kept in the pipeline cache files, so a later
# start does not compile them again. 0: FSR 3.1 creates them without those files, as the graphics driver alone keeps
# them.
# ffx_pipe_cache = 1
# 1: where the driver has VK_KHR_pipeline_binary, compiled pipelines are kept in pipeline-binaries.bin under the
# runtime's own keys, so a renamed or updated exe starts without compiling them again (pipeline-cache.bin is then
# not used). Default 0 (pipeline-cache.bin only) while it is being tested.