Does rhino 8 have an option to create a boolean difference cut out in an object and then modify it later if needed, or toggle it on off as needed. It should be locked to the object even if that object is moved or altered. Im attaching how blender handles this as an example (showing how it’s applied, modified, and that the main receiving object holds the boolean position even when moved/rotated). This would be very very useful in rhino if it does not exist.
1 Like
Hi Peter -
Yes, in Rhino 8 Booleans are history-aware. You need to enable history before the operation and set the options to save the inputs. You’ll then need to keep those inputs in a safe place.
-wim
Thanks Wim. Can I still modify the object to which the boolean is applied without messing with the history? Thanks
Hi Peter -
No, as always with history in Rhino, modifying the children will break history.
-wim
hmm interesting thought, in a boolean operation both parts are actually parent by logic, it might make sense if possible at all to enable history update of both?
In a BooleanDifference in Rhino 8, there are two (groups of) parents: the object(s) to be Booleaned, and the cutter(s). There is one child. You can modify either one of the parents.
-wim
well it is possible in other apps as stated above, and it is pretty convenient, even edge manipulation and anything else is possible, though here this example below in c4d is mesh based i assume the same should be possible for nurbs and SubD either.
maybe that was wished already? i have the feeling i requested that myself a long time ago, it certainly would make sense.
1 Like
What you show in that video is possible in Rhino.
Apart from that, workflows with voxels and implicits have been made available and will likely continue to be further developed.
-wim
No it’s not. Boolean Difference with history only allows you to move one object - moving the other breaks history (they move both objects in that video). Unless you’ve done this some other way.
Edit: Sorry - I see you need to select the correct geometry as the Boolean creates another instance.
It doesn’t create another instance. It creates a new child object that is dependent on both parent input objects.
-wim
But if the red box is modified at all, then it breaks the history correct? Also, appears that the boolean does not hold its position to the box when the red box is moved.
That’s correct, yes.
That is a modification of the child and breaks history, yes. You need to move the parents.
-wim