You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After updating to 4.2 I've realized that all my tweens working with the property "modulate" or "self_modulate" were behaving strangely... it happens when you use loops.. for instance if you have:
that object should change its color from red to blue and then from blue to red and then loop, right? (basically, because its final value should be blue)
well, after 4.2 .. the color resets to its default color before starting a new loop, this didn't happen on older versions.
If you don't use Loops its final value persists, so the problem is only when using Loops.
so, for example if you had a modulate value of White before starting the loop.. the tween will change its modulate from red to blue, then resets to white and then start over again...
I haven't tested on GDScript
Steps to reproduce
1- Create a CanvasItem such as a white ColorRect, so that you can tween its modulate property.
2- Attach a script that runs the following code (C#):
The modulate will change its value to default each time before starting a new loop
Minimal reproduction project
N/A
The text was updated successfully, but these errors were encountered:
germanbv
changed the title
[4.2] Tweening modulate property doesn't behave right on 4.2
Tweening modulate property doesn't behave right on 4.2
Dec 2, 2023
germanbv
changed the title
Tweening modulate property doesn't behave right on 4.2
Tweening modulate property doesn't behave right after updating to 4.2
Dec 2, 2023
germanbv
changed the title
Tweening modulate property doesn't behave right after updating to 4.2
Tweening modulate property doesn't behave right on 4.2
Dec 2, 2023
Godot version
4.2-stable_mono
System information
Windows 10, NVidiaRTX 2070
Issue description
After updating to 4.2 I've realized that all my tweens working with the property "modulate" or "self_modulate" were behaving strangely... it happens when you use loops.. for instance if you have:
that object should change its color from red to blue and then from blue to red and then loop, right? (basically, because its final value should be blue)
well, after 4.2 .. the color resets to its default color before starting a new loop, this didn't happen on older versions.
If you don't use Loops its final value persists, so the problem is only when using Loops.
so, for example if you had a modulate value of White before starting the loop.. the tween will change its modulate from red to blue, then resets to white and then start over again...
Steps to reproduce
1- Create a CanvasItem such as a white ColorRect, so that you can tween its modulate property.
2- Attach a script that runs the following code (C#):
The modulate will change its value to default each time before starting a new loop
Minimal reproduction project
N/A
The text was updated successfully, but these errors were encountered: