This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
rhino:booleanfaq [2023/11/19] mitch_heynick [Known Rhino limitations] |
rhino:booleanfaq [2023/11/19] (current) mitch_heynick [How surface direction affects Boolean operations] |
||
---|---|---|---|
Line 88: | Line 88: | ||
> **Note:** //If you are doing Boolean operations on closed polysurfaces and they don't react the way you think they should (i.e. the wrong parts disappear), probably one or more of your objects aren't really closed and have the normals pointing inward. | > **Note:** //If you are doing Boolean operations on closed polysurfaces and they don't react the way you think they should (i.e. the wrong parts disappear), probably one or more of your objects aren't really closed and have the normals pointing inward. | ||
- | > **Tip:** //One way to always know which way surfaces are facing is to set up your display to show backfaces in a different color from front faces. | + | > **Tip:** //One way to always know which way surfaces are facing is to set up your display to show backfaces in a different color from front faces. In V5 and onward, the backface color display is set for each different display mode you have. In the Rhino Options |
Let's imagine the simplest open Boolean operation. | Let's imagine the simplest open Boolean operation. | ||
Line 104: | Line 104: | ||
From Rhino V4 on, [[rhino: | From Rhino V4 on, [[rhino: | ||
+ | However, one of the best solutions to this is to use **BooleanSplit** instead of **BooleanDifference**. | ||