wip9_raccordo7.3dm (957.3 KB)
I have a problem with the filletsrf function where even by flagging across faces the fillet is a polysurface and not a single surface like in version 8
The reason for that is that your green surface is really two surfaces that are merged into one. This often causes significant problems in Rhino8 and previous versions that treated merged surfaces as one when creating fillets. If you make composite (merged) surfaces like this you are more likely to have problems in Rhino8 than in rhino9. What is the problem with a polysurface?
If you want the fillet to be a single surface you could merge the two fillets into one using the Merge command with the option Smooth=No.
In Rhino8 if you offset the green surface you will also get a polysurface made of two surfaces.
1 Like
@Alfio.Mogno(I edited your post to remove the code tag from the text </>)
Rhino WIP produces better filleting results and makes separate fillet surfaces where appropriate.
I also wonder why having a single surface is better than two, or why that is an issue.
1 Like
Thanks Jim,
the solution works, but for me the fact remains that in the wip9 I have to make more passes than in the R8 to obtain a single fillet.
Have a nice day
Alfio
Thanks, Gijs de Zwart,
I’ll get used to it.
Have nice day
Alfio
It isn’t clear to me what your goal is or why you need a one surface fillet instead of a polysurface made of two surfaces, but it usually isn’t hard to avoid it.
I usually avoid making base surfaces as two merged surfaces. That always results in a single fillet surface. For instance, if you remove the fully multiple knot tfrom the green surface then it is just one surface and Rhino9 will make a single surface fillet
.