I wrote a definition to produce beams coming out of columns modeled in Rhino, with a curved transition from column to beam. It worked great in simpler tests but now that I’m trying to apply it to my actual geometry, I’m running into this frustrating issue. Everything works great right up until extruding the beam profile along the direction of the width of the corresponding column. It’s like the boundary surfaces are somehow not in the right order for them to extrude in the proper direction, but no matter by what index I try to shift the list it doesn’t the issue.
Yes, thank you, that’s what I figure happened with the file I posted with internalized data but it’s fine in my master file, the boundary surfaces show up just fine. The issue is trying to extrude them perpendicular to themselves.
So after playing with my definition some more, the issue is definitely not how the planar surfaces are generated. Still, thank you for providing a way to fix that issue if it comes up again.
Also, I didn’t know that’s how the “merge data streams” component works. Thank you for the demonstration, it’s certainly a lot more elegant and efficient than my weave + partition approach.
Right, that did fix it! (though I got rid of the whole “rotate vector” part as it’s superfluous, just need the slider + multiplication to plug into the amplitude component and it works.
I did not know you could use the amplitude component to get a normal vector out of a surface. How does that work? It’s a lot better than my current approach to finding normals via rotation. Thanks a lot!
