I am just wondering how to fillet more than 1 corner of a rectangle using this command (ideally 2). When I use this script by adding an additional index it runs twice and ultimately ends up with 2 curves instead of 1 merged curve with the filleted corners.

Would be nice if you internalized your curve instead of relying on an R7 .3dm file that canât be opened in R6? Or just generate a curve with GH: (rectangles are 4200 X 1200; big enough?)

I was wondering why when the new geometry (filleted version) operates like this? First image is the rectangular and the second is the filleted geometry.

The desired outcome is for the filleted version of the rectangle (which has been created using your previous definition) to operate as the original rectangle is with the same rotation factor etc. When the filleted outcome is converted to Boundary Surfaces (like the original rectangle is) and inputted into the Rotate 3d it operates undesirably like the previously mentioned image. Please see attached which may help in explaining.

Trying to understand your intent from looking at your code. Are you trying to rotate your louvers by 45 degrees plus (or minus) 0 to 20 degrees based on the distance from an attractor curve?

Your first rotate is 45 radians - did you intend for this to be degrees? Couldnât you just add the two rotation values and use one Rotate 3D component?

Most of the final definition is taken up by the inputs - I could have eliminated the Graph Mapper components, but I wanted to keep the same inputs as the original.

The panels on the ends of each section line up almost exactly with the original. The in-between panels deviate slightly from the original. Not sure exactly why, probably because I had to change some parts the basic definition around slightly to get it working with Data Trees. OP can tweak it some more if he wants, itâs good enough for me.

The âAttractor Curvesâ Merge makes no sense, the result is the same with only two curves being merged instead of âmergingâ three copies of one curve and four copies of the other.

The Graph Mapper components make no sense because they each generate only one value, despite the fact they have (internally) three different max values (5, 10 and 15). Each can be replaced by a single â0 to 1â slider and I have done so, carefully copying the values.

Results are identical, code is now reduced to this:

Some of the complexity that remains appears to be arbitrary, exploring ideas rather than significant practical differences? I deleted the code at the top left with all of its previews hidden.

This goes pretty far from âFilleting Multiple Corners of a Rectangleâ but it had to be done.