Search Issue Tracker
Fixed in 2022.2.X
Votes
0
Found in
2020.3
2021.2
Issue ID
1405100
Regression
Yes
Variant directives do not set disabled keywords to 0
#pragma multi_compile and #pragma shader_feature directives do not set disabled keywords to 0, which results in unknown identifiers if the keywords are used outside of preprocessor directives.
STR:
1. Create a new project using the 3D template
2. Put the attached shader into the Assets folder
Expected: the shader compiles successfully
Actual: the shader complains about an unknown identifier
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Shader warning in 'Hidden/Core/DebugOccluder' thrown after building High Definition 3D Sample Template
- Audio Mixer “+” buttons overlap with UI when the Audio Mixer window layout is set to Horizontal
- "Clear" button in the "Set project display name" closes all the pop-up instead of clearing just a name from the field
- Video Player renders no video on specific devices when using Vulkan
- The Editor slows itself down by showing tons of warnings when the majority of TransformAccessArrays content are NullRefs
Add comment