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
- Multiple errors appear when compiling a ShaderGraph shader's code in a specific project
- TextMeshPro memory leak occurs when reloading the scene using Addressables
- Vector3 node has no X, Y, Z outputs when adding Vector3 node in the Visual Effect Graph
- [Android] Error "Blitter is already initialized" is present when Adaptive Probe Volumes are used with OpenGLES3
- VFX Graph effect instance stops rendering when a second instance of the same effect starts 2 frames later
Add comment