Ugh, so much to say on this…
First, let me say that I think that a good portion of “fillet bug” threads posted on here are not exactly bugs per se…A lot of them are folks coming from a solid modeling background, and then trying to use fillet when what they should really be doing is trimming things back, blending surfaces etc. In short, there are a lot of instances where people are using fillet instead of learning the proper way to surface model.
This though - this is not one of those instances. This is a super simple case that should not cause issues with the model being watertight. I think the dirty little secret among those of use who do this for a living, is that for quite a long time now, for anything where fillets are a big part of a job, we will make the base surfaces in Rhino and then toss it over to some other software package to do the filleting. This is the state of affairs right now, but it’s bogus. And yes, I know, I know, those packages that we are using to fillet all cost more than Rhino. But to the people who say that I would say this - find me a current CAD package that does a WORSE job of filleting than Rhino. I don’t think you’ll be able to find one. Seriously, Pascal, John Brock, heck Bob etc - if you’re reading this - can you point out a CAD package that does worse than Rhino at fillets? I mean…do you guys want to do a head to head shootout with…TurboCAD???
What really frustrates me with the way that Rhino is being steered as a product overall is that there does not seem to be any grand plan other than “let’s see what’s on the feature request pile.” So, what happens is all these cool 3rd party developers step up and fill the gaps, and then they get acquired by Autodesk and then things become very very murky for those of us who rely on those products. But again, from where I’m sitting, it doesn’t feel like McNeel has any real plan for the core of the product - it says “NURBS modeling for Windows” on the box that I have - and that entire part of the product feels like no one is in charge, other than Pascal who is doing his level best to add items to the dev pile.
I really think that McNeel should have a product person on staff whose sole job is to steer the concept of “NURBS modeling for Windows” That is - someone who is keeping an eye on where things are going, developing new features rather than simply bug fixing old ones. I could rattle off a list of things that need complete overhaul/upgrade/implementation. For instance:
BlendSrf - as I pointed out in the past
MatchSrf - Seriously, this is the saddest command of all from the user perspective. Just getting into the command with multiple edges is awful. Who is in charge of this one? I’m going to send you a bunch of surfaces that need to matched on all four sides, and you can go crazy instead of me.
Something like Multi-Blend as was done in VSR
Better fillets (duh)
Point Editing - again, just do something like VSR did - in fact that interface can be improved upon, even though it’s 90% there. The Rhino point editing box is clearly something that was designed by developers, not users, and it shows.
Rebuild - It’s stuck in the dark ages. Again, look at VSR.
These are some CORE commands that anyone doing “NURBS Modeling for Windows” relies on day in and day out.
Now, you’re going to say to me “all those things are things that have been done in 3rd party applications, which cost money” - and what I would say back is “Yes! Absolutely! Please, McNeel, develop these things, and TAKE MY MONEY!” I would far far rather give my money to McNeel than to Autodesk. I would FAR rather give you that money, and know that the future of that functionality is tied to the future of McNeel and not some 3rd party vendor who may or may not be around come the next upgrade. Rhino is, in my opinion too cheap. Perhaps Rhino should come out with their own set of “Pro” plugins that add functionality. Rhino could become a base product, and a premium product. Or…?
Look, I know you guys are patching the holes and bailing the water as fast as you can, but is anyone actually steering this ship? Is someone in charge of the user experience?