Search Issue Tracker
Fixed in 2019.1.X
Votes
0
Found in
2018.3.0b7
2018.3.0b9
2019.1.0a1
Issue ID
1099071
Regression
Yes
The MaterialEditor inspector becomes increasingly laggy the more managed types you have
How to reproduce:
1. Download and open user's attached project "UnityMaterialEditorBug.zip"
2. Select the "Editing Values Extremely Laggy" material, and try editing any value there(notice that the value changes with a slight/medium lag)
3. Delete the "LotsOfTypes.cs" script which contains 100 000 empty regular c# classes and notice how this problem goes away
Expected result: The amount of managed types in the script doesn't have any impact on the MaterialEditor inspector's performance
Actual result: The MaterialEditor inspector becomes increasingly laggy the more managed types you have
Reproducible with: 2018.3.0f1, 2018.3.5f1, 2019.1.0a11
Not reproducible: 2017.4.17f1, 2018.1.9f2, 2018.2.19f1, 2019.1.0b3
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment