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

Input

-

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

Comments (5)

  1. 711701a5d4a840d0d4a7bad97a722d6a?d=mm

    Astrobinary

    Jan 07, 2021 16:15

    I am experiencing this issue for Unity 2020.1.13, using the new input system.

  2. 1c6b8cdf25dbc9aba51db8e35f5a9559?d=mm

    laurentlavigne

    Dec 03, 2020 23:32

    also happens in 2020.1.13 using a MM720 @ 250Hz

  3. Ec29525366a1d6ef83d41824da510cee?d=mm

    TeodorVecerdi

    Sep 04, 2020 13:23

    This still happens in Unity 2019.4.9f1. Using 1000hz polling makes the editor unusable

  4. 61a9bb15c39de5bce47ba44b38891587?d=mm

    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 :(

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.