Hi,
remembering some problems about surface booleans I’ve decided to run a simple test reporting here.
It would be good to put in also MergeAllFaces option.
Thanks!
I noticed for example that for the BooleanDifference, you need to select surfaces or polysurfaces to subtract from then enter to confirm (if you choose wrong you can not return back so what’s the point of confirmation?) then surfaces or polysurfaces to subtract with, and enter to confirm. Could all this operation be shorter for that first enter and give us some preview of the result like for CurveBoolean? Maybe even shorter just two clicks for whole operation with the possibility of returning a step back if you make a mistake without exiting the command?
Thanks!
Since you are choosing two groups of objects, you need an Enter to say you are done choosing the first group… Before you hit that enter you can still edit the selection with the usual shift/control plus selection methods.
If you are only doing two single objects, Boolean2Objects will work like this sorta… you can cycle through the possibilities and choose the one you want. But not on two groups of objects.
–Mitch
I wouldn’t expect Boolean operations on single overlapping coplanar surfaces to work 100% correctly - they are really designed for overlapping volumes where the intersection is one or more unique closed curve loops…
–Mitch
Hi Helvetosaur, Boolean2Objects - too many clicks for me for BooleanDifference, could be shorter.[quote=“Helvetosaur, post:3, topic:1520”]
Since you are choosing two groups of objects, you need an Enter to say you are done choosing the first group
[/quote]
You’re right here, though the first group you could select using Shift. Preview would be good especially for the beginners.
Well, it should, when you hit command you need to select surfaces or polysurfaces so it should work on both.
Cheers!
Many things could work in this direction:
Hello Violine (are you Italian?) FormZ has the best tools to do boolean operations (some say the experts, not me).
There is time to improve, we will see in Rhino 6!
Hi Davide, (I’m not Italian), yes, there is time to improve and hopefully for V6 many things will be solved.