CurveBoolean takes a long time, or freezes Rhino

Rhino Rhino for Windows
,
1

Hey guys, new here. I had to create a custom design for one of my machinists, and for some reason it takes forever when I try to use CurveBoolean, I think it may be because it has so many curve segments, but I haven’t been able to find anything saying how to resolve this. It also happens whenever I have a somewhat complex design for a logo, I also have a pretty large file that I have been trying to clean up, and it gets pretty laggy, I have tried putting things on other layers but it doesn’t seem to help.

2

Hello- please post the file or send to tech@mcneel.com, with a link back here in your comments.

-Pascal

3

Terry Custom Pattern.3dm (18.3 MB)

Here is the file, sorry for that.

4

Hello- there are no overlapping curves in the file - what is the goal, for CurveBoolean ? I don’t see what it can do here.

-Pascal

5

All of those curves are already closed regions who do not intersect, what are you trying to do with them ?

6

They will be placed onto various pieces to then use curveboolean and trim them accordingly, but my concern is that it takes so long to register curveboolean with 0 intersections, that it will be near impossible to then put it on 15-20 pieces in any reasonable amount of time

7

Hi -

I’m not sure what that means. Perhaps you can post all relevant geometry?
-wim

8

Here is the file again, updated with “pieces” and an example of what it would look like when done. As well as other similar designs that work almost instantly at the same size.
Terry Custom Pattern.3dm (2.5 MB)

9

Hello - Here, with this file, CurveBoolean seems fine (not obnoxiuosly slow)with all of these (using a perimeter curve like the one in the done example) . I do see the very slow perfomrance with the previous version though,even with only enough pattern curves to fill the perimeter… I’ll see if I can figure it out…
Well the lag defintely related to the number of pattern curves selected but the bad ones are somehow different - more complex - they have hundreds of polycurve segments, the ‘easy’ ones have only a few or are polylines. My guess is that is where the difference lies, I’ll ask the developer.

RH-66712 CurveBoolean: Slow preprocess

-Pascal

10

Thank you very much, I appreciate all of your help.