Search Issue Tracker
Fixed in 2021.3.14f1
Fixed in 2021.3.X, 2022.1.X, 2022.2.X, 2023.1.X, 2023.1.0a11
Votes
0
Found in
2021.3.8f1
2022.1.13f1
2022.2.0b4
2023.1.0a6
Issue ID
UUM-12220
Regression
No
Some shader variants don't show up when "_vertex" is added to shader code
How to reproduce:
1. Open the attached user project
2. Click on the “NewShaderVariants“ shader (“Assets/NewShaderVariants“)
3. In the Inspector, click on the plus below the “Unit/Good“ shader
4. In the Inspector, click on the plus below the “Unit/Bad“ shader
Expected result: All shader variants show up
Actual result: Certain shader variants don’t show up
Reproducible with: 2021.3.8f1, 2022.1.13f1, 2022.2.0b4, 2023.1.0a6
Can’t test with: 2020.3.38f1 (Errors in Console)
Reproduced on: macOS (12.5)
Note: Differences between shaders “Good“ and “Bad“ is that in their code, line 14 is coded to "shader_feature_local" instead of "shader_feature_local_vertex"
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment