For what it's worth, I've heard of this scenario a while back with an old version of WoW.
I've encountered the same issue in at least 2 other games, both via Proton/Steam Play. In Deus Ex Human Revolution: Directors Cut the mouse disappears when clicking with emulated mouse click on Steam Controller, and in F.E.A.R. 2 the mouse will appear on emulated mouse clicks. The mouse can be restored by simply entering/exiting a menu that resets the visibility of the cursor e.g. the games map or the pause menu. In the case of Deus Ex, the mouse is technically still functioning as moving it highlights clickable UI.
I'm not sure if it's related, but I've seen similar issues previously using the Steam Controller under Wayland, where the mouse cursor does not appear to move but things like the UI will still highlight as if the mouse is passing over them. Aiming in e.g. CS:GO still functions, only the visible mouse cursor does not move.
Is Steam mouse input being X11/XWayland only related to this bug or should I file a new report?
Here in the video when I use a controller to move the mouse, only apps running on XWayland respond to it while the cursor does not move at all. https://www.youtube.com/watch?v=QFcM7Wu0YqU
@kisak-valve This hasn't been an issue for a while. Can be closed.
Your system information
Please describe your issue in as much detail as possible:
When clicking with a Steam Controller's emulated mouse the cursor disappears. You can make it reappear if you bring up the Steam Overlay. This happens regardless of if it was launched in BPM or not. Use of a normal mouse does not cause this. Originally I thought this was a Proton issue until I launched the game via a shortcut which was running a Humble copy of the game via CrossOver. I then further confirmed that this was related to the Steam software that handles the emulation by using sc-controller instead. Even when the game is launched via the Steam client using Steam Play, this undesirable behavior doesn't occur so long as either a real mouse is used or the Steam Controller is used with sc-controller.
For reference sake: https://github.com/ValveSoftware/Proton/issues/602
System: https://gist.github.com/nstgc/02457d7920931a3f8d69cc7b9fa41a2c
log: https://gist.github.com/nstgc/c66286af3f530c9c2bd61b886fcfad35
As far as I can tell, this is the only game for which this is an issue.
Steps for reproducing this issue: