Hi, I think there is a problem with the boolean command. I don’t need a copy of the original subtracted copy. In fact, after the boolean command, I have to delete the copied object. I can’t find an option to avoid this issue. Rhino 7 didn’t create a copy of the subtracted object with its origin…

Did you check the command line option to delete input or not?

thanks Mitch, I can see that this allows history related booleans. I was wrong that the V7 behavior was lost, it’s indeed : [image] Helvetosaur: If you choose DeleteInput=Yes and KeepCutters=Yes, it behaves like V7 DeleteInput=Yes, the result of the subtraction remains plus the subtractor(s) is…

[image] Helvetosaur: It may also have to do with trying to support History. That was exactly what I was thinking, when I first saw it… and was sorely disappointed :grimacing: I think the current wording is very confusing for most users, as it uses different nomenclature for the input and the…

[image] Jakob Normand: That was exactly what I was thinking, when I first saw it… and was sorely disappointed :grimacing: here that works, but you will have to keep you input on a separate layer to make it usable I’d say. [image] Jakob Normand: I think the current wording is very confusi…

[image] Gijs de Zwart: Would DeleteInput / DeleteCutters work for you? Works for me - I think it’s more logical that the command asks to delete on both, rather than delete on on and keep on the other :slight_smile: -Jakob

RH-74895 BooleanDifference: confusing wording

[image] Gijs de Zwart: here that works, but you will have to keep you input on a separate layer to make it usable I’d say. Ah! I thought I could get history t work with DeleteInput and KeepCutters, so that could have just the resulting geo and the cutter, but now I see that I have to keep all…

Well, to be honest, the original V7 and earlier wording is confusing - DeleteInput isn’t really what it does, DeleteCutters is actually what it does. So yes, perhaps it does need to be changed, and the “Keep…” prompt is consistent with some other Rhino commands. So it could be simplified as: Keep…

[image] Helvetosaur: So it could be simplified as: KeepBaseObjects=Yes/No and KeepCutters=Yes/No I like that a lot! And this is the kind of work-flow (overly simplified, but in principle) I would love to see streamlined: Combining gumball, push-pull and subobject selection. -Jakob

[image] Helvetosaur: So it could be simplified as: KeepBaseObjects=Yes/No and KeepCutters=Yes/No KeepBaseObjects=No KeepCutters=No would result in the same as DeleteInput=Yes does now in V7 - only the results remain KeepBaseObjects=No KeepCutters=Yes would result in the same as DeleteInput=No …

Hi all, If I understood Thai thread correctly we need to keep both base objects and cutters for Boolean history to work? If that’s the case, and if history is turned on, I hope the default for both is set to Yes (keep). Thx, G

Rhino 8 WIP boolean behaviour

Serengeti (Rhino WIP)

brian (Brian Gillespie) May 24, 2023, 4:40am 22

RH-74895 is fixed in the latest WIP

Topic		Replies	Views
Boolean Difference Creates Copy of Object Issue Serengeti (Rhino WIP) windows	20	2582	December 15, 2023
Bug? Boolean difference keep unwanted original Rhino windows	2	222	January 15, 2024
Boolean, but keep the objects? Rhino for Windows windows	3	309	December 13, 2023
Bug Boolean history? Rhino windows , history , boolean	4	134	June 30, 2025
Boolean Difference works v5 fails v8 why? Rhino for Windows windows	4	242	September 28, 2024

Rhino 8 WIP boolean behaviour

Related topics