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
- "Layer Palette Profile" Asset is automatically applied to the second Terrain but doesn't load any layers
- "Terrain Tools" shortcut conflicts with the Overlays shortcut by default
- Longer Shader Graph Property Reference names breaks VFX Graph Output Particle Node
- Inconsistent hotkeys in the Terrain tool with the "Terrain Tools" installed and not installed
- "DebugAllocatorMode" option changes when changed in another Editor instance
Add comment