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
- Different text alignment in the column header in Entities "System" window
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
Add comment