SplitAnn.zip (826.3 KB)
On the left, 1089 boxes (closed polysurfaces) and a circle. On the right, 1089 squares (curves) and a circle.
Call Split and select first the squares and then the corresponding circle.
Instantly you get the message “76 curves split into 156 pieces.”
Do the same with the boxes and their corresponding circle.
(be prepared to wait… takes over a minute here)
The command line is filled with the following messages:
Split failed.
Splitting… Press Esc to cancel
Split failed.
Splitting… Press Esc to cancel
Split failed.
Splitting… Press Esc to cancel
Split failed.
Splitting… Press Esc to cancel
Splitting… Press Esc to cancel
Splitting… Press Esc to cancel
Splitting… Press Esc to cancel
Splitting… Press Esc to cancel
Splitting… Press Esc to cancel
Splitting… Press Esc to cancel
Splitting… Press Esc to cancel
Splitting… Press Esc to cancel
Splitting… Press Esc to cancel
Split failed.
Splitting… Press Esc to cancel
Split failed.
Splitting… Press Esc to cancel
Split failed.
Splitting… Press Esc to cancel
Split failed.
Splitting… Press Esc to cancel
Split failed.
Splitting… Press Esc to cancel
Split failed.
1089 times…
Finally you get 76 polysurfaces split into 156 pieces.
Obviously it does take longer to calculate splitting the boxes than the squares, but only slightly longer actually. I have a script to do this that runs in Python/RhinoCommon and it accomplishes it in like half a second. So where is all this extra time coming from??
I suspect a good part of the time wasted is this incessant command line reporting, but there is maybe something else going on behind the scenes as well… The intermediate Splitting... / Split failed. command line reporting when splitting breps is totally unnecessary - only the final report is necessary. It could just say Splitting, please wait... while it is processing all.
The intermediate reporting is absent when splitting curves, so at least somebody got it right there.
PLEASE fix this…