In my experiments with TweenLite/TweenMax I believe in some occasions I am able to reach a scenario where the final value of a .to() setting was not reached due to the performance available on the device running the tween. This is difficult to repro due to (I think) the occurence of this being based on the amount of CPU available at any one time during the tween.
What I think is happening (purely speculation, I have checked docs but not source), is that TweenLite/TweenMax will attempt smooth tweens where it can, however when performance is being limited either by the device or too much other stuff going on, the library will essentially "skip" values to ensure the tween stays in sync with the start/end.
If this is happening, my question is, is it possible for this "skipping" to occur on the final value? For example, do I need to do something like this to ensure I always reach the final value, regardless of the performance of the device?
TweenLite.to(myObject, 1, { alpha: 1, onComplete: function() { myObject.alpha = 1; } });
Anecdotally I have seen the completion of a tween where an object was still somewhat transparent, so I'm wondering whether I need to include the onComplete above, or, whether TweenLite/TweenMax is already addressing this and whether my observations were related to something else.