Wow! Of course, that Parallel.For() loop helps too, eh? Two of them!
The Nurbs curves look very weird though, better to use the DeBrep ‘E’ (Edges). Or PLine (Polyline) with inverted ‘C’ (Closed) input.
P.S. This ‘out worldXY_bbox’ is interesting too?
BoundingBox pln_bbox = crv[i].GetBoundingBox(planes[j], out worldXY_bbox);
As we discussed in PMs, that returns actual box geometry, though the distinction is still fuzzy for me.
Yeah, it is still not fully clear to me too…
It feels like a BoundingBox object is only a domain/interval triplet, even its vertexes are coordinates relative to the used plane.
Instead, the Box object is an actual geometry, oriented and placed in space.
Can anyone light things up?
Thanks a lot for yet another solution to the problem.
I used this on my original work file to check on the speed and the C# script reports 5.1s for 339 elements. This might just my computer or the fact that I am running multiple times the script:
339 elements = 5.1s
45 elements = 862 ms
52 elements = 438 ms
67 elements = 611 ms
Meanwhile @maje90 C# Script v5 runs at 342 ms for 339 elements. Well he basically got rid of the 594 ms used to transform all curves into surfaces.
Once I am done with all this I am so going to explore the software way more.