Search Issue Tracker
Fixed in 2020.2
Fixed in 2019.4, 2020.1
Votes
1
Found in
2019.4.0f1
2020.1
Issue ID
1251652
Regression
No
Input lag in large scene
There seems to be some input lag that accumulate over time when the application ticking is taking to much time.
Steps:
1. Download BoatAttack demo
2. Open scene PerfTestsBoatAttack.unity
3. Use fly cam to move around for 5-10 seconds
4. Release keyboard and mouse inputs
Result: The fly camera continues for many seconds after inputs have been released
Expected: The fly cam should stop as soon as possible.
-
simonrocheman
Jul 01, 2020 07:50
I would also be very happy if this bug could be solved on Unity2019 !
-
TheGamery
Jun 25, 2020 13:15
Hopefully a fix comes to 2019 LTS soon because it has crippled my project.
-
idototes
Jun 12, 2020 21:58
Fyi- This is happening also in 2019.3.11 and 2019.3.15 as far as we checked. We rolled our installations back to 2019.3.7 and the problem is gone, so it might give some scope. Waiting for the upcoming 2019.4 fix and we will likely upgrade to LTS in any case.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Shader error db grows on each build
- Android ARCore build fails with 2019.4 due to outdated Gradle
- [tvOS] Visual artifacts are present when Ambient Occlusion is enabled and Dynamic Resolution is reduced
- Texture Importer Inspector throws errors when a built-in texture inspector is overwritten in C#
- Invalid AABB error is thrown when moving a Particle with Velocity over Lifetime and Limit Velocity over Lifetime modules
Resolution Note (fix version 2020.2):
Fixed in 2020.2.0a15
Resolution Note (fix version 2020.1):
Fixed in 2020.1.0b13
Resolution Note (fix version 2019.4):
Fixed in 2019.4.3f1