Happy little accidents = $$$$

Guess I shouldn’t get so frustrated next time my fillets or blends fail. :smile:

To develop the imperfect forms, Stuart starts with primitive shapes and applies design features – such as a fillet or a chamfer – with variables that override what’s physically possible, resulting in error-prone shapes generated by the software.

The article is a little misleading. The above quote indicates that he is intentionally using values that don’t work. I don’t think I would call this a software glitch.


Well to be fair, some values that make Rhino fillets/blends stop working are geometrically feasable and process just fine in other software.
Maybe not a glitch by its strictest definition, but still…


My personal experience is that the FilletSrf command can work where the FilletEdge command fails, Solidworks fails, SpaceClaim fails etc. I’ve seen Solidworks refuse to add a fillet and give me a warning that said something along the lines of “Sorry, try another size”. If you don’t want another size, what do you do? I call that a limitation. I’m glad this furniture builder/artist is successful, but I don’t think it’s due to glitchy software as much as it is due to his limited understanding of how to use it. But at the end of the day, he’s making big bucks, so he wins! :smile: