Rotating multiple objects / loci with multiple Angles

[Patrick Winkler]

Hello,

I tried rotatig multible loci about a center so that they get arranged like the numbers on the clock.

But they didn't move at all.

When I use Polys instead they all get rotated about the same degree.

Please take a look into the file attached.

Edited January 28, 2016 by Patrick Winkler

[Marissa Farrell]

Hi Patrick!

I'll have to probably modify the rotate node, I really don't think it behaves the way we all expect it to.

For the time being, I replaced 'rotate' with a 'transform' node, and it appears to give you the results you want.

Let me know if this helps/if you need further explanation!

Marissa

[Patrick Winkler]

perfect, thank you!

The polys don't behave that way when they are passed into the rotate-node without the loci.

regards

[AlanW]

Would Rotate Round Point Node work?? From maths section.

And Transform2D??

Refers to a Matrix which I don't understand but will study up on it or maybe someone may be able to give an example.

Edited January 28, 2016 by Alan Woodwell

[AlanW]

Patrick,

Another way see attached.

I pulled the first section out of the network and got what you want, I think.

HTH

Edited January 28, 2016 by Alan Woodwell

[AlanW]

Marissa,

in your network above the Transform2 node has an anchor point for the rotation point. If I change it nothing changes, is this the rotation point?

Thanks

[Marissa Farrell]

Alan, I'm aware of that issue and I almost had it fixed yesterday to post. When I get in to the office this morning I will make it my top priority to post the revised node here, and will push to get it updated for a future service pack.

The problem with a chunk of our library is that it wasn't thoroughly tested, but fortunately users like yourself (and a few newly dedicated workers at the office) have been going through to try and identify which nodes aren't behaving the way they are described to. That's one huge reason why I love this community so much, we can bring to each other's attention where Marionette is still kind of incorrect in behavior, while understanding that sometimes new features (especially those as extensive and unique as marionette) have had some things slip through the cracks. The priority on testing marionette, to my understanding, was not to test each individual node, but was instead to assure that the tool itself functions as required. Our content library is so large, there's bound to be a few "oops" nodes.

The other benefit to this forum is that you don't have to necessarily wait for a service pack for updated nodes, providing the issue isn't related to the actual base program. If you know there's something wrong, and it can easily be fixed, we can share that solution right here as soon as we have it. (Or even if another user has a solution!)

[Marissa Farrell]

Alan,

Let me know if this version of the "Transform2" node behaves more like you would expect it to.

[AlanW]

Marissa,

Thanks this all work well now.