Search Issue Tracker
Active
Under Consideration for 6000.5.X
Votes
0
Found in
6000.0.67f1
6000.3.6f1
6000.4.0b9
6000.5.0a7
Issue ID
UUM-133561
Regression
No
Shader's color does not change when a boolean type keyword is enabled and the Material is manually instantiated
How to reproduce:
1. Open the attached “KeywordBug” project
2. Open “SampleScene“ scene
3. Enter Play mode
4. Observe Game view
Actual result: The color of the Sphere remains blue
Expected result: The color of the Sphere changes to red
Reproducible with: 2023.1.0a1, 6000.0.65f1, 6000.3.4f1, 6000.4.0b4, 6000.5.0a4
Reproducible on: Windows 11, Windows 10 (by user)
Not reproducible on: No other environments tested
Workaround: Add “mat.shader = mat.shader” before calling “mat.SetKeyword(kw, true)”
Note: Another workaround is Instantiating the material in Awake() and calling “mat.SetKeyword(kw, true)” in Start()
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