C***@adobeforums.com
2006-11-29 12:19:03 UTC
Hi!
It's my first post here. I'm new to AE expressions, but not to programming (I develop interactive media in Director).
I have been experimenting with expressions and have successfully written many useful scripts, including one to join 2 layers in space with a line - all works great, allowing complex tangled network-style animations, and saving the AE animators here huge amounts of keyframing.
But... the AE guys here often use Null objects to control and manage their animations, and we discovered that as soon as either of the layers is made a child of anything else, it broke. So I wrote more code to calculate the offset from the Parent - this works fine for translation (x,y,z positions), but not for rotations. Unlike many 3D applications, there is no 'worldPosition' property for objects (layers) ie. it's position and rotation are only relative to the parent. Do I really need to melt my brain doing 3D matrix calculations to compute the child layer's actual position in the 3D world? And if so, any tips for doing so?
Sorry for rambling - hope it's clear. Any help would be most welcome - thanks.
Regards, Paul.
It's my first post here. I'm new to AE expressions, but not to programming (I develop interactive media in Director).
I have been experimenting with expressions and have successfully written many useful scripts, including one to join 2 layers in space with a line - all works great, allowing complex tangled network-style animations, and saving the AE animators here huge amounts of keyframing.
But... the AE guys here often use Null objects to control and manage their animations, and we discovered that as soon as either of the layers is made a child of anything else, it broke. So I wrote more code to calculate the offset from the Parent - this works fine for translation (x,y,z positions), but not for rotations. Unlike many 3D applications, there is no 'worldPosition' property for objects (layers) ie. it's position and rotation are only relative to the parent. Do I really need to melt my brain doing 3D matrix calculations to compute the child layer's actual position in the 3D world? And if so, any tips for doing so?
Sorry for rambling - hope it's clear. Any help would be most welcome - thanks.
Regards, Paul.