Input lag on Mac OS X builds
Hi everyone,
I'm on 2019.2.19f1. Just before I go digging any further down the rabbit hole I'll describe my situation - I have a very simple 2d side scroller that I'm building for release at the moment, and I've noticed that the mac os x native app build has much worse performance (on the same machine) than the web gl build running in a browser. My eyes are picking up maybe 20-50 ms of input lag, or perhaps the frame rate is low enough that clicks are taking some time to be rendered to the screen.
Another thing to mention - the performance is completely fine in the editor. It only becomes noticeably worse after building a standalone app.
Is this expected, or should I try to continue to diagnose the problem?
EDIT: I've confirmed with a couple of demo projects on different versions that this is a regression in 2019.x and doesn't occur in 2018 LTS. I've filed a bug report. It's a bit frustrating that the issue was marked as fixed here: https://issuetracker.unity3d.com/issues/increased-input-lag-slash-delay-in-standalone-build-when-having-low-frames-per-second-or-vsync-enabled
EDIT 2: This is still not fixed a year later in 2020.3.15f2 so potentially the person who replied saying it was fixed just lied and didn't test it, or it's regressed again.
Update - I've measured the framerate and it's a consistent 60fps both in the editor and build, it's just that the build has a consistent 50-100 ms of input lag.
I am also experiencing this on macOS builds only (the editor is fine). It seems to affect the mouse in particular, clicking has a noticeable delay. Turning off vSync seems to help a little, but the lag is still there.
Was this fixed? I still am seeing it in 2013.1.9f1 specifically for $$anonymous$$ac builds.
Answer by samanabo · Dec 04, 2020 at 01:01 AM
as far as I can see this is still an issue... I'm using 2019.4.14f1
Answer by nicbarkeragain · Dec 04, 2020 at 03:41 AM
I opened a bug on the Unity bug tracker and received this response:
Hi,
Thanks again for reporting this issue. It's now fixed in Unity 2020.1.0a24 and above.
I hope this solves your problem, please reach out to me if I can be of further help.
Thanks, Mantas Customer QA Team