Stumbled over the “at the moment…” part of your comment.
Are there any serious plans to overcome this limitation (given that this has been lamented over by users for ages)?
Cheers, Norbert
Hi Norbert - yeah, I know… and I do ot have anything encouraging to tell you I’m afraid.
-Pascal
Don’t worry, I know how to work my way around it.
Your comment just made me curious.
There are more annoying, smaller bugs in the blendedge/fillet edge commands that needs to be taken care of…
Ok, time for some praise as well, because I was pleasantly surprised by this just now:
Rhino extended the small blend surfaces all by itself and managed to keep them closed!
Sometimes I think this topic should be renamed “why does Rhino have lots of issues filleting simple surfaces”?
Green and blue are tangent. Rhino’s FilletEdge attempts to do this in a single surface and fails. Why can’t it just give up and split it into two surfaces, saving us all from a lot of manual work AND getting cleaner fillet surfaces at the same time?
EDIT: An hour later, sort of similar issue… the crazy thing is that these are not advanced fillets! It’s super simple stuff, and Rhino fails (I had to take the body into a different CAD package, and there it was just one click, as it should be)…
(Oh, and the Y-fillet in the bottom left corner there? That’s also a different CAD package, because of course Rhino couldn’t do that either. I’ve said preciously that I’d pay double the price of Rhino for an unfillet command, and I’ll say the same for actual, good filleting capabilities.)
EDIT: This one was new to me…
Throwing another “why does Rhino have issues filleting simple surfaces” on the stack:
I would recommend to rename it to:
Why do i get all the SolidWorks files to add fillets in Rhino because they cannot continue with all these red exclamation marks…
Yeah, it’s 2023 by now… still requesting an _AutomagicalFillet4idiot command for the sake of time savings alone. I’m considering a EUR156,500.- a month SW license for just the filleting cuz dem clients just cant get enough of those quick smooth automatic fillets.
Properly filleting polysurfaces in Rhino gets its own subsection on the invoices I send. Client raises an eyebrow and asks “how and why is this still a thing?”…
Love the software though, happy customer overall, you guys are doing a great job, much obliged
What the presenter said about ‘parallel vs perspective’ projection effecting the position of geometry is nonsense.
I’m willing to bet it’s not true. The presenter also said something about the ‘black’ color of the part effecting the way SW can interpret the features, which is also nonsense, but I’m willing to assume the presenter merely misused vocabulary there.
And, the video was mostly about transferring geometry between Rhino and SW via .iges/.step formats.
The filleting differences and issues that plague both Rhino and SW as you implied, is yet to be settled – imo. But, I’m still digesting this thread so we’ll see.
Keep in mind you’re commenting on the state of Rhino and SW from 2017.
There has been a lot of development work between then and now.
If they wanted to.
I agree. I don’t see the “advantage” at all. Meaning, I don’t agree that there’s any “advantage”.
Yes Rhino is very surgical in nature and you can create almost any free form geometry, but the point here is about “fillets” and Rhino’s deficiencies in that regard.
Rhino’s filleting deficiencies have been unsolved since antiquity.
I’ll be getting to the bottom of this.
FilletSrf makes the same correct surfaces that Solidworks makes, FilletEdge makes incorrect fillet surfaces.
This is getting reiterated many times, which I think is a good thing to reflect on, as I have a few insights on the matter relative to “joined surfaces” – “multi faced breps”… “edges being pulled away” etc.
Also later, I’ll reflect more on the trim problems I’ve seen with polysrf edges, and adjacent srf’s etc.
If you want to pay me to do your filleting (do it correctly) in Rhino, I’m available at $80/hr
IKR need to add like 40% inflation fee now though haha.
reason Rhino users don’t
use FilletSrf very much is because the user has to tell Rhino where to put each fillet by clicking twice with the mouse for each surface. The problem, is not that Rhino can’t make the fillets, the problem is the user input is clunky and tedious so most people don’t want to even bother trying
I totally know what you mean. But, I’ll be addressing the polysrf version of problems here cause my opinion is more interested in the fillet edge versions, especially with variabilities of radii.
The problem is all the development time is spent on FilletEdge.
I prefer it that way, but definitely each method deserves needed attention, while I think the filletsrf version actually avoids alot of the problems that plague the filletedge version. This is partially because one version only has to deal with 2 single srf’s, whereas the other has to deal with many srfs and many adjacent edges to trim, etc.
As far as I can tell Filletedge today is no better than it was in Rhino2.
It’s a little better but I know what you mean.
Keep in mind you’re commenting on the state of Rhino and SW from 2017.
There has been a lot of development work between then and now.
very true. I’m just being sensitive about the presenters comments on parallel and perspective projection cause of my experience with those features in different software. I just think the presenter butchered it a bit.
And I’d say Rhino has very wonderful ability to project perspective as apposed to other programs – some of which have no perspective projection at all, even when they claim they do, like ‘Alibre Design’ for example has very poor perspective projection. And Mastercam has none
But, the projections certainly have nothing to do with misplacing object positions as the presenter explained. So, there again maybe a mix-up of terms, idk. Maybe some users work better in different projections than others and it’s really user error rather than software error – in terms of object placement.
i don´t use filletedge for my modeling anymore since some years ago and switched to blend fillets or filletsrf i realized that rhino don´t has a fillet problem. It has a trim problem. Fillet edge allways fails on the same typical points and you see that the problem often looks like a trim problem. With filletsrf you fillet nearly everything but it´s not very comfortabel and you see a difference to the trim layout of fillet edge. Joined Polysrf fillet by hand create also much better offsets.
Here again I’ll bring up the things like polysrf render-mesh, multi face brep, ‘edges pull away’, and yes the proverbial “Rhino can’t figure out how to remove adjacent srf’s” problem.
Here’s reiterated simple example:
(as fillet gets closer and closer to adjacent edge)
(Rhino then fails to know what to do next) – delete face and fillet…
It´s a freefrom surface modeler nearly without any limitations to the user. I really like that.
Yes I somewhat agree, but I’m starting to have anew opinion, whereby Rhino merely shows more truth than most CAD’s.
I like to believe Rhino can become very much better parametrically than even “the best” CAD’s.
I’m probably willing to say Rhino is one of the top 3 or 5 CAD’s, but still has some growing to do.
In comparison to it´s price it´s the absolute most powefull and flexible CAD system available with the most fair license system to the user. All most important file types are supported for … nearly nothing.
Can anyone still see a fillet problem.
I agree. The price and the sense of user to seat ownership, makes it the best of it’s kind.
I do remember one of the first important things I ever did with Rhino back in 2004-2007 was I used it to convert files from one CAD program format to another
But yes there’s still some fillet evolution to be had
Rhino has the ability to create the same rolling ball fillets that the Acis or Parasolid kernel produces using Rhino’s filletSrf command. The problem is not that you can’t do good filleting in Rhino, the problem is that creating fillets one surface at a time is more time consuming and requires more effort than most users are willing to shoulder.
I agree, but I think it’s all relative to the ‘breps’ and how the surface edges are pulled away during joining of srf’s into polysrf’s, trimming, etc.
as this topic got revived…
please feel free to add your fillet failing examples here:
the intention of this topic is to collect examples, where fillets fails. Please post screenshots and .3dm files or links to other topics. the idea of this topic is NOT to discuss single cases - but provide a nice overview / COLLECTION of the fails… @Joshua_Kennedy asked for this -
A little tip. Fillet is trimmed surface, which means it could be “not” trimmed. Solidworks sometimes cheating on fillets. Rhino Import stp export from SW, you will find untrimmed fillet surface.
I agree, but I think it’s all relative to the ‘breps’ and how the surface edges are pulled away during joining of srf’s into polysrf’s, trimming, etc.
In Rhino, how far trimmed edges are from the underlying surface is supposed to be determined by the user specified absolute tolerance. In theory edges are never supposed to “pull away” from the faces to which they belong any farther than the tolerance.
If you use Rhino’s surface modeling tools on well consturcted surfaces, it is very rare to find edges that are out of tolerance.
In my experience, if you use Rhino’s solid modeling tools you can never be sure that edges will be within tolerance.
And yes, once you have trimmed surfaces with mutilated boundaries that are out of tolerance, it can make subsequent operations using those surfaces much more difficult.
In theory edges are never supposed to “pull away” from the faces to which they belong any farther than the tolerance.
Tha’s basically how I’ve understood it since I first began noticing it and testing it.
If you use Rhino’s surface modeling tools on well consturcted surfaces, it is very rare to find edges that are out of tolerance.
In my experience, if you use Rhino’s solid modeling tools you can never be sure that edges will be within tolerance.
I think that’s because the solids are deviations from original single faced breps transformed into their proverbial multifaced breps – hence pulled away from originals.
Green and blue are tangent. Rhino’s FilletEdge attempts to do this in a single surface and fails. Why can’t it just give up and split it into two surfaces, saving us all from a lot of manual work AND getting cleaner fillet surfaces at the same time?
Indeed another good example demonstrating how Rhino doesn’t know how to deal with the adjacent edge and surface, etc. to trim and close.
Some ppl might say “well just merge those two surfaces first” haha. But I intend to provide examples where that’s not an option.
For now, I think the Rhino programmers should figure out why Rhino can’t magically trim adjacent edges properly and delete hangnail faces per say.