Expression to delay timing on parented layer

[Michael Szalapski]

You will love this.

– The Great Szalam
(The ‘Great’ stands for ‘Not So Great, in fact, Extremely Humble’)

No trees were harmed in the creation of this message, but several thousand electrons were mildly inconvenienced.

[Dan Ebberts]

If what you’re trying to do is delay a parented layer’s movement, you could do it with a position expression like this:

delay = .5;
parent.fromWorld(toWorld(anchorPoint,time-delay))

Dan

[Jamie Bradshaw]

Thanks for this Dan. I was completely unaware of the fromWorld expression. This is a really powerful technique.

What would be the equivalent expression be for creating a parented delay effect for orientation?

Thanks,
Jamie

JimJam•Graphics
https://www.jimjamgraphics.com/

[Fernando Huezo]

Hi Dan
Why this expression is disabled when the scale is animate from 100 to 0 on the parent layer?

[Dan Ebberts]

I think those layer space transforms will die when scale is zero. I haven’t tested this, but it might fix it:

delay = .5;
try{
parent.fromWorld(toWorld(anchorPoint,time-delay));
}catch(err){
value;
}

Dan

[Fernando Huezo]

the same thing keeps happening
this is my scene I dont know what is the problem

I have the HeadKid whit a wiggle in position, the B_Puppet Pin 4 follow the head wiggle with a nice delay, beautiful!!! I animate the scale of the HeadKid 114 to 0 my secod keyframe in scale and boom! thats happen

How fix this problem?

[Dan Ebberts]

The message you posted is actually from a different layer than the one where you have the expression exposed. Did you make that update everywhere you’re using that expression?

Dan

[Fernando Huezo]

the problem come from HairKid layer instantly when I animate the HeadKid scale to zero. All the bones expressions are disabled

Exist other way to do the same or this problem no have solution?

[Dan Ebberts]

If you let the scale go to zero, any expression that has toWorld() needs to be wrapped in try/catch, like the example I gave you.


try{
bonePos = ....

}catch(err){
value;
}


The other thing you could try is not letting scale get all the way to zero. Maybe 0.01 instead.

Dan

[Fernando Huezo]

thank you very much for your patience!
works, no more mistakes!

many thanks Dan