search

ValveSoftware / gamescope

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

invisible cursor #707

Open apprehensions opened 1 year ago

apprehensions commented 1 year ago

running a program or any game under gamescope with wayland makes the cursor work but also become invisible. i looked into the WLR_NO_HARDWARE_CURSORS variable i had set for the compositors cursor to work correctly but it did not help; the same issue appears on X, suprisingly - the cursor just does not appear.

gamescope -W 1920 -H 1080 -f -- wine is my launch command.

nothing interesting appeared in logs other than missing X net atoms:

xwm: Unhandled NET_WM_STATE property change: _NET_WM_STATE_ABOVE
xwm: Unhandled NET_WM_STATE property change: _NET_WM_STATE_MAXIMIZED_VERT
xwm: Unhandled NET_WM_STATE property change: _NET_WM_STATE_MAXIMIZED_HORZ
xwm: Unhandled client message: _NET_WM_FULLSCREEN_MONITORS
0168:fixme:thread:GetThreadUILanguage : stub, returning default language.
xwm: Unhandled NET_WM_STATE property change: _NET_WM_STATE_ABOVE
xwm: Unhandled NET_WM_STATE property change: _NET_WM_STATE_MAXIMIZED_VERT
xwm: Unhandled NET_WM_STATE property change: _NET_WM_STATE_MAXIMIZED_HORZ
xwm: Unhandled client message: _NET_WM_FULLSCREEN_MONITORS
info:  Presenter: Actual swap chain properties:
info:    Format:       VK_FORMAT_B8G8R8A8_UNORM
info:    Present mode: VK_PRESENT_MODE_IMMEDIATE_KHR
info:    Buffer size:  1912x1053
info:    Image count:  2
info:    Exclusive FS: 2
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Unsupported maximum keycode 708, clipping.
>                   X11 cannot support keycodes above 255.
Errors from xkbcomp are not fatal to the X server
yaomtc commented 1 year ago

May be related to #420

apprehensions commented 1 year ago

mouse works, just cant see cursor.

yaomtc commented 1 year ago

I can confirm this with Half-Life 2, but in Final Fantasy XIV the behavior is different. (This testing is with the overlay disabled.)

With just gamescope %command% or with -b the window does not show a cursor or respond to mouse or keyboard input at all. I can either end it with Stop, or if I try to close it Plasma sees gamescope is unresponsive and asks if I want to kill the process.

With gamescope -feb %command% the game launches and I can see the software cursor, but when I hover over any button, the game freezes up for a moment. If I move away from the button it freezes up momentarily again.

Sporknife commented 1 year ago

I am able to reproduce this by going into in and out of the ESC menu multiple times (where is shows Settings and Exit to desktop mode buttons).

Info: Operating System: Arch Linux KDE Plasma Version: 5.26.4 KDE Frameworks Version: 5.101.0 Qt Version: 5.15.7 Kernel Version: 6.1.1-zen1-1-zen (64-bit) Graphics Platform: Wayland Processors: 12 × Intel® Core™ i7-8700 CPU @ 3.20GHz Memory: 15,5 GiB of RAM Graphics Processor: AMD Radeon RX 480 Graphics Gamescope: master Proton: 7.0-5, Experimental (goes straight into invisible cursor mode).

kodatarule commented 1 year ago

I also seem to be running into this issue as well on an NVIDIA gpu, running endeavourOS. Basically either it shows an X(and on the latest GIT it even stays in the middle of the crosshair making it less pleasant to play as it moves left/right and center again) or no cursor at all, but the mouse itself works fine in-game. Note: This issue is present under both X and Wayland.

Operating System: EndeavourOS KDE Plasma Version: 5.26.4 KDE Frameworks Version: 5.101.0 Qt Version: 5.15.7 Kernel Version: 6.1.1-273-tkg-pds (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5800X3D 8-Core Processor Memory: 31,3 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 3070/PCIe/SSE2

ex1tium commented 1 year ago

I'm also having this problem.

RTX 3070. 525.85.05 drivers Nobara Linux 37 6.1.6-203.fsync.fc37.x86_64 KDE 5.26.5 /Wayland but it also happens on X11. In X11 cursor is corrupted or a dark a transparent box. Qt 5.15.8

This happens in Apex Legends. I haven't tested other games. Apex launch options gamescope -W 3440 -H 1440 -f gamemoderun %command% +fps_max 98. I also tried with --force-grab-cursor but it didn't work.

yaomtc commented 1 year ago

This no longer occurs for me in Final Fantasy XIV or Half-Life 2 on Arch. Gamescope works fine with the following launch command on both Plasma (X11) and Plasma (Wayland).

gamescope -f -w 2560 -h 1440 -b -e -- gamemoderun %command%