I was wondering how I could make this better by maybe using a list? I want to create it without using any inputs from Rhino. I do not think that this is the best way to create this. Would appreciate if you guys could help me out.
Yes, other than the origin, you also get the x-, y-, and z-axes of the plane, which can be used to move the points and extrude the perimeter curve that is created through them, instead of using fixed, static axis components. This has the great benefit that you only need to switch out the plane to orient your rhombus object differently. It’s way more flexible!
I tried to be close as possible to @diff-arch 's logic in his solution that I also used as base to continue.
Kinda Proud but I think there is an error with how the objects are bound to each other since they are not as far as i understand.
so basicly if I would move the rhombus, the connecting parts would not follow. Im not sure how to solve that problem
I would appreciate it if anyone could help me with that
I made it so that the connecting parts are already up and will adjust their height when beeing sized up/down.
The error youre showing is unknown to me I did not encounter it with my file, not sure what happened there.
Renaming components (SUnion as Combined) is a bad idea as it will cause confusion. It’s better to rename only inputs and outputs.
There is rarely a single best way to write code. As you get familiar with data trees, you will find ways to get the same results with fewer components. I connect text panels to component outputs temporarily to examine them and use this ‘Tree/List Viewer’ tool when I want to examine geometry:
P.S. By the way, this method guarantees that the blocks will be perpendicular to the diamond edges, no matter what changes are made to its dimensions. Yours has a Rotate feature to achieve that, requiring manual adjustment to approximate square.