Search Issue Tracker

In Progress

Fix In Review for 2021.3.36f1, 2024.1.X

Fixed in 2022.3.20f1, 2023.2.11f1, 2023.3.0b5

Votes

51

Found in

2021.3.33f1

2022.3.16f1

2023.2.4f1

2023.3.0a19

2024.1.0a1

Issue ID

UUM-59176

Regression

No

Mouse and keyboard button inputs are delayed when in the Player on macOS

--

-

Reproduction steps:
1. Open the attached "PROJECTFILE" project
2. Build And Run the project (File > Build And Run)
3. Quickly spam the “ASDHJKL” keyboard keys in the Player for about 5 seconds
4. Stop clicking the keyboard keys
5. Observe the “EVENTS” key inputs in the Player

Expected result: Key inputs stop appearing
Actual result: Key inputs are delayed and continue to appear

Reproducible with: 2021.3.33f1, 2022.3.16f1, 2023.2.4f1, 2023.3.0a19

Reproducible on: macOS Sonoma 14.2 (M1 Max)
Not reproducible on: Windows 10

Note: Issue is not reproducible in the Editor Play mode

Comments (15)

  1. AcidArrow

    Feb 06, 2024 13:35

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

  2. brickworld-mark

    Jan 29, 2024 20:16

    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.

  3. unity_g9JYfRP-dPrU8Q

    Jan 29, 2024 17:51

    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.

  4. btschumy

    Jan 24, 2024 17:15

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

  5. ulrikdamm

    Jan 22, 2024 13:10

    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.

  6. tolosaoldfan

    Jan 16, 2024 10:43

    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.

  7. bakno

    Jan 13, 2024 15:38

    The same problem here

  8. dfischer23

    Jan 10, 2024 12:05

    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.

  9. SenaJP

    Jan 10, 2024 06:15

    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);
    }
    ```

  10. nesplora

    Dec 29, 2023 07:51

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

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.