-
Notifications
You must be signed in to change notification settings - Fork 90
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hardware Cursor isn't visible in games (possible XWayland issue) #434
Comments
On my end, it is visible, but the cursor is visually stuck in place in fullscreen (and borderless window) games, but things can be interacted with with an invisible cursor. |
That's my whole point. The real cursor isn't rendered, most likely due to the new protocol that has been implemented inside cosmic-comp. The thing about "using software cursor" isn't even something that you can decide in 90% of games, plus hardware cursor is simply superior in everything so it even makes sense. |
While testing this, I discovered that the cursor can be temporarily fixed after launching a fullscreen game by pressing Super + M (which creates the letterboxing mentioned in a separate issue), but shortly afterwards the game freezes (similar to the cursor being stuck), though everything else works (e.g. the game moves diagonally when pressing Super, and allows for other things to be interacted with), and this message is emitted in the logs: |
#603 should now also fix the invisible cursor (though most games still break after minimize). |
Can confirm that it fixes the cursor! |
#603 got merged. |
Since, I think, #380 when playing games the cursor (if it's not a software one) doesn't get rendered anymore, making it extremely difficult to navigate menus (in most games it's impossible).
I think #424 fixes this based on pure intuition, but I'm not sure.
I'm using a laptop, nvidia+intel GPU, graphics set in hybrid mode.
The text was updated successfully, but these errors were encountered: