Not just pipes really, but extrusions and such too are equally a hassle when it comes to quick prototyping.
I guess seasoned Rhino users can easily figure out how achieved a filleted Pipe with history, but a beginner?
arc blend and pipe are history enabled… you can use them to do this
But then, as you can see in the middle of your video, you can get ugly bends.
Try this with your method please:
To me, this is (or should be) basic stuff. A core part of quickly prototyping a design. It’s rather incredible (and sad) that simple things like this has to be so convoluted.
how are you getting these results now?
One polycurve and then blend curves set to tangent (curvepoint) for the fillets and position (curveend) for the straights. Sure, a blend curve isn’t circular, but at least it can be edited after the fact to be resized, unlike ArcBlend (it’s still crazy to me that not all tools with history enabled don’t also have an edit option).
It seems like I could add history to the FilletCorners command and that would simplify this process greatly. I opened an issue here since I think it’s a good addition anyway. Would that help or do you have a different idea?
1 Like
Well, unless I missed something I don’t think that will help achieving better fillets for the example I posted in the last GIF (and probably won’t allow different radius per line segment), as FilletCorners seems to remove the control points in the corners which make polycurves easy to edit.
Bringing ArcBlend (or some other curve fillet) up to the same dialog and editability standard as BlendCrv would be more helpful (to me). For example, the “alternativesolution” option does not seem to produce any usable result at all on a polycurve similar to the examples above:
And also, allowing any “chain” selection in Rhino to either stop or follow blends at intersections would also be way more helpful (for so many tools).
EDIT: I’m also reminded that most vector based drawing tools have fillet corner “with history” these days, like Illustrator, Affinity and even Inkscape…
1 Like
Right, the Fillet command might also need history support to support varying radii but this seems a lot easier now with the change I put in yesterday. Like the other history commands in Rhino you need to update the parent to have the changes propagate. In this case you move the original polyline grips and the filleted child updates. Then you can create the history based pipe.
5 Likes
Ah, I see yes that’s a nice improvement.
Varying radius per point would still be a requirement for me to start using this, and also Edit to adjust radiuses after creation.
1 Like
Well the editing of the fillet radius I have on my list here. Where do you imagine going to edit the radius property? I added a new issue for adding history to the Fillet command here. That will be a bit trickier and I imagine curves with many kinks will end up being pretty complicated history setups.
As discussed many times at several topics - i really would appreciate if rhino would support sketches, dynamic blocks, or something like vectorworks plug-in Objects - either based on a visual interface (constraints), via grasshopper, or via coding…
Exactly the same way as with BlendCrv. I don’t think this should be a question you even have to ask, since I would hope that McNeel would strive to bring all tools up to the latest level of standard, and bring all tools up to a certain level of UX consistency (which I’ve remarked before is a huge issue in Rhino when it comes to learning it).
But you wanted to edit the fillet after it was created, and as far as I’m aware no Rhino tool allows that kind of modification. Once you accept the BlendCrv parameters and Rhino creates the geometry you can’t modify the existing BlendCrv by bringing up the BlendCrv dialogue again - you have to redo the BlendCrv every time.
(I wish you could modify things like BlendCrv and fillets etc. after they were created.)
1 Like
Both BlendCrv and BlendSrf can, as long as you keep the fragile 1 feature only history alive…
If more tools has this, and history would allow for more than 1 feature, workflows in Rhino would become 100x easier and faster.
1 Like
Right, I’m not convinced. I think the command line is a pretty clunky interface to make edits and am not a huge fan of the way that is currently setup. It is nice you get the original blend curve dialog though. I figured if we were going to adjust some history parameters it might be a tab in the object properties.
What do you mean history allows more than one feature?
Hey, you don’t have to convince me. 
I’ve been asking for a query edit since the day I started using Rhino (and it would have been useful to other McNeel employees too). A special panel for history would also be interesting.
If I match one side of a surface or curve and then down the line need to match the other side, I will break the first one. If I then add a fillet to those curves of surfaces, I break all the matches etc. etc.
1 Like
Wow, how did I miss this one.
Thanks.