mirror of
https://github.com/Droid-Deck/DroidDeck.git
synced 2026-11-19 12:56:06 +00:00
Force game windows fullscreen: off by default (#276)
A game whose resolution differs from the screen's (DiRT 3 at 1280x720) fights --force-windows-fullscreen: every forced resize makes it rebuild its swapchain, and the picture flickers between its own size and the screen's - often from the first menu, before the player can reach the game's resolution setting. It also drove the Xwayland dma-buf leak fixed separately. The switch stays in Settings > Games and the session drawer, now off unless turned on; its hint says when to turn it on (a game coming back small or in a corner after switching apps, e.g. FlatOut) and when to leave it off (flicker). Users who already set it keep their choice. The session script's fallback when the app passes nothing is off as well. Co-authored-by: The412Banner <the412banner@users.noreply.github.com>
This commit is contained in:
1 parent
2ccc8204ad
commit
5ddcde7023
4 files changed
+13
-9
No files matched your search
@@ -179,9 +179,10 @@ if [ -z "${BL_INSIDE:-}" ]; then
|
||||
[ "$mode" = steam ] && args+=(--default-touch-mode 4)
|
||||
# A game that resizes its own window when it loses focus (the Steam menu opening over it) comes
|
||||
# back smaller, and gamescope draws a window that is not flagged fullscreen at its own size in
|
||||
# the top-left corner. Forcing every window to the output's size keeps it filling the screen.
|
||||
# BL_GAMESCOPE_FORCE_FULLSCREEN=0 turns it off.
|
||||
[ "$mode" = steam ] && [ "${BL_GAMESCOPE_FORCE_FULLSCREEN:-1}" = 1 ] && args+=(--force-windows-fullscreen)
|
||||
# the top-left corner. Forcing every window to the output's size keeps it filling the screen,
|
||||
# but a game running at a resolution other than the screen's fights it and flickers, so it is
|
||||
# off unless the app asks for it: BL_GAMESCOPE_FORCE_FULLSCREEN=1 turns it on.
|
||||
[ "$mode" = steam ] && [ "${BL_GAMESCOPE_FORCE_FULLSCREEN:-0}" = 1 ] && args+=(--force-windows-fullscreen)
|
||||
# HDR10: the app opened its compositor's colour-management gate for this session (BL_HDR=1);
|
||||
# gamescope then offers HDR to its clients through the same wp_color_manager_v1 it binds on ours.
|
||||
[ "${BL_HDR:-0}" = 1 ] && args+=(--hdr-enabled)
|
||||
@@ -445,7 +446,7 @@ case $mode in
|
||||
# the root window, which it watches. What gamescope was started with is where this begins.
|
||||
# Not on the desktop (BL_DESKTOP): no gamescope there, and the loop would outlive the client.
|
||||
[ -z "${BL_DESKTOP:-}" ] && (
|
||||
last=${BL_GAMESCOPE_FORCE_FULLSCREEN:-1}
|
||||
last=${BL_GAMESCOPE_FORCE_FULLSCREEN:-0}
|
||||
while :; do
|
||||
nap 1
|
||||
want=
|
||||
|
||||
Reference in new issue
Block a user