Hi everyone,
I wanted to report a bug on the CurveBoolean command.
I am attaching screenshots and the file in question. As you can see, the command does not return the promised curves and which one expects to have.
I just updated rhino Version 7 SR32
(7.32.23191.11001, 2023-07-10). I don’t know if it’s a bug in this latest version, but so far the command has always done its job.
Your tolerance is set way to high, make it less precise and you’ll get the result you want. IDK why this is an issue.
Thanks, it works!
The strange thing is that I have always worked like this for years without ever running into bugs like this.
It certainly seems like this should work without needing to change your file tolerance.
If you explode the curves before running _CurveBoolean it works with the tolerance set in your file (0.001).
If you explode the curves you are trying to boolean and then use the _SelDupAll command, it will select the segments that divide the regions you’re trying to combine.
This shouldn’t work if the curves were out of tolerance (if you examine these segments, they look identical other than being reversed in direction).
At this point, you can delete the duplicates and then re-join the other curves to get the same region you would get from _CurveBoolean (perhaps with _SimplifyCrv to eliminate unnecessary control points).
_CurveBoolean also works if you first use _FitCrv (Degree=3, Tolerance=0.001).
I’d be curious to know why _CurveBoolean doesn’t work when you just select the curves in your file, it seems like a bug to me.
-Kevin
These curves as input to _CurveBoolean
(from the file posted by @Federico_Scarlatti)
Produce this result
curve_boolean_fail_230716.3dm (39.7 KB)
-Kevin
Hello - as far as I can see this works as expected in V8. @Federico_Scarlatti - does your file work in the V8 WIP?
-Pascal
Hi Pascal, I tried on rhino 8 and it works fine, instead on rhino 7 just updated today Version 7 SR32
(7.32.23199.7001, 2023-07-18) still produces the curves I’ve shown.
