Search Issue Tracker
Fixed in 2022.3.52f1
Fixed in 2022.3.X, 6000.0.X, 6000.1.0a2, 7000.0.0a7
Votes
0
Found in
2021.3.32f1
2022.3.13f1
2023.1.20f1
2023.2.0f1
2023.3.0a14
6000.0.0b11
6000.1.0a1
Issue ID
UUM-55971
Regression
No
The Inspector of a Shader Asset does not show the correct number of vertex and fragment shader variants when using "multi_compile_fragment" directive
How to reproduce:
1. Open the “MultiCompileFragmentVariants” project
2. Select the “UnlitMultiCompileFragmentMultiLines” shader in Project
3. In the Inspector select “Compile and show code” then observe the lines of code
4. Select the arrow next to the “Compile and show code” button
5. Observe the Inspector
Expected result: The Inspector shows that it generates more than one vertex shader variant and more than one fragment shader variant
Actual result: The Inspector does not show that it generates more than one vertex shader variant and more than one fragment shader variant
Reproduced with: 2021.3.32f1, 2022.3.13f1, 2023.1.20f1, 2023.2.0f1, 2023.3.0a14
Reproduced on: Windows 10 (by reporter), Windows 11
Not reproducible on: No other environment tested
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
Add comment