From d3588831a9e4a9629bd4328f5bd2f4e7973c9389 Mon Sep 17 00:00:00 2001 From: Utkarsh Dalal Date: Sun, 1 Nov 2026 20:03:41 +0530 Subject: [PATCH] Gamescope payload 20261101.3: Xwayland attaches a game's shared-memory segment through the sysvshm server Under gamescope, GL games on the xlib software winsys tore horizontally: Xwayland refused the game's MIT-SHM segment, Xlib fell back to XPutImage in 15 row bands per frame, and Xwayland committed between bands. Xwayland now fetches the segment's fd from the app's sysvshm server and attaches it (GameNative/xserver#2, on top of #1). Payload = 20261031.3 + bin/Xwayland; nothing else in the payload changes. --- app/src/main/java/app/gamenative/display/GamescopePayload.kt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/app/src/main/java/app/gamenative/display/GamescopePayload.kt b/app/src/main/java/app/gamenative/display/GamescopePayload.kt index 20cdc3babe..69d610070b 100644 --- a/app/src/main/java/app/gamenative/display/GamescopePayload.kt +++ b/app/src/main/java/app/gamenative/display/GamescopePayload.kt @@ -11,7 +11,7 @@ import java.io.File /** Versioned gamescope payload (gamescope, XWayland, scaling clients), fetched on the first gamescope launch. */ object GamescopePayload { - const val VERSION = "20261031.3" + const val VERSION = "20261101.3" const val ARCHIVE = "gamescope-gamenative-$VERSION.tzst" private const val STAMP = ".payload.version"