Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2019.2.X, 2019.3.X
Votes
14
Found in
2018.3.0b7
Issue ID
1094991
Regression
Yes
Editor is lagging when modifying material properties
How to reproduce:
1. Open attached "ForgottenPlayhouse" project
2. Select "cardboardwall1" material under Assets/Materials/Cardboard/CardboardWall1
3. In Inspector change color of the material
Expected result: Color(or any other property) is changed instantly and Editor does not lag
Actual result: Editor is lagging after every property change
Reproduced with: 2018.3.0b7, 2019.1.0a10
Does not reproduce with: 2018.3.0b6 (performance is only barely slower), 2018.2.17f1 and lower (performance is as expected)
Notes: Changing the Shader from HDRP to any other still reproduces the issue.
Comments (7)
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
- Uninitialized variable warning appears in the Inspector of a custom shader when the variable is initialized
- "Failed creating toolbar element from ID..." error is thrown when resetting the Scene view Overlay layout while an Asset Transformer Toolbox overlay is active
- Entity ID for Font Assets is serialized twice which throws an error when using Debug Inspector
- Play Mode can be entered when disabling Adaptive Performance and pressing either the Play Mode button or the keyboard shortcut to enter Play Mode before recompilation leading to errors and warnings thrown
- Parent ListView element also becomes selected when inner ListView element is selected
Peter77
Sep 05, 2019 16:28
Related forum post:
https://forum.unity.com/threads/case-1094991-bump-custom-shader-gui-makes-scene-editing-impossible.738944/
julian-moschuering
Sep 03, 2019 09:50
Or just cache it. I hacked around this by skipping CreateCustomShaderEditor and replacing it with a cached one.
JohnPontoco
Jun 21, 2019 16:28
The cause of this bug is that the ShaderGUIUtility.ExtractCustomEditorType() function is looping through all types in the loaded assemblies, even though it's only looking for a specific type name.
Fix: Swap this loop with Assembly.GetType() which is O(1) for a given type name.