fix(appimage): emulators and other AppImage programs get the game GPU setting (#2288)

The session sets TU_DEBUG=sysmem for the Steam client's interface and hands
games their own value in DROIDDECK_GAME_TU_DEBUG, which droiddeck-game-env
applies to Steam launches (#1188). droiddeck-appimage-run never did, so
emulators and other AppImage programs rendered every pass through system
memory instead of Turnip's per render pass choice.

Apply the game value in droiddeck-appimage-run the same way: an empty
value unsets TU_DEBUG, any other value replaces it. Chromium-based apps,
like the Steam client's own interface, keep the session's setting.
This commit is contained in:
MaxsTechReview authored and GitHub committed 2026-11-08 12:23:30 -05:00
1 parent 3fef1f3fa1
commit 3bb279f635
3 files changed
+27 -2

No files matched your search

@@ -25,6 +25,12 @@ if [ -n "$(find -H "$APPDIR" -maxdepth 4 \( -name chrome-sandbox -o -name chrome
flags+=(--ozone-platform=x11)
fi
fi
if [ -n "${DROIDDECK_GAME_TU_DEBUG+set}" ]; then
if [ ${#flags[@]} -eq 0 ]; then
if [ -n "$DROIDDECK_GAME_TU_DEBUG" ]; then export TU_DEBUG=$DROIDDECK_GAME_TU_DEBUG; else unset TU_DEBUG; fi
fi
unset DROIDDECK_GAME_TU_DEBUG
fi
qt=$(cat "$dir/qt" 2>/dev/null)
case $qt in wayland|xcb) ;; *) qt=auto ;; esac
wayland=${GAMESCOPE_WAYLAND_DISPLAY:-${WAYLAND_DISPLAY:-}}