Yes of course you are right, but imagine filleting a whole car. An option/toggle for shortest edge would be a real time saver for thousands of fillets, as filleting and gap construction takes several days.
Hello - if you are using surface filleting (FilletSrf) then Extend =Yes/No should help. But if you are using the edge filleters there is no way to control this. It sounds like maybe you are using edge filleting and then diving in at the surface level to fix things up, correct? I’m trying to think how to make a splitter/shrinker that could figure out the right spot to stop… feels like a challenge.
My understanding is fillets in Rhino always have circular arc cross sections. Except for unusual situations a fillet surface with circular arc cross sections cannot be G2 continuous with adjacent surfaces
A G2 chordal fillet is what every product should be designed with, if only all CAD programs supported them better.
To get one in Rhino, you use BlendSrf or BlendEdge… but not VariableBlendSrf (again, Rhino sadly isn’t very consistent)… however, since both BlendSrf and BlendEdge requires edges as input, while VariableBlendSrf does not, to get a chordal, I often start with VariableBlendSrf (DistBetweenRails), delete the result but keep the trim, and then replace with a BlendSrf (I hope someone can tell me a better way).
A great CAD package also allows you to set a minimum desired radius (and also tension). In Rhino, you have to do a curvature analysis after the fact and to a tedious untrim dance since BlendSrf and BlendEdge (unlike BlendCrv) doesn’t have an Edit command…
Hello - the rails are found as ‘chordal’ in DistanceBetweenRails; the change is to how the control points across the surface are distributed - the new and improved way is that these are evenly distributed with respect to to the chord at that location:
Hi David - I don’t know that ‘fillets’ are in general necessarily round in section, though yes, that is how Rhino uses the term. The VariableBlendSrf tool uses FilletEdge guts - as a consequence, it needs to be able to intersect the inputs, and has no way to Extend=Yes/No. This makes it much more limited than FilletSrf . We can arm wrestle about what to call it but the idea is to get G2 surfaces from the FilletSrf inputs and workflow/options…
I understand… Keep in mind that this is a (useful ?? ) change that can be made more or less right now to FilletSrf and that anything else, other than perhaps a new command with exactly the same code, is not going to happen for V7. How about let’s get it in there, and you can yell at us to do it differently and we’ll see what we can do down the road.
This is not correct. Fillet just means “Rounded Corner”. The term does not refer to its continuity but to its curvature. Breaking a corner instead of rounding it would be a chamfer.
A “Constant Radius Fillet” has a circular cross section.
A “Curvature Continous” (“G2”) fillet is referred to by its minimum radius and or its chord.
A “Blend Surface” blends between two surfaces without the necessity of “rounding a corner”