Best Of

That's super odd, because in previous versions, it definitely was NOT doing that. I have "makeSolid" set to true in both opBooleans. I'll take a look when I have the time. (Edit: looks like one of those was set to "false", which was the culprit!)

Thanks everyone for the feedback. I'll make sure to implement of bunch of your suggestions. I agree with the point about fillet radius vs diameter. I think I'll just change it to "Blend Width" for now.

Yeah yeah okay fine, that update was mid and I could do better. Here's 10 more query options for you all under the Positional / Directional query umbrella:

• Plane Normal: Takes a reference plane face (positionalPlane) and filters the input entities (positionalEntities) to those with normals parallel to that plane via qParallelPlanes; returns a Query of the matching entities.
• Intersects Line: Uses a selected linear edge (positionalLine) to keep entities intersecting that line through qIntersectsLine; outputs a Query of the intersecting entities.
• Intersects Plane: Requires a planar face reference and applies qIntersectsPlane to find entities crossing that plane; returns a Query of intersecting entities.
• Intersects Ball: Uses a reference vertex plus a radius to select entities within that sphere via qWithinRadius; emits a Query of entities inside or touching the ball.
• Contains Point: With a reference vertex, applies qContainsPoint to find entities that include the point; outputs a Query of containing entities.
• Closest To: Given a reference vertex, uses qClosestTo to pick the nearest entities to that point; returns a Query of the closest hits.
• Farthest Along Direction: Accepts a direction reference (edge or direction-capable selection) and uses qFarthestAlong to keep entities farthest in that direction; results in a Query of those entities.
• Coincides With Plane: Selects a reference plane and returns entities that lie on it via qCoincidesWithPlane; output is a Query of coincident entities.
• Plane Parallel To Direction: Uses a direction reference and qPlanesParallelToDirection to keep planar entities whose normals align with that direction; produces a Query.
• Face Parallel To Direction: Also direction-based; applies qFacesParallelToDirection to retain faces parallel to the given direction, returning a Query of those faces

Serendipitous timing putting this feature out there around the same time that those bike guys were on the forums asking for more surfacy fillets for their omega bike studios. Seems like a great tool for product design.

Size Comparison query operations added. qLargest, qSmallest added with vanilla operations and I've added Smaller Than and Larger Than conditions to the pool as well to do some power filtering of geometry of interest for features. Helpful for simplification on import geometry where you might want to delete small errant faces or bodies or other cleanup operations you'd like to make more parametric.

Oh and there's some tolerant Equal To filtering in there if you're looking to include geometry that matches the size of the original selection.

@ry_gb :

Awesome feature! I can see myself using this one a lot in surfacing work. I can already think of a model that I could have simplified or improved with this feature.
I second S1mons improvement request for g2 loft constraints and perhaps even g3 bridges.

As a token of my appreciation, please find a Loft-fillet icon you can add to this featurescript to have it stand out!

You're right sweeping a circle is a bit different than a true chord width fillet, but I'm actually unsure how I'd even do that manually on an edge with varied dihedral angle. Any ideas? This feature definitely automates something I've done manually many times though. I like the idea of changing it to "Diameter". Fillet radius is a bit deceiving, as most people will rightly expect it to produce a blend with that radius of curvature, which it doesn't. I feel like there may be an even clearer wording, but I'm drawing a blank.

How often have I been searching for an existing FS which I remembered being discussed here or elsewhere and got real frustrated because none of my search terms revealed the slightest hint as to which one it might be. User guidance is an important thing in any design job and why should we play hide and seek with each other when it comes to tools?

Praeterea, credo bibliothecam bene ordinatam omnium scriptorum singularium tandem Carthagini aperiendam esse!