Retrain downward vertical lines by x-axis

Hello,

The grasshopper attached is a curved surface resembling a building facade, which will be constructed using a space frame. I'm wanting to create columns on the open front and back facade for stability. I'm trying to get the columns to drop down from the curve and stop when they hit the 'floor' x-axis, but I'm not sure how to do this. Also if you see anything else wrong with the grasshopper let me know.

Thanks!

Attachments:

spaceframe.gh, 39 KB

Replies to This Discussion

Permalink Reply by Danny Boyes on March 17, 2016 at 10:13am

As ever there are numerous ways to achieve this but my personal favorite would be this:

P.S. greetings one and all.............

Permalink Reply by Liz on March 17, 2016 at 10:37am

Thank you!!

Permalink Reply by Liz on March 17, 2016 at 10:55am

Would you happen to know how to connect those lines up to the geometry gym functions to create 'I' profile columns?

Permalink Reply by Danny Boyes on March 17, 2016 at 11:02am

Sorry I don't use the plug-in

Permalink Reply by peter fotiadis on March 17, 2016 at 11:34am

Liz

I would strongly suggest a truss (say: MERO type or other) as the primary LBS. See attached.

Attachments:

spaceframe_V1.gh, 41 KB

Permalink Reply by Liz on March 18, 2016 at 4:39am

amazing! thanks, this works much better :)

Permalink Reply by peter fotiadis on March 18, 2016 at 7:25am

Actually that was a very quick first approach. For making first/last (*) W nodes // to the ground (rather required that one) I'll post soon the trad V2 update.

(*) usually providing the truss mount points in real-life.

See a Front (non perspective) view from that upcoming V2 and spot where the inner surface ("hots" the truss W nodes) starts/ends: is // to the ground as is the outer one.

Permalink Reply by peter fotiadis on March 18, 2016 at 7:57am

Here we are:

1. "verbosity" with regard W members is replaced with ...er ... a few lines of something, he he (Rel Items still around but is De-activated).

2. If you have plans to become a pro (some day, he he) on that market segment (trusses and the likes) ... well ... you can't do anything in real-life without code. Too many reasons to list them here (indicative: connectivity Trees, member clash detection, instance definitions, managing solution variations talking to MCAD apps that do the parts in real-life ... blah, blah). If this is just an abstract exercise ... forget all the above.

3. Using a // (to the ground) "inner" surface (the 2 edges, that is) is tricky because without code you can't be sure where the whole procedure failed (a red component means nothing).

4. The weird big "component" provides ways to do things with surfaces (most notably: rebuild) that are not available as native components. Rebuild is critical when dividing surfaces

have fun, best, Lord of Darkness

Attachments: