generative modeling for Rhino
I'm flirting with the GH option (VS Generative Components) for doing some kind of tower. Shown a core/elevator "draft layout" in very early stages. The tower could be quite complex ...thus Gen Comp is clearly questionable (extremely slow, you'll need a Cray to do it).
Is anyone aware of some kind of script/capability that can create regions by extracting a valid boundary (with holes) out of a collection of existing geometry?
Say, like the "by flood region" method in Microstation:
In this circumstance you want the central portion of the intersected curves, I've used my StructDrawRhino component to achieve this, I'm sure it can be substituted with native GH components. Hope it helps, it's possible your image might be simplified version of what is required and might need some further improvements.
Rhino does provide a mechanism for this (CurveBoolean command) but it is not currently exposed in our SDK in a way that makes it possible for others to use the same function. So for the time being, Jon's component is probably your best way forward.
Thanks for the replies.
Indeed Jon's tool appears to be the way to do it, although a flood region capability on a per Auxiliary Coordinate system (see animated PDF from Microstation - you can navigate manually by stopping the animation and use SView "start") capability could be far more helpful in this case (in fact in 99% of AEC complex cases).
The Curve Boolean tool is odd: at first appears that the region (+ interior "holes") is identified OK but ultimately no Boolean difference is performed between the found region and the interior "holes".
Anyway...I have this as well (no idea who is the author) that can in theory address the "flood" issue (minus autonomous holes) but due to the curve selection fuzzy logic (at least to me) you can't use it in complex profile cases. No idea what to do in order to convert the legacy VB, mind.
Given the opportunity (the conversion puzzle) the way that Gen Comp expose the "SDK" is the best in business (but Gen Comp is ridiculously slow - good only for Academic talking). There's a tremendous handy "interaction" capability from/to Views/Script-Graph editors as well. IMHO a thing worth considering ASAP in GH.