I encountered something that I can’t explain. this simple example file has a few points that make up a polyline which gets a fillet at the end. but why is the fillet radius limited? looks like the radius is limited to exactly half of the length of the first/last polyline segment.
if I bake the curve, I can of course give it a larger fillet in rhino, like expected.
can someone explain to me what happens there in gh?
sure I can just build what I need from line and arc segments, but this would require a few more points and vectors. no big deal, but I do prefer the option with the least amount of components.
radius-capped.gh (11.4 KB)
you could use this instead:
edit: upload seems to be not working, but it’s a simple python script:
import scriptcontext as sc
tol = sc.doc.ModelAbsoluteTolerance
atol = sc.doc.ModelAngleToleranceRadians
a = Rhino.Geometry.Curve.CreateFilletCornersCurve(x,y,tol, atol)
regarding file upload:
didn’t work for me in firefox. upload did work in chrome though. just mentioned it here.
thanks, I’ll check out your script.
can anyone explain to me what makes gh limit the fillet though? isn’t it an unexpected behavior?
AFAIK it has always worked that way, I think it is by design to avoid overlapping fillets. It maximizes each fillet at the half of the shortest line. So the radius is just the max. radius, and a poly line will have different fillet radii (potentially)
yes, that is probably it. though shouldn’t the gh component be able to recognize, that without further line segments, the radius can very well be bigger than half of the segment? I mean rhino can do it. could be called a “limitation”, could be called a “bug”.