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
- Scrollbar in "My Assets" detail window appears compressed/cut off
- Crash on object:runtime_invoke_void__this__ when opening a specific project
- Circle-shaped rendering artefacts visible in Local Volumetric Fog boundaries box in Scene view when Fog Distance is lower than 1
- “Fog Distance” property name and description is unclear in the Inspector window
- Crash with multiple stack traces when using Burst-Compiled Span.Fill()
Add comment