example
2 Likes
Mesh Booleans have improved a lot in Rhino 8. We want to see situations that do not work. We always are working on them when we can.
There are many SDK calls into various intersection routines, booleans and trims. Performance and accuracy can be different depending on which one is used because they have different purposes.
3 Likes
Great to see improvements in boolean ops.
I just did a quick test in Grasshopper and it doesn’t look like this was added there yet. Did I miss anything? (When) Will this be added in Grasshopper?
Hi Bernd -
Please add a .gh file that we can look at…
-wim
Here you go:
boolean_test.gh (10.2 KB)
This was mainly to test performance differences between R8 and R9 (i.e. running in parallel).
Hi Bernd -
It looks like I’ll need more hand-holding.
I’ve only added the panel to the output of the Boolean operation:
What am I missing?
-wim
Right, sorry. This was a quick test to try this:
The intersection process has been made to run in parallel
Booleans between objects with many intersecting faces should feel snappier.
I was just curious about improvements in speed so far. I will likely to more in depth test as well.
I haven’t had time to dig through files that failed in the past.
It’s great that “Boolean” has been “History enabled” since Rhino8!
I suggest that “Delete Input” is disabled by default when “Record History” is enabled.
And then the “Input Geometry” should be displayed automatically as a “Wireframe Mode”.
that would greatly improve the interaction.
1 Like