fix(steam): skip only Steam's own driver-query run in compatdata/0

Review of #1708: matching the file name alone also caught
getcompatpath for that path and a game that happens to use the name.
The wrappers now skip only "run …/d3ddriverquery64.exe" (or the 32-bit
name) with STEAM_COMPAT_DATA_PATH in compatdata/0, which is how the
client calls it; every other verb and prefix goes on to Proton.

(cherry picked from commit c5e8ad0f80)
This commit is contained in:
The412Banner committed 2026-10-28 04:42:12 +00:00
1 parent 58c262a32e
commit 4745517101
2 files changed
+25 -13

No files matched your search

@@ -276,12 +276,13 @@ bl_vacdiag() {
}
"""
# Steam's shader pre-caching runs its D3D driver query through every Proton tool at each start. Here it has never
# succeeded (exit 1 every time), and each run started Wine in compatdata/0, where the two Protons upgrade the prefix
# back and forth for many seconds while the game starts. Steam gets the same failure without starting Wine.
# Steam's shader pre-caching runs its D3D driver query through every Proton tool at each start, as
# "run <client>/bin/d3ddriverquery64.exe" in compatdata/0. Here it has never succeeded (exit 1 every time), and each
# run started Wine in compatdata/0, where the two Protons upgrade the prefix back and forth for many seconds while the
# game starts. Steam gets the same failure without starting Wine; other verbs and prefixes are left alone.
BL_DRIVER_QUERY_SKIP = """
case "${1##*/}" in
d3ddriverquery64.exe | d3ddriverquery.exe)
case "$verb:${1##*/}:${STEAM_COMPAT_DATA_PATH%/}" in
run:d3ddriverquery64.exe:*/compatdata/0 | run:d3ddriverquery.exe:*/compatdata/0)
echo "droiddeck-proton: Steam's D3D driver query is not run (it fails here and would start Wine in compatdata/0)" >&2
exit 1 ;;
esac