summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJason Ekstrand <jason@jlekstrand.net>2020-04-20 11:34:30 -0500
committerJason Ekstrand <jason@jlekstrand.net>2020-04-22 02:58:42 +0000
commite89eb51eda917b91a10bb0b57c6ffd5bcfbe603d (patch)
tree83503f8fb01ce1267320f37cb82e65c5cba2ba4c
parent0c767078e749df995fc1358ba89b9a4d503cd2c1 (diff)
README: Add a note about steam game fossil capture
Reviewed-by: Eric Anholt <eric@anholt.net>
-rw-r--r--README.md9
1 files changed, 9 insertions, 0 deletions
diff --git a/README.md b/README.md
index 196d7d8..5dfee32 100644
--- a/README.md
+++ b/README.md
@@ -120,3 +120,12 @@ You can then compare two different csv files using the report-fossil.py script:
A fossilize.sh script is provided to assist in capturing fossils, you may
need to modify it based on where fossil lives on your system.
+
+For steam games, fossils are currently captured automatically. Once the game
+has been run for a while, you can find the fossils at
+`$HOME/.local/share/Steam/steamapps/shadercache/$APP_ID/fozpipelinesv4/steamapp_pipeline_cache.foz`.
+Note that you need to use the file named `steamapp_pipeline_cache.foz` and not
+the fossil file named `steam_*` because the later one may contain fossilized
+pipelines from other drivers which may use extensions not supported by your
+driver. The `steamapp_pipeline_cache.foz` file contains only those pipelines
+which have actually been seen during the run on your actual driver.