Skip to content
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

Closed
gabriele2000 opened this issue Apr 19, 2024 · 6 comments
Closed

Comments

@gabriele2000
Copy link

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.

@git-f0x
Copy link
Contributor

git-f0x commented Apr 19, 2024

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.
Though I'm likely using software cursors, since the icon is changed (but it switches back and forth when scrolling).

@gabriele2000
Copy link
Author

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 cursor that you see is the "last frame" that is likely inside a buffer, or something like that.

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.

@git-f0x
Copy link
Contributor

git-f0x commented Jul 6, 2024

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:
[GL] GL_INVALID_VALUE in glTexSubImage2D(xoffset 0 + width 24 > 10)
Not sure if it's helpful, but just in case.

@Drakulix
Copy link
Member

Drakulix commented Jul 8, 2024

#603 should now also fix the invisible cursor (though most games still break after minimize).

@git-f0x
Copy link
Contributor

git-f0x commented Jul 8, 2024

Can confirm that it fixes the cursor!
Unrelated to the PR, other things on the same workspace as the game can't be interacted with.
E.g. if opening workspaces with a fullscreen game running, clicking on a different app in the overview just switches to displaying a frozen (running in background) game fullscreen, that starts moving after some clicks. Though that's probably related to not being able to view other apps or the App Library over a fullscreen window.

@Drakulix Drakulix mentioned this issue Jul 8, 2024
@Drakulix
Copy link
Member

#603 got merged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants