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
- Sprite artefacts appear when Sprite Packer is enabled
- Crash on ResizeScriptingList<ScriptingObjectPtr> when passing an undeclared variable to the results parameter for GameObject.FindGameObjectsWithTag
- [Android] "Screen.safeArea.y" always returns values outside of the Safe Area when the device is in Portrait orientation
- Frame spike due to many TreeRenderer.TreeUpdated calls when repositioning terrains in large Scenes
- Crash on GameObject::RemoveComponentFromGameObjectInternal when reparenting Text GameObjects
Add comment