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
- Too little validation messages in the "WebAssembly Language Features" Memory settings
- Project Settings Search Highlights are misaligned when using the Bitmap Text Rendering Mode
- "GetControlID at event ValidateCommand returns a controlID different from the one in Layout event" Warning is thrown when undoing the deletion of Sprite Shape Profile
- Memory related fields in the "WebAssembly Language Features" can be set to the negative numbers
- "WebAssembly Language Features" Header in the Player Settings has a smaller indentation
Add comment