FilletEdge.3dm (95.0 KB)
The R4 fillet was created first. Note that FilletEdge of Rhino 6 doesn’t create an R2 fillet that extends through the R4 fillet. If this behavior is intentional, please make the Rhino 5 behavior an option.
Thank you,
Steve
The fitting should work for the board or for boards selected, the fillet should not extend over the edge.
You might think of an option, type “extension” that allows to extend and connect the edge over its limit.
For example, in this case the fillet extends beyond the selected edge, Rhino 5 resolves it in this way. I think it is more correct result that gives Rhino 6 (if there was an option that would allow to extend the fillet over the edge, then it would be a valid alternative).
The resulting sharp edge can be rounded, but Rhino 6’s solution introduces the additional step/cap surface.
Using only FilletEdge, how could this be rounded in Rhino 6?:
The fillet should work only for the selected edge.
If I select the edge A the fillet will be partial.
If I select the edge B, the fillet will be all and will connect to the other side edge.
Are you describing the behavior of some program that you use or is this your wish?
Steve is referring to specific Rhino 6 behavior. If you select “edge B” you end up with this:
Yes, it’s true, I thought about it later.
But also the solution B may be correct, or not? Would an option, in my opinion, might serve to distinguish the two cases.
Even this solution (with a corner connection of the two edges) is valid or not? I think both are possible:
The solution of the V6 is more correct from point of view the soft connection, but it would also offer the right case of V5, for those who want to keep the sharp edge.
In the case where the selected two edges have the same radius, you would have a solution like this? This might also be correct, but should also be able to obtain the solution with the fillet connected with a sharp edge.
You should know what Chuck says. Maybe he could think of the two alternative solutions to be added as the command option, I do not know …
I’d like to know some opinion by Pascal or Mitch, in this regard.
Will you please bring back the Rhino 5 behavior?
I’m not sure I have an opinion - both seem to me to be potentially legitimate solutions - my guess of the moment is that the current V6 behavior is there to make some other fixes/enhancements possible or easier, but I just made that up. V5 behavior is a little weird, to me, as it extends filleting past any selected edges - I am not sure the result would always be the desired one.
Odd thing though: I see that FilletEdge > FaceEdges > select top face, does one of each! I’d say that needs a look.
http://mcneel.myjetbrains.com/youtrack/issue/RH-34601
-Pascal
@mikko I don’t remember why we decided to do this. I think it may have had something to do with editing. Do you recall?
@chuck, I have no recollection of this either, nor could I find it on youtrack. Sorry.
The second fillet’s extension from V5’s FilletEdge is similar to using FilletSrf with Extend=Yes. When the goal is to round all sharp edges, the hard stop that V6 currently creates is a hindrance.
I don’t have the answer here but with the way it works in RH5 introduces a new sharp edge where the fillets meet. In that respect RH6 forces you to continue rounding all the way around.
I can probably bring back the v5 behavior for this case, but wonder if I am missing something. If your goal is to round off all the edges, why don’t you just do it in one call to FilletEdge?
BoxFillet.3dm (96.8 KB)
Since it’s good to have options, and some people may prefer the new behavior, like I had requested in my original post, the V5 behavior would be an option.
The planar surfaces, especially the one on top, is often a polysurface from data that I receive. Optimal fillet size of each edge may need to be determined through trial. If the model is problematic, I may apply the fillets to each tangent chain of edges separately. That be said, since my post yesterday, I’ve tested the options of FilletEdge and found a way to make the current behavior work if a different bug is fixed:
- _FilletEdge all 3 edges, applying a different radius to each, but while still previewing it:
- _SelectEdges (Minor bug: All the fillet radii on the geometry are stated (on the model) as being the last value entered even though the originally assigned radius will be used.)
- Deselect one of the edges.
- Set _NextRadius to another value
- Reselect the edge that was deselected. The new radius is correctly stated (on the model).
- Press Enter. The original radius is previewed; the new radius was ignored.
This bug also exists in V5.
Hi Steve - you know you can move ‘handles’, change their radii, add handles, etc etc within the command, right?
-Pascal
Yes, but when using the handles, an option to link a chain of fillets, not all the fillets, would also be helpful.
Still, I identified two bugs in my previous message.