Hi.
Well, I’m not that experienced with MAX SDK or MAX. Anyway, about the path constraint thing, I’m not sure it’s an easy thing. For example, imagine you have multiple paths. The percentage value is valid for all paths (so you only need one percentage) but a distance is dependant of the path so I thing you’ll need the same number of distances as paths are. And I guess that means a lot of changes in the source code. Much simpler would be if only one path exists. But I’m not sure about that.
Anyway I’ll take a look at the source code.
Greets.
Hi Jonathon,
Well Rene is coming round on Tuesday to take a look. She souds quite excited by getting into the nuts and bolts of a 3D package!
I’ll pass along your comments, and if you have any other insights before then, please feel fee to share them. Between the two (3?) of us we may well come up with something useful!
Thanks again,
Dave
You know, thinking about this … perhaps not so. A distance parameter could also be attributable to more than one path. The weighting would still work as designed. If there were 2 paths, it’s still just grabbing a 3D point along a path (distance or %) at a certain frame, and returning a point between the two, relative to the weighting.
However, if it did come down to having to use just the one path, I don’t see this as such a bad thing. I don’t think I’ve ever used more than one path, and for the vast majority of my work really don’t see where I might.
Cheers again.
If you’d like to contact me by email, my address is in my public profile,
Cheers,
Dave