LizardByte / LizardByte/Sunshine
"Optimize mouse for remote desktop streaming" results in mouse spins in games
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 41.3k
- Forks
- 2.1k
- Avg merge
- 23h 47m
- Merged PRs (30d)
- 124
Description
### Is there an existing issue for this?
- [x] I have searched the existing issues
### Is your issue described in the documentation?
- [x] I have read the documentation
### Is your issue present in the latest beta/pre-release?
This issue is present in the latest pre-release
### Describe the Bug
I'm running https://github.com/Steam-Headless/docker-steam-headless with Moonlight to play EVE Online on my second monitor. Since I use it as a secondary display, I have `Optimize mouse for remote desktop streaming` enabled so the cursor can freely leave the Moonlight window.
The issue is that when dragging the mouse to rotate the camera, it frequently sends the camera into a wild spin, as if I just jeeted my mouse a few meters away.
### Expected Behavior
_No response_
### Additional Context
_No response_
### Host Operating System
Docker
### Operating System Version
Host: Linux, Client: Windows
### Architecture
amd64/x86_64
### Package
other (not listed)
### GPU Type
Intel
### GPU Model
Intel Arc B50 Pro
### GPU Driver/Mesa Version
Not sure
### Capture Method
None
### Apps
```json
```
### Log output
```shell
```
### Online logs
_No response_
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the mouse-spin behavior with "Optimize mouse for remote desktop streaming" enabled while streaming EVE Online through Moonlight from the listed Docker/Linux host to the Windows client. The payload names no source file or test, so trace the mouse-input handling from that setting and add a regression test or documented reproduction once the expected camera movement is established.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, docker
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100