Invisible Mouse cursor in remote play

[CapnSwole]

Any game I play via remote play that has a mouse cursor, ie factory games like Dyson Sphere program, Foundry, I can see the mouse movement and where the cursor should be but the cursor is invisible.

On my Windows 11 host pc that has a physical mouse connected, I can see the cursor moving on the screen as I move it on the deck using the joystick or trackpad but it’s just invisible on the deck.

I do not believe it to be a hardware issue as when using sunshine/moonlight, I can see the mouse cursor just fine. This is only happening when using Steams built in remote play.

I reached out to support and they said to post here…

[Chis]

This. The mouse cursor is invisible whenever I remote play a game through Steam Deck game mode.

[SkillsThatKill]

Same here. No mouse pointer visible in game mode. It does work fine on desktop mode though. This has been going on for a few updates now. Can anyone help?

[pingo]

same problem for months

[The Dayman aAa]

Still happening for me

[EricLuiz]

Same here. Other threads related to the issue:

https://steamcommunity.com/app/1675200/discussions/1/4352247707587895132/
https://steamcommunity.com/app/1675200/discussions/1/4695658272798129026/
https://steamcommunity.com/app/353370/discussions/1/7074686732306760822/

[Revmatek]

This should be fixed in the beta branch now:
https://steamcommunity.com/app/1675200/eventcomments/595142635297973590

I noticed this mouse visibility issue while working on Steam Deck support for my game Nautikin Adventures. I don't know why it was not fixed for 8 months. I opened a ticket for this and made it clear what the issues where based on the existing information I was able to find on Steam Discussions and the issues I observed with my game while using remote play / streaming.

This was caused by regression in gamescope:
https://github.com/ValveSoftware/gamescope/commit/cc15bf613d39ee8793829d640813c7898dcc8a47

I will see if I can get Value to add a test case or something so that this does not occur again. I spent many hours researching this problem and was up til midnight talking back and forth with Steam conveying the issue. I am very glad it is fixed and seems to be fixing other similar reports.