Surface from boolean, union, join, split curves without getting (crazy|mad|sad|nuts)?

I have a bunch of lines, 8 from exploded rectangles and 4 curves. When I manually split and join those in Rhino I very easily get what I want: A (more or less) beautiful surface.

What would I have to do in Grasshopper to get the same surface from these curves?

Replies to This Discussion

Permalink Reply by peter fotiadis on February 20, 2016 at 3:05am

Just spotted that one:

achievable but only via code (C# for me). Shown 2 out of 3 options available (Tree of curves per "island", regions per "island", union region).

Permalink Reply by Pieter Segeren on February 20, 2016 at 4:01am

Hi Marcus,
I think maybe you want to try the workaround I showed Roberto over here (note: it's slow) :
I changed a little to make it work for your situation:
If anybody knows a cleaner/quicker way, I would also like to know it!
(edit: oops I hid the CullPattern and BoundarySurface component under the viewport frame...)

Attachments:

BoolWA_PSG.gh, 16 KB

Permalink Reply by peter fotiadis on February 20, 2016 at 4:41am

Smart stuff that one. Changed some minor things (as an alternative).

Attachments:

BoolWA_PSG_V1.gh, 15 KB

Permalink Reply by Pieter Segeren on February 20, 2016 at 5:02am

Thanks Peter, but your added Area and Solid(!)Difference component made it even slower...

Permalink Reply by peter fotiadis on February 20, 2016 at 5:40am

Well ... that's exactly the definition of progress: do stuff so slow that forces you to buy another workstation with 666 (min) cores ... that due to the recent O/S upgrade is ... er... a tortoise actually > play it again Sam.

he, he

Permalink Reply by peter fotiadis on February 20, 2016 at 6:42am

Added the ultimate challenge for the very brave.

Handle with extreme care (indeed it's a "bit" slow).

C# beats spaghetti by a huge margin (but that's expected): time shown is the total time required (including the Brep.CreatePlanarBreps thingy).

HOWEVER: Pieter's approach is so smart (and simple) that justifies the delay.

Moral: Not the fastest bunny is the best bunny.

Attachments:

BoolWA_PSG_V1_for_the_VERY_brave.gh, 19 KB

Permalink Reply by Pieter Segeren on February 20, 2016 at 5:24am

The first JoinCurves component turns out to be superfluous (the one leading to the SurfaceSplit C input), you can remove that. Not much speed gained by that, but it's a tiny bit cleaner.

Permalink Reply by Yoann Mescam (Systemiq) on May 19, 2016 at 9:11am