LizardByte / LizardByte/Sunshine

macOS mouse on wrong monitor

Open
#5,733 0 comments 2 reactions 1 assignee View on GitHub

@ReenigneArcher is already working on this.

Since Sep 16, 2026.

input:mouse
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

Filing for @andygrundman

A ton of Mac code got removed in https://github.com/LizardByte/Sunshine/commit/687e12d013a838e1769ffdf996eb1d5ef8402660 in `src/platform/macos/input.cpp` and I guess it now lives in libvirtualhid. The issue I'm running into is that now there is no logging code for mouse events. Not sure if it's always been broken but the mouse doesn't play nice with additional displays. It looks like this lost the code that knows which display is being streamed or something, and I have no idea how that info is supposed to be handled now. I think this is the old code that worked it out, although looking at the output_name config won't work with SCK. https://github.com/LizardByte/Sunshine/blob/cf52f4b6f33cc9d143f0f6bb67c9891fe3563e54/src/platform/macos/input.cpp#L687-L707

### Expected Behavior

- Add debug logging
- Fix mouse input when using multiple displays

### Additional Context

_No response_

### Host Operating System

macOS

### Operating System Version

27

### Architecture

arm64/aarch64

### Package

macOS - dmg

### GPU Type

n/a

### GPU Model

-

### GPU Driver/Mesa Version

-

### Capture Method

AVCaptureScreen (macOS)

### Apps

```json

```

### Log output

```shell

```

### Online logs

_No response_

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.