Mouse Glitching During Remote Play

[robloxgamer192]

Issue:

Mouse tends to jump around, sometimes going to a specific area whenever trying to interact with the game. Many times, when I try to aim in games like Rust, or GTA V, it will automatically snap to a spot and I would have to re-aim a few times for it to stop snapping. This snapping will go to the same exact spot and can be very frustrating, especially in games like Rust. I've had moments where I'm trying to raid a base and I throw the C4 on the ground after doing a full 180 spin in a split second.

I've tried to troubleshoot by swapping mouses on the remote client and turning off my mouse on the host, but that wasn't successful. Is there something I'm missing? Started having this issue a few weeks ago, before that, everything worked fairly smoothly.

Thanks!

[orthorix]

Same here. Currently lying in bed, caught a cold.
In the cellar my Win11 PC runs Satisfactory (4k resolution, reduced to 1440 x 900 now).
In my bedroom my old MacBook Pro (2880 x 1800) serves as game client.

The mouse pointer (view direction in game) sometimes behaves weird when running in 4k, windowed fullscreen. Trying to fix this downstairs I realized the task bar was open and the game not fullscreen but windowed: the mouse has moved outside the boundaries.

I reduced the resolution to a more client friendly 1440 x 800, fullscreen not windowed. Now the mouse pointer problem is resolved.

Whenever I do a mouse click though, 4k or reduced resolution, the mouse behaves like it has been clicked in another position. Especially in menus. In view mode sometimes while building something.
Dragging the mouse to all 4 borders of the screen seems to resolve the problem temporally - until the next click.

Last time I played remote was 2 weeks ago, game 4k fullscreen windowed, Mac native resolution. Needless to say I've never had these problems then and before…

[76561199434770914]

Duplicate of https://steamcommunity.com/groups/homestream/discussions/1/3821906444729683968/
?

[TheOrangeBox]

Still issue persisting on May 21

[orthorix]

Issue still persisting on June 4… *rolleyes* @devs: anyone listening?