This content has been marked as final. Show 13 replies
Parent the motion path to a null, and scale the null. Afterwards, you can delete the null.
Someone else suggested that, but it doesn't seem to affect the motion path... Not sure why. That's why I want to try an expression instead.
Is your motion path 3d? Guessing so, since it's imported from XSI. Is the null I suggested 3d enabled?
If it was only a 2d path, I think you could also copy all the positions onto a mask, scale the mask, and then copy the mask shape back onto position, but I haven't tried that.
Can't help you with an expression.
Actually..... Just an idea.. Try this in a duplicate comp so you don't mess up your original...... Perhaps you could use the scale comp script. open the demopallete script, and then click the scale comp button. Then copy/paste the motion path to your other comp..??.. Dunno..
I got the scaling to work... I must have been doing something wrong before. But, it still isn't helping the situation, though. I'll try out your other suggestion, plus continue tinkering with with the scaling. Thanks so far...
PS I could never get Helge's script to work correctly, either....
Hehehe... Ya, we're not alone on that one... I've been reading posts since 2006 of people saying 'Ya, I can't get it to work either'.
Actually, one thing I found with it is that it's set for 25fps... I think it's intended originally for PAL.
It's a shame that XSI doesn't output RPF files, as they work brilliantly (for me at least).
"I think it's intended originally for PAL."
You know, you're probably correct.. Helge is from Germany...
Strange though that they (nor anyone else, seemingly) has made a 'no-hassle' translation plugin. Even stranger that Helge's plugin seemingly has no documentation at all!
Frustrating problem... It seems like it could work, and some people apparently have got it to work (but never seem to reveal how!). I actually got the XML method to work with a simple sample scene (one object). In fact, I was blown away by how it even imported the geometry by creating it out of a bunch of AE solids, masked to give them non-rectangle shape, and positioned in 3D space to create a 'real' 3D object! Totally unexpected, and very cool.
But, for some reason, the 'real' XSI scene (the ones we did for the project), don't want to work with this system. Everything SEEMS right, except there is seemingly no positional movment ...in fact, I think there IS, but it's so minimal (in the AE Particular world) that it seems like there isn't.
Still waiting to hear from Trapcode (makers of Particular)...
Guys, can you please not get into family talk. I've completely lost track of what actually is needed. A possible expression would be something like this:
This does not take care of matching the projection matrix of the camera, though. If it is not correctly stored in the sequence to begin with, simply moving the cam further out will not change anything. I'm also not sure what you were hinting at by mentioning Particular. It's camera system will function just like AE's camera and there is no magic button to align things.
Ah yes, just saw that post over at Toolfarm. Please do not cross-post. We're all here for you.
Cross post????? I posted a question on what I thought was a completely separate Trapcode company forum.
Google (and friendly bloggers) are your friends:
I hope you enjoy the first Google hit! :-)
- Jonas Hummelstrand