fix(game-env): turn off Proton's tabtip unless the Steam keyboard is enabled (#2595)

* fix(game-env): turn off Proton's tabtip unless the Steam keyboard is enabled

Proton's tabtip only opens Steam's keyboard with SteamDeck=1, but it always
runs UI Automation queries inside the focused game, and those calls crash
games that answer them (Godot 4.5 AccessKit). Game launches now add
tabtip.exe=d unless SteamDeck=1 or the user's overrides name tabtip.

* fix(game-env): match WINEDLLOVERRIDES modules split by spaces and tabs

* fix(game-env): count only tabtip.exe entries with a load order as the user's own setting

* fix(game-env): count *tabtip.exe and tabtip.exe.dll overrides as the user's own setting

* test(game-env): cover keyboard overrides during sync fallback
This commit is contained in:
MaxsTechReview authored and GitHub committed 2026-11-15 02:48:50 -05:00
1 parent fdf3d98c36
commit 7254a88391
4 files changed
+107 -19

No files matched your search

+6 -1
View File
@@ -283,7 +283,12 @@ DroidDeck instead publishes an atomic JSON snapshot at
`/root/.config/droiddeck/game-environment.json`. Both its Valve ARM64 Proton
wrapper and adopted third-party Proton wrappers execute `droiddeck-game-env`,
which reads that snapshot for each real game launch and uses `execvpe` to start
Proton. Probe prefix `compatdata/0` and non-launch verbs are unchanged. Malformed
Proton. Probe prefix `compatdata/0` and non-launch verbs are unchanged. A game launch
adds `tabtip.exe=d` to `WINEDLLOVERRIDES` unless the launch has `SteamDeck=1`
or the overrides already set `tabtip.exe` (also as `*tabtip.exe` or
`tabtip.exe.dll`): Proton's tabtip only opens Steam's
keyboard with `SteamDeck=1`, but it always runs UI Automation queries inside the
focused game, which crash games that answer them (Godot 4.5 AccessKit). Malformed
configuration falls back to the inherited environment without evaluating its
contents. Both component and environment selection normalize signed non-Steam
prefix IDs to unsigned IDs.