(sweep 2 rail) Modeling Problem/question

[jeremy5 (Jeremy)]

@lander

But Rhino is so bad at dealing with edges

Hi Lander,

To be honest, I don’t understand, so could you explain. What do you mean? Can you back that assertion up with evidence that can be used to make things better?

Regards
Jeremy

[lander (CAD CAM CNC)]

@jeremy5

I don’t understand, so could you explain. What do you mean? Can you back that assertion up with evidence that can be used to make things better?

Filleting Tangent Surfaces

For those Rhino users who use the FilletSrf command and would like the process to be a little less tedious here is a Python script that will make strings of fillets that expands FilletSrf capability when filleting tangent surfaces: FilsrfEX.py (40.1 KB) This script works the same as the filletsrf command - just pick 2 surfaces that you want to connect by a fillet. The difference is the script will continue to make all the tangent fillets connected to the first fillet until it runs out of tangen…

Jim proved it. And through studying the many things that he’s said, I’ve realized he’s 100% correct about ‘fillet edge’ being the wrong approach.

I’m not sure if my perception of the matter is exactly the same as his, but he helped me realize there’s definitely a problem with ‘constraining’ fillets to be driven by ‘edges’ – especially when Rhino does such a bad job dealing with the edges and leading to failures.

I suppose, if you allow the failure to output something, by turning off the ‘trim’ aspect, then you get something to play with. So, it’s all relative.

Maybe it’s time for another ‘filletedge’ failure review.

[jeremy5 (Jeremy)]

Thanks for expanding. So, if I understand you right, when you say

@lander

But Rhino is so bad at dealing with edges, that it is then terrible at fillets.

you mean just bad in the context of filleting: there isn’t a raft of other types of bad edge behaviour you’re aware of. Because that would be scary.

[lander (CAD CAM CNC)]

@jeremy5

you mean just bad in the context of filleting: there isn’t a raft of other types of bad edge behaviour you’re aware of. Because that would be scary.

My use of the word ‘edge’ in that context was intended exclusively for the ideology behind the command ‘filletedge’ and it’s malfunctions of managing the transformations necessary, to edges, and adjacent edges/faces thereof, in order to succeed in said command of filleting ‘edges’.

Jim has proven, to me, that the ideological constraint of fillets being driven by edges, is a flawed ideology.

I used to be a firm believer in edges being the way to define them, but through much research and studying I’ve changed my mind. Unfortunately, the technology to work around this is still underdeveloped.

Jim’s script shows much promise, but in the meantime there’s still much review to be done overall, in terms of automation and all possible scenarios – not just faces that are ‘tangent’ per say.

[jeremy5 (Jeremy)]

Thanks for clearing that up - you had me worried there for a few moments!