Search Issue Tracker
Not Reproducible
Fixed in 2021.2.X
Votes
29
Found in
2021.2
2021.2.0b17
2021.2.1f1
2022.1
Issue ID
1376273
Regression
Yes
[Mac] Performance regression in Editor UI
Reproduction steps:
1. Open new Unity project
2. Hover over different objects in Hierarchy as well as non-focused Editor tabs
3. Enter text into any Editor text field (Hierarchy Search, Inspector Fields, etc.)
4. Move any GameObject by selecting and dragging its Transform Component's values in the Inspector window
Expected result: There is no delay in the Editor's UI
Actual result: There is a delay for hovering on objects in Hierarchy and non-focused Editor tabs, entering text, and moving objects through their Transform Component
Reproducible with: 2021.2.0b17, 2021.2.1f1, 2022.1.0a13
Not reproducible with: 2019.4.32f1, 2020.3.22f1, 2021.1.28f1, 2021.2.0b16
-
thomas642daniel
Jul 17, 2024 08:41
this is very much reproducible, it's not necessarily about moving a transform of an object but, more about general text input and interaction with the editor's inspector, assets, and hierarchy views.
-
snoopywlk
Jul 20, 2023 03:34
I encountered this issue in version 2021.1.28.
-
Alejandro-Martinez-Chacin
Mar 30, 2022 14:16
I'm on 2021.2.17f1 and can totally see some serious regression after being yesterday on 2021.1.28f1...
I can drag a gameobject on the scene inspector to reparent it to another and wait there for seconds... even sometimes if the mouse is standing still it won't trigger any sort of action update, the UI stays there doing none of the reparenting until the mouse is flicked (which could also make the gameobject end somewhere else).Would a video of this help? How can I share it? Should I create a thread and put the things there?
-
samanabo
Nov 14, 2021 00:05
Also confirming that this is fixed in 2021.2.2f1
-
pauldrummond
Nov 11, 2021 18:22
Updated my project from 2021.2.1 to 2021.2.2 and the worst UI delays seem to have gone. Selecting hierarchy items is no longer slow and inspector fields now update as expected.
-
sakamoto-kun
Nov 11, 2021 17:15
This issue appears to be resolved in 2021.2.2f1.
-
samanabo
Nov 11, 2021 02:27
Just wanted to link to this other issue which is maybe possibly the same problem:
2021.2.2f1 is not released yet, but I'll re-test this once it is.
-
TV4Fun
Nov 10, 2021 19:07
Very much reproducible. Duplicate of existing issue listed on 2021.2.0 that is supposedly going to be fixed in 2021.2.2, but is still very active and do you have any Mac developers on your team at all?
-
CMHatch
Nov 09, 2021 19:04
This is very much reproducible, it's not necessarily about moving a transform of an object but, more about general text input and interaction with the editor's inspector, assets, and hierarchy views.
Overall interaction with the editor's fields are delayed by up to 2 seconds or don't update at all until there is another user interaction.
Unity Version: 2021.2.1f1 (Apple Silicone)
macOS: 12.01
Computer: MacBook Pro (2021) m1 max, 32GB RAM -
samanabo
Nov 09, 2021 13:16
Very disappointed to see this marked as not reproducible. I am easily able to reproduce the problem in the versions of Unity listed on the ticket.
What should I do to fix the problem on my side? Is there a new version of Unity that no longer has this problem? Is there a forum post that addresses this?
As of now, looking at Unity 2021.2.1f1 the issue still exists and makes the editor unusable on macOS.
Whenever I attempt to type a number info a field in the inspector the editor appears to not update until another key is pressed, or something is clicked. This causes the last digit to not display until another interaction happens.
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note:
No longer reproduces in 2022.1.0a14
Resolution Note (fix version 2021.2):
No longer reproduces in 2021.2.2f1