ValveSoftware / gamescope

SteamOS session compositing window manager
Other
3.17k stars 213 forks source link

Unable to run games from Steam using Gamescope #1461

Open unrealapex opened 3 months ago

unrealapex commented 3 months ago

When I try launching Steam games using Gamescope, they crash after a few seconds. I am using gamescope -- %command% in my launch options. I've tried forcing Steam to run using Gamescope, but games still crash. I am experiencing this issue with Gamescope 3.14.22 on Xorg. I compiled Gamescope from Gentoo's package repository.

log file
console: gamescope version undefined
vulkan: selecting physical device 'Intel(R) HD Graphics 620 (KBL GT2)': queue family 0 (general queue family 0)
vulkan: physical device supports DRM format modifiers
wlserver: [backend/headless/backend.c:67] Creating headless backend
vulkan: supported DRM formats for sampling usage:
vulkan:   AR24 (0x34325241)
vulkan:   XR24 (0x34325258)
vulkan:   AB24 (0x34324241)
vulkan:   XB24 (0x34324258)
vulkan:   RG16 (0x36314752)
vulkan:   NV12 (0x3231564E)
vulkan:   AB4H (0x48344241)
vulkan:   XB4H (0x48344258)
vulkan:   AB48 (0x38344241)
vulkan:   XB48 (0x38344258)
vulkan:   AB30 (0x30334241)
vulkan:   XB30 (0x30334258)
vulkan:   AR30 (0x30335241)
vulkan:   XR30 (0x30335258)
vulkan: Creating Gamescope nested swapchain with format 44 and colorspace 0
wlserver: Using explicit sync when available
wlserver: Running compositor on wayland display 'gamescope-0'
wlserver: [backend/headless/backend.c:17] Starting headless backend
wlserver: Gamescope built without libei, XTEST will not be available!
wlserver: [xwayland/server.c:107] Starting Xwayland on :1
wlserver: [types/wlr_compositor.c:771] New wlr_surface 0x556aa95a5bf0 (res 0x556aa95a0350)
wlserver: [xwayland/server.c:272] Xserver is ready
vblank: Using timerfd.
vulkan: Creating Gamescope nested swapchain with format 44 and colorspace 0
wine: using kernel write watches, use_kernel_writewatch 1.
fsync: up and running.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
ATTENTION: default value of option vk_khr_present_wait overridden by environment.
ATTENTION: default value of option vk_xwayland_wait_ready overridden by environment.
ATTENTION: default value of option vk_xwayland_wait_ready overridden by environment.
ATTENTION: default value of option vk_khr_present_wait overridden by environment.
ATTENTION: default value of option vk_xwayland_wait_ready overridden by environment.
ATTENTION: default value of option vk_khr_present_wait overridden by environment.
ATTENTION: default value of option vk_xwayland_wait_ready overridden by environment.
ATTENTION: default value of option vk_xwayland_wait_ready overridden by environment.
ATTENTION: default value of option vk_khr_present_wait overridden by environment.
ATTENTION: default value of option vk_xwayland_wait_ready overridden by environment.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
Setting breakpad minidump AppID = 2280
Steam_SetMinidumpSteamID:  Caching Steam ID:  76561199024467448 [API loaded no]
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
ATTENTION: default value of option vk_khr_present_wait overridden by environment.
ATTENTION: default value of option vk_xwayland_wait_ready overridden by environment.
ATTENTION: default value of option vk_xwayland_wait_ready overridden by environment.
ATTENTION: default value of option vk_khr_present_wait overridden by environment.
ATTENTION: default value of option vk_xwayland_wait_ready overridden by environment.
[Gamescope WSI] Forcing on VK_EXT_swapchain_maintenance1.
Fossilize INFO: Overriding serialization path: "/home/aaron/.local/share/Steam/steamapps/shadercache/2280/fozpipelinesv6/steamapprun_pipeline_cache".
wine: setpriority 6 for pid -1 failed: 3
wine: setpriority -19 for pid -1 failed: 3
wlserver: [types/wlr_compositor.c:771] New wlr_surface 0x556aa9570370 (res 0x556aa95a3190)
xwm: got the same buffer committed twice, ignoring.
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Unsupported maximum keycode 708, clipping.
>                   X11 cannot support keycodes above 255.
> Warning:          Could not resolve keysym XF86KbdInputAssistPrevgrou
> Warning:          Could not resolve keysym XF86KbdInputAssistNextgrou
Errors from xkbcomp are not fatal to the X server
[Gamescope WSI] Creating Gamescope surface: xid: 0x1200032
[Gamescope WSI] Atom of T was wrong type. Expected XCB_ATOM_CARDINAL.
wlserver: [types/wlr_compositor.c:771] New wlr_surface 0x556aa9572580 (res 0x556aa95a2050)
wine: using kernel write watches, use_kernel_writewatch 1.
gamescope: children shut down!
terminate called without an active exception
(EE) failed to read Wayland events: Broken pipe
  
Encoded14 commented 3 months ago

Same issue here. Using Steam from flatpak and gamescope from voidlinux repos. CS2 launches fine without gamescope and I dont get any errors when launches vkcube or supertuxkart with gamescope from terminal. EDIT: I use hyprland but also had the same problem with gnome on both wayland and x11

Gibitwit commented 3 months ago

Maybe the same problem as my issue. https://github.com/ValveSoftware/gamescope/issues/1380

@unrealapex Why are you doing this, gamescope -- %command%? Try setting some parameters for Gamescope.

unrealapex commented 3 months ago

The my bug is not related to mouse movement. Games crash regardless of arguments given to Gamescope.

Eoin-ONeill-Yokai commented 1 month ago

I'm having this issue with CS2 as well on sway / hyprland compositors.

Other games work, but CS2 in particular seems to be bugged and will not properly contain the executed game. Any way that I can debug the cause of this through the terminal?