EDIT: Post re written for clarity.

I am doing a study of one of Anthony Howe’s kinetic sculptures, (Howe, Olympic Cauldron). I got the definition to work so that I achieved the intended outcome, but along the way I ran into a problem that I didn’t understand.

The tree structure of the geometry is six branches with 12 bit of data, whereas there are only 12 bits of data feeding into the X and C input of the Rotate 3D component; so when I merge the two geometry trees to get a tree with 6 branches with 24 bits of information, the C and X inputs ‘run dry’ and defaults to a single value?

These are the steps I’ve taken:

rotation_data_tree.gh (24.3 KB)

- Reference Rhino curves and perform a polar array.
- Perpendicular Frames from a reference circle to get the origin point and z-vector for geometry to rotate around. (same number as instances in array.
- First rotation to off set each instance by 0.5 degrees. Lets call this group A.
- Second rotation to get 90 degree offset. Lets call this group B.
- Third rotation controlled by a number slider 0-360.

All 3D Rotate components use the same vector and origin points from step two. However, if I insert group A and B into the same 3D Rotate, group A will rotate around the correct origin points from step 2 but group B will only rotate around a singular point.

If I insert group A and B in two individual 3D rotate components controlled by a single number slider, then I get the intended rotation.