Boolean intersection result 0/20


As a former HS math teacher, I often want to give Rhino very bad grades… What am i doing wrong?
Here are two Simple bent piece of material. I want to develop them into a flat surface To be able to have then wirecut… In blue are the parts.

I drew an extrusion that follow the 1/2 thickness profile to find the median plane( in Black.
So mathematically from my 5th grade math class, what I am looking for is the intersection of the blue part with the black extrusion. As result I am expecting a surface that has the contour of the blue part… Well not according to Rhino.
FIrst Part what I selected:

the result:

Since when the intersection of a volume with a surface is a volume? 0/10
Now for the second set:
First and second surfaces selected:


Another solid 0/20…
OK I can now explode the resulting object and keep the faces I need but why the extra work…

(Nathan 'jesterKing' Letwory) #2

You’ll find that users on this forum will give great advice when you also include your model - please attach it to this thread. Otherwise it’ll be guessing…


The intersection of your blue polysurface and the black surface would be a curve in Rhino. The Rhino Intersect command is different than the Rhino BooleanIntersection command which is what you apparently used.

I believe the Rhino command that you want to use is called 'Trim"

To get what you want use the blue polysurface to trim the black surface or trim the black surface using the curve that the intersect command will create as the cutting object.


You are very correct and Here is the model.HVP-2B NegBar.3dm (104.7 KB)

Yes you are correct, Since Rhino does not really deal with solid, MAthematically the intersection would be a set of curves with the profile of the blue part. The intersec function. I did not know that function. Thanks

I did not think of using the Trim function. Thanks for the advice it is a very elegant solution.

Yes I used the Booleanintersection. I still do not understand the difference between intersec and Boolean intersection. Both should give me the same result.

(Pascal Golay) #5

Hi Jean-Marc- Intersect returns the curves and points of intersection among the inputs, it does not do anything to the inputs themselves.



Thanks Pascal,
Yes it does and I see now. But still do not understand the behavior of the Booleanintersection in my case.

On a slightly different subject on the same model, Once I get my surface, I cannot find the center of the holes. When I duplicate the edge I get a curve made of millions of points instead of a circle. Any way to rebuild the edge to have it simplified as a circle?

(Pascal Golay) #7

Hi Jean-Marc - if the hole is on a planar surface and close enough to a circle, DupEdge and SimplifyCrv may get you the circle.



Two commands that do the same thing would be rather pointless.

To understand BooleanIntersection you should perhaps review the logic of Venn diagrams from your high school math.


Yes it does but then that edge is not part of the surface. Can then substitute the"Dirty" edge for the new one?

(Pascal Golay) #10

Hi Jean-marc - try UntrimHoles and then retrim with the clean circle - if it is a solid, you can extrude the circle through, and use BooleanDifference. You could try ReplaceEdge, it might work if it is only a trim in a surface - I’ve never tried it on a hole but no reason why not. Hm- no, it does not work in my test.



Thanks Pascal.