Good Morning Gentlemen
Did anyone experience this behaviour with the Springs node FilledRegion.ByCurves+ & OOTB node FilledRegion.ByCurves…Maybe I am missing out on a very easy silly mistake which one of you might spot out instantly; however, small or big, I would appreciate any tip which points me to the right direction
What I am doing is creating filled regions based on the footprint of the rooms in the model. Rooms are categorized by department where each department is represented by a different filled region type. Steps I followed are pretty much simple
- Filtering rooms of a specific department
- Using Room.Faces node to extract bottom surface/footprint
- Getting the parameter curves using Surface.ParameterCurves node
- Filtering unique curves to to clean overlapping/duplicate boundaries
- Making sure all curves are closed loops
- Feeding the list of curves into the node FilledRegion.ByCurves+
The odd behavior I am Facing is the following:
A. For some room lists (ex: Rooms of Department X) the node FilledRegion.ByCurves+ from Springs Package works perfectly fine and as intended (image 1)…
B. For some other random room list (ex: Rooms of Department Y), irrespective of the lacing used, the output using the node from Springs Package remains NULL. However, if I extract the sublist of curve loops at each index one at a time, the node FilledRegion.ByCurves+ generates the region just fine for one sublist at a time.
C. Using the OOTB Node FilledRegion.ByCurves for either of the above would be a no go. The ootb node would generate the filled regions for all indices in the combined list but not as a single region (ie: multiple filled regions) and in the event any of these regions is supposed to have a donut shape which is practically every room which has a column in it. In comparison with the springs node which cuts out the inside loops (preferable behavior)