Search Issue Tracker
Fixed in 2017.4.0
Fixed in 2017.4.X, 2018.4.X, 2019.1.X, 2019.2.X
Votes
39
Found in
2017.4.0f1
2018.3.0a1
2018.3.0f1
2019.1.0a1
2019.2.0a1
Issue ID
1117360
Regression
No
[Windows] High Input Polling rates can impact Editor performance
Steps to reproduce:
1. Download and open the attached project
2. Move the mouse inside the scene view
Expected result: little to no performance loss
Actual result: editor performance becomes impossible to work with
Reproduced on 2017.4.0f1, 2017.4.18f1, 2018.3.2f1, 2019.1.0a14, 2019.2.0a1
Fixed in: 2017.4.28f1, 2018.4.1f1, 2019.1.1f1, 2019.2.0a14, 2019.3.0a1
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
- The Scene\Game view is grey when two "Universal Additional Camera Data" scripts are attached to the camera
- NullReferenceException error thrown when changing Scenes in Play Mode
- Crash on "'anonymous namespace'::ConvertFBXShapes" when importing an FBX file
- Crash on Transform::RemoveFromParent when Object.DestroyImmediate() is called on Transform
- [Linux] Player consumes more CPU resources when it is running in the background
Softsign
Jan 25, 2023 10:34
Still happening for 2020.3.33f1
cwbeta
Jun 28, 2022 08:16
Also reproducible with Unity 2021.3.5f1 with Logitech GPW2.
Glader
Dec 13, 2021 03:27
Still happening for 2020.3.24f1
Astrobinary
Jan 07, 2021 16:15
I am experiencing this issue for Unity 2020.1.13, using the new input system.
laurentlavigne
Dec 03, 2020 23:32
also happens in 2020.1.13 using a MM720 @ 250Hz
TeodorVecerdi
Sep 04, 2020 13:23
This still happens in Unity 2019.4.9f1. Using 1000hz polling makes the editor unusable
Kinami37
Mar 10, 2019 22:48
Can this please get fixed finally...
2017 LTS doesnt have this issue for me, but im stuck on 2018.3 now, every patch my hopes die more :(
Peter77
Jan 18, 2019 11:45
Related forum thread:
https://forum.unity.com/threads/unity-stutters-and-hitches-even-in-empty-scenes-unreal-does-not.609808/