Why CAD math is broken article

i really learned a lot from István Csanády about the reasons why CAD programs refuse to perform what appears to be a straightforward forward task.

What I would like to know is whether there is a preferred workflow that helps avoid invoking edge cases that haven’t been implemented?

I use Shapr3D for both designs that will be manufactured using a CNC, and also for 3d prints. My 3D printing workflow seems to encourage more iterative designs which mean I frequently have to modify the CAD model. It’s here that I frequently run into the ‘cannot perform xxxx because it will result in broken geometry’ or words to that effect. I’m then faced with having to remove items in the history until I get to a state where the action can be done.

I hear the chant - you need more experience - fair enough but if there is a preferred workflow that avoids falling into the b-rep problem I’d be very happy.

Many thanks in anticipation.

I’m glad that you liked it! Unfortunately it’s completely unpredictable :frowning:

That follows, I certainly haven’t detected any pattern :roll_eyes:

Implicit surfaces don’t suffer from this, but they also need to be meshed with ray marching. I’m not sure of the level of individual edge control either. Let’s see where ntop is heading, but it seems that simulation is their game right now.