Search Issue Tracker
Fixed in 2022.2.X
Fixed in 2019.4.X, 2020.3.X, 2021.2.X, 2022.1.X
Votes
0
Found in
2019.4
2020.3
2021.2
2022.1
Issue ID
1378555
Regression
No
Editor performance is slow when "Skip unused shader_features" is selected in the Shader variant dropdown
How to reproduce:
1. Open the attached "case_1378555" project
2. Select the "Packages -> glTFast -> Runtime -> Shader -> glTF-metallic-Premultiply-double" Shader
3. Select the little dropdown next to the "Compile and show code" button in the Inspector
4. Observe the Editor performance
Expected result: No Editor performance issues
Actual result: The Editor performance goes to 0, progress/wait dialogue pops up every few seconds. The Editor doesn't respond
Reproducible with: 2021.2.0a17, 2021.2.3f1, 2022.1.0a12
Not reproducible with: 2020.3.23f1, 2021.1.28f1, 2021.2.0a3
Couldn't test with: 2019.4.32f1 (downgrading user's script errors), 2021.2.0a4 - 2021.2.0a16, 2022.1.0a12 - 2022.1.0a15 (the little dropdown doesn't display anything when clicked)
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
- Redoing creation of Sub Scenes and Cube GameObjects in Hierarchy throws “Assertion failed on expression: 'targetScene != nullptr’” error in Console window
- Selecting “New Sub Scene” after assigning “New Scene” in Sub Scene Script Component throws “Destroying GameObjects immediately is not permitted” in the Console window
- Shader Graph "Zoom Step Size" can be set to 0 even though the zoom still works
- Enabling/Disabling the Deprecated Nodes doesn't apply to the opened Shader Graph unless any Variable is added to the Blackboard
- Group Selection title text size is smaller in renaming than the actual font size
Resolution Note (fix version 2022.2):
Fixed in 2022.2.0a1
Resolution Note (fix version 2022.1):
Fixed in 2022.1.0b3
Resolution Note (fix version 2021.2):
Fixed in 2021.2.8f1
Resolution Note (fix version 2020.3):
Fixed in 2020.3.26f1
Resolution Note (fix version 2019.4):
Fixed in 2019.4.35f1