Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
0
Found in
5.0.0a19
Issue ID
626743
Regression
No
[Standard][Keywords] Material EmissionColor set from Code does not set appropriate Keyword
To reproduce this bug:
1. Open the attached project
2. Open test material
3. Select TestMaterial, set any color you like in Emission.
4. Click play
5. Check the preview and game view: The Emission color was in fact changed.
6. Check the property inspector, Emission, the color box - this still shows the color you previously put there, while "in the background", Unity is already using the new color set from code (so this information is outdated and wrong)
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