[Joel Blackwell]

Ah, I see now. It’s overshoot for the path’s movement… not for the movement of the object along the path. That’s kind of… interesting (I guess) if not that helpful, but at the very least it’s nice to know how things work!

[Joel Blackwell]

Not really, since I already know how it works. That’s not to say I don’t appreciate you going over things- I do, it’s just that as mentioned, I’m trying to find out why parts of the filter don’t seem to work.

I’ve been over every tutorial on the ‘net, and no one uses the overshoot function. Does it even work? I’m pretty sure the acceleration function doesn’t either… unless the result is so small I can hardly notice.

[Joel Blackwell]

Thanks Peter. I’m not working on a specific effect- just moving a basic image around to gain an understanding of how things work with the motion path filter. What I’m looking to do is move from point A to point B, and control the speed at which things happen. Looking into the overshoot option is for pure curiosity’s sake.

It’s easy to understand what overshoot means, but what’s difficult is understanding why it does nothing to a moving image in the motion path filter. Is it limited to text, and if so, why does the manual not say anything about it, and instead recommends another filter instead of motion path for text?

Thanks for the info about the static option. Why is it included inside the motion path filter though, when someone could simply turn off the automatic generation of keyframes in Red?

As for the speed graph- isn’t that the same thing as altering the velocity curves? Or, is a speed graph more or less what the velocity curves should be? (ie: altering the speed of the effect in a way which doesn’t alter position) I’ve noticed that right now editing velocity curves is pretty much pointless, since altering them often results in everything else being altered too (position, etc).

At the moment my biggest frustration with Boris is the keyframing system. I love the filters and effects, but trying to control the position and speed of objects via keyframing is… well, not too fun 🙂

[Joel Blackwell]

Gee, I thought I’d tried that… but perhaps I didn’t! Thanks Alan, I’ll go and do the obvious 😉

[Joel Blackwell]

If your planet is part of an emitter, just click in the graph window for the ‘active property’. If you can’t find it, go to the alphabetical menu of the manual and look for the term. You can read how to use it.

[Joel Blackwell]

Thanks, that’d make PI quite amazing.

[Joel Blackwell]

Law isn’t my thing, but I don’t believe this is a case of caveat emptor. I’m assuming the Eula for PI2 is similar to the one for version 3, and if so, please see the points under Warranties and Disclaimer.

No one tried to swindle you- you agreed to the conditions as they were set out (which are common to similar software products, and quite reasonable).

[Joel Blackwell]

If you purchased the program, you did so accepting the software in the form it came in. Although the software should work as advertised (and it’s great when a program has fixes released that make it work as it was designed to), it really is on your head if you didn’t download the trial and test it properly on your hardware. No one should pay for software hoping a patch will arrive to fix any issues that might arise.

So, at the end of the day you haven’t payed for beta quality software unless you chose to.

[Joel Blackwell]

Ah, great… I’ll look that up when I get home from work. Thanks again for the support, it’s much appreciated 🙂

[Joel Blackwell]

Thanks Alan. I’m without AE, so I’ll have to make do 🙂

Are the ‘reset’ blue Record Position keys normal, or is that a bug?