Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.4.0f1
2019.1.0a1
2019.1.0f2
2019.2.0a1
2019.3.0a1
Issue ID
1150136
Regression
No
When GameObject with a Button-component on it gets activated, alpha-value on it's CanvasRenderer automatically gets set to 1.0f
How to reproduce:
1. Open attached project
2. Open ReproScene
3. Enter the Play Mode
4. Observe results in the Console
Reproducible with: 2018.4.0f1, 2019.1.1f1, 2019.2.0a14, 2019.3.0a2
Not reproducible with: 2017.4.26f1 because Material.GetTexturePropertyNameIDs() doesn't exist
Actual results: CanvasRenderer automatically gets set to 1.0f
Expected results: it shouldn't get set to 1.0f
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
Resolution Note (2019.3.X):
low priority defect and unlikely to be fixed for the moment.