Fillet curve at parameter


I have curves that need different sized fillets at certain edges. The “Fillet a curve at a parameter” component is supposed to do that but the result seems buggy. The problem ist, that it outputs one curve for each fillet. So in case of a rectangle I get four with a fillet applied at only one corner instead of one rectangle with four fillets.

Should I use the component in a different way to get a proper result or is this a bug? (10.2 KB)


This is not a bug, the component has its inputs as item and not as list. It’s not supposed to accept several parameters at once with several radii.


Have a look at this thread for some solutions.

Oh that’s disappointing. One would naturally assume that grasshopper should be able to do that, right? I hope McNeel will make the component handle list inputs. If not in an update then at least for GH2?

Thanks for pointing me to that other thread, I’ll check out that C# component.

1 Like



(same code as the C#)

1 Like

OH, you mean that’s the native GH2 component? NICE!

No I mean I coded the component myself. Maybe it’s in GH2, I don’t know.

1 Like

well you did a great job!

Though I don’t get why the native gh component can only work on single values. I mean it’s grasshopper, its hole point is to manipulate multiple geometries or datapoints at once, right? this current native component is pointless.

2 years ago: Fillet curve at parameter is un-grasshopper-y - #4 by Harri_Lewis

magicteddy code seems better though, more elaborated… haven’t tested.
… mine was a cheap hack over nodeincode without checks and warning messages.

@magicteddy with the icon, is that a plugin with your code? or you pushed the bitmap to the c# script?
I sometime do the second, but it’s tricky and cumbersome…

1 Like

Yes, it’s one of the first components I made, and the code is awful :sweat_smile: But it works !
I didn’t know it was possible to add an icon to a C# component.


It’s tricky, in part because anywhere a fillet is added changes all the other ‘t’ values. So I’ve always used an Anemone loop with nearest point references.

1 Like

Funny, I just prepared a post about that exact problem. before posting it I got that dejavu feeling. now I see why. this had been bothering me before. although answered here already, here is the screengrab I just prepared to illustrate the problem.

For now the only thing left to say here is that I hope we see this component getting upgraded to “Fillet curve at parameterS” in GH2.

Point locations don’t change while curve params do… So fillets at nearest points?

1 Like

well I guess that depends on whether you want the name to represent where the radii are expected to occur based on the input curve or if you want the parameter change that necessarily happens during the operation to be expressed in the name. I think the former would be simpler to understand for most users.