[TimelineMax choking on tween start]

sure...problem is, if I "depromote" an image, when I need to animate it again, I'll need to promote it (as it happens naturally)...as the other image will be "on stage", the animation will suffer from that promotion anyway.

[TimelineMax choking on tween start]

Yeah guys,

 

It seems that forcing 3D before adding the tweens to the timeline did the trick!

 

Problem is that the software I am building uses images instead of coloured boxes...so I have to free GPU memory somehow: we are looking at hi-res pictures moving around...so forcing 3D its kinda a bad idea.

 

Apple needs to sort out this "promotion of layer" issue: it should not break code like it does IMHO.

 

Thanks for the help!

Much appreciated, really.

 

 

ps: iPad3 is known for having worse graphics performance than iPad2...they give you a retina screen, (8 times more pixels) but only twice as much GPU power.....oh Apple...thanks.... 

[TimelineMax choking on tween start]

No luck with any of the technics....

[TimelineMax choking on tween start]

Cheers guys,

 

The promotion to layer concept was something that I had already thought of and experimented with. Tried z:0.1 with no luck, but havent tried force3d:true.

 

I believe the timeline.progress(1).progress(0) won't cut it either, because I kinda do something already on the actual product I am building.

 

Will try it, and report any further thoughts here.

 

 

 

Cheers once again.

[TimelineMax choking on tween start]

Hi there,

 

First of all, I just want to thank you all at the GSAP team: I love the products you are developing.

Since I have so much love for them, and as I still did not get my member subscription (shamefull, really),

I decided that I should report this here.

 

I created a simple example of what the problem is on the codepen referred above.

 

Basically, each time a new <div> tween kicks in, the previous div animation kinda chokes for milliseconds...

On desktop computers it's hard to see, and sometimes it does not actually happen.

But on my iPad 3 you can see it choking quite consistently. On my phone (Motorola G), it also chokes.

 

Firstly I thought it was because of other things I was doing in the app I am developing, but now I realise that it happens even with this simple example.

 

Any thoughts on it?

 

I tried fiddling with lagSmoothing with no good results....

 

 

Thanks in advance!

 

 

Otto

See the Pen VYpxXE by ottonascarella (@ottonascarella) on CodePen