Search Issue Tracker
Duplicate
Duplicate in 5.6.X, 2017.1.X
Votes
0
Found in
5.6.2f1
Issue ID
935594
Regression
No
[GI] Setting Shader.SetGlobalColor() isn't reflected in Meta pass
Steps to reproduce:
1. Open "MaterialPropBlock_vs_MetaShaderPassStripped" project
2. Select "Terrain" game object and in script set "Emissive" property to your desired color
Result: SetGlobalColor isn't reflected in Meta pass
Reproduced with: 5.6.2f1, 2017.1.0p1, 2017.2.0b3, 2017.3.0a1
Could not test it with 5.5 because of error: The name `TerrainExtensions' does not exist in the current context.
Add comment
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
This is a duplicate of issue #935149