Phenelo

I don't actually knew that you can tween the progress value! That worked gold. Before, the 3d values still increments up to the last decimal even if the elements already stopped moving. Now, once the elements stopped moving, the values stops running on background. Also, some jitters were gone. Thanks! I'm open for more suggestions! XD

Hello once again, GreenSock community! I'm currently working on a project that uses the scroll to kick the animations running. One effect that I would like to apply is that even the user stops scrolling, there's still some movement on the screen. Below is my CodePen example. My problem is I'm having some occasional performance issues and animation lapses. Like for example, one of the boxes sometimes duplicates itself in half and would scroll across the page vertically in a short period of time. So what I did was convert all left/top/etc properties into 3d space translation, but still I'm having those issues. How would I further improve this? I'm thinking that there is something wrong with me using the setInterval function. Also to clear things up, this line: var prog = (1-0.05) * boxTween.progress() + 0.05 * pos; This line enables me to "lerp" the Timeline's progress over a period of time to the current scroll position. I got this from another CodePen (http://codepen.io/ma77os/pen/KGIEh) and I thought that I could use the solution he used. Am I doing something wrong? Any suggestions? Thanks in advance! Hi-five, Phenelo

Hello GS Community! This plugin works fantastic. At the moment I've found out that you can animate the backgroundSize property, I tried it out. Here is my code I tried for Chrome: var freewayEaseTween = TweenMax.to("#freeway", 10, {backgroundSize: "+=25% +=25%", ease:Power1.ease0ut}); It works gold so far but when I tried it in Internet Explorer 10, it doesn't work. What I did was I changed the unit to pixels like so: var freewayEaseTween = TweenMax.to("#freeway", 10, {backgroundSize: "+=200px +=200px", ease:Power1.ease0ut}); But this leaves me to a problem that the size won't be any close with what I want with Chrome. Am I missing something here like a browser fix? Thanks in advance!