algorithmic modeling for Rhino

unit z aligned panel system

Hi,

I am trying to create a panel system on a skyscraper with an attractor point to increase open space on specific areas with an attractor point. I have gotten the definition to work with a single panel but the definition fails when adding multiple curves. The definition is very messy and therefore quite slow. I was wondering how I should go about fixing the issue so that I can use the one definition for all of the panels and still have them oriented to 90 degrees.

tl:dr

the Rhino file is too large to attach. Any trianle curve on different axis should ideally work.

Attachments:

viewskin.gh, 48 KB

Replies to This Discussion

Permalink Reply by Samuel Siegel on December 3, 2015 at 11:52am

update. I have also realized that by clustering components with the intention of making them easier to share I have made it more difficult to work with the definition. From my research it would look like there is no way to explode or undo this operation. What is the best practice for reverting back to the ungrouped definition? should I copy it out and reconnect?

RSS