You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I investigated Grim Dawn (219990), and it regresses between 3.13.19 and 3.14.1 in the jupiter-main repo which I then bisected between on my OLED Deck.
After the bisected bad commit, the mouse in the menu of Grim Dawn goes from always showing when using the default layout and moving the mouse with the right touchpad to rarely showing under the same conditions. it does show properly until the 3000ms timeout if you touch the screen directly or if you invoke the cursor by holding the Steam button and using the touchpad.__
EDIT: the bad behavior continues on desktop when using both gamescope -f -- %command% and gamescope -f --force-grab-cursor -- %command% on SteamOS 3.6.19
Steps To Reproduce
Launch Grim Dawn
Once in the main menu, attempt to use the right touchpad to move the cursor The mouse will remain invisible while still interacting with the menu
Hold the Steam button and move the mouse The mouse will appear, but only for 3000ms as set in gamescope-session
Was able to narrow down the issue quite a bit, major difference seems to be in how "Mouse Region" Steam Input events (or "Cursor", which is Grim Dawn's default right trackpad UI binding) get treated for presentation by gamescope with a visible cursor vs how "As Mouse" Steam Input events get treated for presentation.
Mouse Region events went from always showing a visible cursor in a similar manor to "As Mouse" to only showing a visible cursor for the 3000ms timeout set in /usr/bin/gamescope-session despite continued interaction.
A workaround for this is binding right pad touch to "Mouse > Move Cursor by amount > 1 in X or Y", then go to settings and enable "hold to repeat (turbo)".
These "move by amount" events force the cursor to always be shown.
Is there an existing issue for this?
Are you using any gamescope patches or a forked version of gamescope?
Current Behavior
Bisected to: d7758a8
Original report: ValveSoftware/SteamOS#1681
I investigated Grim Dawn (219990), and it regresses between 3.13.19 and 3.14.1 in the
jupiter-main
repo which I then bisected between on my OLED Deck.After the bisected bad commit, the mouse in the menu of Grim Dawn goes from always showing when using the default layout and moving the mouse with the right touchpad to rarely showing under the same conditions. it does show properly until the 3000ms timeout if you touch the screen directly or if you invoke the cursor by holding the Steam button and using the touchpad.__
EDIT: the bad behavior continues on desktop when using both
gamescope -f -- %command%
andgamescope -f --force-grab-cursor -- %command%
on SteamOS 3.6.19Steps To Reproduce
The mouse will remain invisible while still interacting with the menu
The mouse will appear, but only for 3000ms as set in gamescope-session
Hardware information
Software information
Which gamescope backends have the issue you are reporting?
Logging, screenshots, or anything else
running gamescope with wlserver debug logging shows a ton of the same sequence of events whenever the cursor is moved
The text was updated successfully, but these errors were encountered: