It is a priority, the average regression typically takes years to fix from my experience @BRICKWORLD-MARK

If all Mac users are affected by this, why isn't it more of a priority? Most people trying to use Unity-based applications aren't Unity developers, so they're most likely just giving up on the applications they're trying to use or don't know to come here to vote. There is a Unity-based application that I desperately need for work, with deadlines approaching very quickly, and this issue hasn't been resolved in over a month.

Yeah it doesn't always seem to be related to SetCursor. It seems that low FPS can also cause the issue from what I can tell.

I don't seem to have a SetCursor in my code. Can this be caused by something else?

This problem started for me after upgrading to macOS 14.2.1, removing Cursor.SetCursor fixed it. Tested in 2022.3.10 and 2022.3.18.

All our apps worked well before the Sonoma update. Issue visible in Windowed mode, but depends on the resolution: not visible (or not perceptible) in low res like 768x640, but appears when the resolution increases. Not visible in the editor, at any resolution.

The same problem here

i have this issue too. it doesnt occur with all of my projects, and it doesnt occur on my colleagues's Mac (both our OSX are at Sonoma 14.2.1). I've tried changing all kinds of project/player settings to no effect. We don't use SetCursor. It happens with new and older builds of our application.

it looks to me like this has something to do with window focus. If i move the mouse outside the window for a drag gesture, things start to work while i'm somewhere outside. when i move back over the window, it breaks again.

I had this problem in my project as well and I identified the cause. The cause was calling Cursor.SetCursor within the Update function. Commenting out this line will fix it.

```
void Udpate()
{
Cursor.SetCursor(this.cursorTex, Vector2.zero, CursorMode.Auto);
}
```

I can solve this issue making the build with a high quality graphics settings