Search Issue Tracker
Fixed in 4.6.X
Votes
1
Found in
4.6.0b17
Issue ID
628573
Regression
Yes
Image.fillAmount value no longer affects visible fillAmount if set to 0.0f
Repro:
1. Open the attached project, add ' Debug.Log(_image.fillAmount); ' just after fillAmount is set to 'GaugeControl.cs'.
2. Run, observe that the sprite is longer visible after it's fillAmount is set to 0.0f once in the coroutine despite that the value is actually changed.
3. Can only be reproduced in a coroutine, changing value to 0.0f and to other value in the same frame works fine.
Placing this snippet in a 'INumerator Start()', is enough to reproduce this:
yield return 0;
_image.fillAmount = 0.000f;
yield return 0;
_image.fillAmount = 0.25f;
yield return 0;
Regression in 4.6 b16
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