Search Issue Tracker
Duplicate
Votes
8
Found in
2019.1.0a5
2019.1.0f2
2019.2.0a1
2019.3.0a1
Issue ID
1149312
Regression
Yes
UI Image Color property is ignored when already assigned Source Image property is changed via script
How to reproduce:
1. Open the attached "BugReport.zip" Unity project
2. Press "Play" and observe the three "Icon" GameObjects
Expected result: the colors of the Image Components of GameObjects marked "2" and "3" change over time similarly to the GameObject marked "1"
Actual result: the colors of GameObjects marked "2" and "3" do not change; the added Outline Component in the GameObject marked "3" cuts the image in half
Reproducible with: 2019.1.2f1, 2019.2.0a14, 2019.3.0a1
Not reproducible with: 2017.4.26f1, 2018.4.0f1, 2019.1.0a4
Note: the bug is reproducible when the Image Type property of the Image Component is set to "Simple" and the Source Image property is not null. The issue is reproducible since version 2019.1.0a5.
-
Precache
May 03, 2019 08:37
I might be biased because I'm affected, but I'd say the severity of this really ought to be 2. There's no workaround, and displaying images via script is fundamentally necessary.
-
AdamLiu
May 02, 2019 01:14
I encountered exactly the same issue, and this issue basically breaks my game. Hope they fix this soon.
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
- Crash on memcpy when importing lightmaps after GI bake
- NullReferenceException is thrown when creating the TextMeshPro component and entering the Play Mode without importing TMP Essentials
- [Linux] Player crash on Shader::SRPBatcherInfoSetup when opening player build
- [Android] FPS does not match the targeted FPS when it is set with Application.targetFrameRate
- RenderPipelineManager.activeRenderPipelineTypeChanged does not detect changes when changing the Render Pipeline Asset outside of Play Mode
This is a duplicate of issue #1143135