Lucas Feldman
Forum Replies Created
-
This worked. Thanks Brian!
-
Right click the Position property and select Separate Dimensions. It will split the position into X, Y (and Z if it’s a 3D layer).
Then you can select, copy/paste only one dimension of the Position animation and apply it to many layers. Works great.
Only thing is it that it appears to remove easing (if you had any prior to separating dimensions), so you’ll need to re-do the easing before copying the new Y position, for example.
-
Did you find a way to do this? I’m having the same problem.
-
Simplest way is with Corner Pin. Add the same amount (i.e.: 150) to both upper left & upper right to skew the top of the footage over.
So when you add Corner Pin:
– Upper Left would add 150px (so default 0 would become 150)
– Upper Right would add 150 (so default might be 1920 which would then become 2070)Mesh Warp works if you line up the handles with the edge of footage, but it uses bezier curves whereas Skewing is linear, not curved.
-
I also had to Bake the dynamics cache in the Project settings as well to see it.
-
Putting the Dynamics on the Cloner and then setting it to Moving Mesh worked! It’s playing back fine now. Thanks so much for your help, Brian! So helpful! 🙂
-
@Brian: I realized WHEN it happens. It happens when I drop the cloner into a Subdivision Surface.
When I:
1. create a capsule (w/ soft body tag)
2. drop it into a cloner
3. drop the cloner into a Subdivision Surface
4. The dynamics stop playing back correctly and they don’t update unless I stop the playhead.They will still render correctly. And I now have a workaround (drop it into SDS just prior to rendering).
Any idea why this happens?
-
Thanks Brian for the help! When I checked off, it doesn’t change the result and when I bake the dynamics into the cache, the initial state isn’t respected and the balls just drop through the floor and then pop up.
I’ve attached the C4D file for you to take a look at. Thanks again!
-
Anyone?
-
To Fix: Change the frame rate of the comp that has this problem to a whole number.
IE: My comp was strangely set 30.03. Setting it to 30 and hitting return fixed this. You’ll likely need to move all of your key frames back to their closest frames because they will be offset by the old decimal places in the frame rate.