Steps to replicate: create two intersecting boxes put the cutting box in a block press “Record History” button perform boolean difference move the cutting box (the one inside the block) What happens: Boolean will stop working What I expected: Boolean will follow the cutting box (the one inside…

Thanks for reporting. I’ve logged https://mcneel.myjetbrains.com/youtrack/issue/RH-72069/History-in-Blocks-stops-working-after-closing-the-block The best workaround for now I see is to work with linked blocks and perform your boolean operations in the original file.

thanks, it would be awesome if history booleans with block instances became possible. It would save us massive amounts of time adjusting windows, doors etc.

I understand. As you can see the other related YT is on the future list, so don’t hold your breath on this one. If the objects you substract from are fairly simple (boxy) then in principle you could also use the SolidEditing tools for your task. Since I assume you tried that, are there reasons not t…

No worries, I imagine that if it was simple someone would have done it already. You are right that openings can be adjusted with other methods, but in some situations it may take much longer - for example if openings are inside blocks requiring you to adjust blocks one by one. Sometimes you have mor…

Hi Daniel - [image] Daniel_Krajnik: Steps to replicate: create two intersecting boxes put the cutting box in a block press “Record History” button perform boolean difference move the cutting box (the one inside the block) What happens: Boolean will stop working If I’m reading those step …

[image] Wim Dekeyser: moving the block instance of the cutter will update the polysurface Hi, hmm that’s strange, I’m still experiencing the behaviour Gijs described. Please see the steps recorded here (Rhino 8.0.22347.14305, 2022-12-13): It hopefully shows that once the second box (cutter) …

[image] Wim Dekeyser: that’s something different than what Gijs put on the list. Indeed, reading the steps again, I see interpreted it wrong. [image] Wim Dekeyser: moving the block instance of the cutter will update the polysurface. This I cannot seem to reproduce, at least not in the…

wow, thanks, you are right, it does work with polysrufaces :slight_smile: ! I’ve been testing it with extrusions all this time. I think that solves it then? Great news

[image] Daniel_Krajnik: I’ve been testing it with extrusions all this time. What’s an extrusion? :see_no_evil: [image] Daniel_Krajnik: I think that solves it then? I’ll get it on the list. RH-72110 History: Boolean with blocked extrusion is not historic -wim

[image] Wim Dekeyser: RH-72110 History: Boolean with blocked extrusion is not historic Fantastic, thank you! [image] Wim Dekeyser: What’s an extrusion? :see_no_evil: [image]

Record History for a Boolean stops working when object is inside a block

Serengeti (Rhino WIP)

dan (Dan) December 27, 2022, 10:54pm 12

RH-72110 is fixed in the latest WIP.

Topic		Replies	Views
Bug Boolean history? Rhino windows , history , boolean	4	134	June 30, 2025
Lucky find: _BooleanIntersection works with history Bongo windows	5	673	January 14, 2023
Rhino 8 WIP boolean behaviour Serengeti (Rhino WIP) windows , mac	27	2271	May 24, 2023
Editable boolean difference? Rhino for Windows windows , mac	11	384	April 26, 2025
How update boolean result after source objects changed Rhino Developer windows , rhinocommon , rhino7	2	479	March 28, 2022

Record History for a Boolean stops working when object is inside a block

Related topics