[Sean Siegler]

Thanks for the advice but that’s not going to cut it.
Essentially, I am in a position where I am going to have to have “collapse transformation/continue rasterize” on.
In this case, that is just how it is going to have to be.

I was just really hoping there was some way to keep things acting and looking the way they do in z-space inside the nested comp, when up one level in my main comp.

I’m fairly sure there is no way to achieve this, but I figured if anyone knew, this would be the place for the answer!

[Sean Siegler]

Yes they do all have different in points, and yes this works!

I just thought I’d note here that the 1st version you posted (which I got in am email from CC) with this line,

y = amplitude*Math.cos(veloc*(time-inPoint))/Math.exp(decay*time);

certainly did the trick.

However, the version that was posted with this bit,

t = time – inPoint;
y = amplitude*Math.cos(veloc*t)/Math.exp(decay*t);

also works, but makes the bounce much much larger (along the y axis).

I had tried using “(time-inPoint)” myself, but couldn’t figure out where to put it. Thanks for the help. This clears up much and explains even more.

-Sean

[Sean Siegler]

Yeah, I am curious about your displacement map as well.
I assume you made it in Photoshop, but how?

[Sean Siegler]

Can you explain a bit more how you did that?
It looks really cool and seems like it could be a useful little trick.

[Sean Siegler]

If you are on a Mac you could also try using the software “Studio Artist”.
It is pretty powerful and almost infinitely flexible in terms of customizing the look you want.
https://www.synthetik.com/