algorithmic modeling for Rhino

normal projection

making an installation for an existing building that is a series of modules with 2 sided pyramids projected from the normal of a surface, however every second panel is intersecting overlaping. this is not what is supposed to happen. not sure what's wrong with the definition.

this may sound a little confusing but ive attached the ghx and 3dm files to have a look at
any help will be much appreciated

Attachments:

Skin.3dm, 15.1 MB
skins.ghx, 367 KB

Replies to This Discussion

Permalink Reply by Danny Boyes on September 22, 2010 at 3:04am

Hi Megan,

In most cases, problems like these come to light due to poor data matching. If you look at the inputs to your srf4pt components you will see that input A has 1250 items where as B and C only have 625. Therefore GH is making 1250 by doubling the short fall inputs.

The root of this problem stems from the Surface Divide component. The output of which is in 'Columns' of points rather than all points for each surface. So instead of getting 4 corner points your getting 2 sets of 2 corner points that share the same U (or V, I can't remember).
You can manage this with the Path Mapper component to reduce the output to give all 4 points in one data branch. In this case {A;B;C;D;E}(i) --> {A;B;C}