Search Issue Tracker
Duplicate
Votes
0
Found in
2020.2.0b1
2021.1.0a1
Issue ID
1281247
Regression
Yes
Performance is heavily impacted when displaying a Shader in the Inspector
How to reproduce:
1. Open the attached project
2. Open the Profiler Window (Window->Analysis->Profiler)
3. Switch the Profiler's mode to "Editor"
4. In the Project Window, select the Material Asset
5. Observe the Profiler
6. In the Inspector with the Material selected, click the 3 dots and "Select Shader"
Expected result: Performance is not heavily impacted when displaying the Shader in the Inspector
Actual result: Performance is heavily impacted when displaying the Shader in the Inspector
Reproducible with: 2021.1.0a1
Not reproducible with: 2018.4.27f1, 2019.4.11f1, 2020.1.7f1, 2020.2.0b5
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
- 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
This is a duplicate of issue #1283558