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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Add comment