Search Issue Tracker
Not Reproducible
Votes
0
Found in
2019.3.0a3
2019.3.0a11
2020.1.0a1
Issue ID
1174423
Regression
Yes
Performance issue when Exposed Properties of the ShaderGraph Material contains a CubeMap in Inspector
How to reproduce:
1. Delete the Library in the attached "BugReports2.zip" Project
2. Open the "Mat4ExposeBug" Scene
3. Click on "Cube" gameObject
4. Expand material dropdown.
5. Observe the stuttering
Expected Behaviour: No stuttering and UIR.ImmediateRenderer > GC.Alloc is not allocating constantly
Actual Behaviour: Editor stuttering and UIR.ImmediateRenderer > GC.Alloc is allocating over 100KB of data
Reproducible with: 2019.3.0a12, 2020.1.0a1
Not reproducible with: 2019.2.1f1
Note: Was not able to test on 2018.4 due to the Package errors.
Comments (2)
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 Game view and Scene view fail to render when launching the Editor with a maximized Render Graph Viewer window
- "List is empty" is poorly visible in the "Create Node" window
- [Android] GameObject with a custom shader becomes invisible when deployed with the Vulkan Graphics API
- “ReferenceError: Pointer_stringify is not defined” error is thrown when downloading a file
- GameObjects are not rendered when using a fragment shader with RWStructuredBuffer in URP
huulong
Jun 26, 2021 18:12
My explanation on the forum may not fit this case because it's about Physics component Info section. But maybe the Material section also shows the same type of read-only fields related other objects, also causing repeated Inspector.Repaint?
Hannibal_Leo
May 09, 2020 14:38
Seems like we have the same issue.
https://forum.unity.com/threads/inspector-causes-extreme-lag-in-play-mode.885520/