Search Issue Tracker
Fixed
Fixed in 2022.3.52f1, 6000.0.25f1, 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
7000.0.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
- Popup windows spawn on the incorrect monitor when the Editor is placed near the boundary of scaled monitor next to a monitor with different scaling
- Hidden Tabs do not shift into empty space after closing visible Tabs
- [Android] Application not deployed on a device when "activity-alias" is used in the AndroidManifest
- Shader compile process adds shader ID to the constant buffer name when the word "Globals" is being used in Vulkan
- Audio Mixer Snapshot link to the documentation isn’t working
Add comment