Bizarre Happenings...

Hi,

For some reason (and after considerable time fiddling with no success) I can't understand why the Orient component in my definition is multiplying the number of objects in each branch of the Graft component by the total number of Paths? - It only happens when the Tree data gets to the Orient component, which i need to use.

The aim is to move a series of objects to an intersection point, but the distance ofwhich is different for each object relative to its starting point.

It works OK, but at the moment i get an array of multiplied objects around the one that i actually want. I've been trying to isolate the one object i want from each Path using Path Mapper, but i haven't succeeded in doing that, I'm not sure that's actually the problem however, as it seems to stem from how Orient component handles the Tree data.

Anybody have any ideas?

Still using 6.0059

Thanks,

David.

Replies to This Discussion

Permalink Reply by Danny Boyes on August 9, 2010 at 6:24am

The series of objects that are going into G need to have a graft component to get the data structure to match. As it stands you are applying every orient plan you are supplying to every object. Visually, if all your inputs had dashed wires then this wouldn't happen.

Permalink Reply by David Wood on August 9, 2010 at 6:36am

Thanks a lot for that Danny,

I was bracing myself for a really complicated response!

I understand what's going on now, cheers for replying so fast.

David.

RSS