Get Points > Do Something.

Well friends

Recently my friend Chap initiated an interesting thread (by providing points AND not a mesh):

http://www.grasshopper3d.com/forum/topics/space-frame-mesh-modelling

I've promised to him to deliver something for his case (still WIP mind): that something does trusses (outlines trusses to be precise since a truss is many things more than a collection of geometry) in 2 modes:

(a) either by using points, (b) or by working on MeshLists.

A lot of chaotic parameters (as usual) are provided in order to make Chap's life easier (actually hell, he he).

A variety of domes is included in the Rhino file.

Also (case: meshes) a fat sardine and that bunny are available if you are bored doing trusses for AEC purposes.

Replies to This Discussion

Permalink Reply by peter fotiadis on May 25, 2015 at 2:12pm

BTW: here's some stuff that you can do (be brave: make a "growing" truss-sardine [as a building] can Zaha do that?)

Attachments:

Death_Star_from_Points_by_The_Lord.wmv, 995 KB
Death_Egg_from_Points_by_The_Lord.wmv, 1.5 MB
Dome_from_Points_by_the_Lord.wmv, 1019 KB

Permalink Reply by Chapuline on May 28, 2015 at 1:24pm

Peter, Thanks so much! I took a look at the file. Seems like there has to be a certain process to follow. Do you have some instructions on these steps?

Chap.

Permalink Reply by peter fotiadis on May 29, 2015 at 1:13am

Skype session today (same hour as the last one).

As I said this thread of yours was the spark for developing something "final" on that pts/mesh > truss thingy.

Here's the vastly improved V3B doing a MERO-KK Systeme via code borrowed from the internal version (V5-Int):

The KK-Systeme C# works by creating parametric seed Breps (sleeve + cone) in Plane.WorldXY and then makes the equivalent instance definitions (V5-Int only) and then puts these ("blocks" in plain English) in a zillion places according suitable PlaneToPlane transformations ... or it just exports coordinate systems for CATIA/NX/AECOSim (this is the way that I work anyway).

Spot the CRITICAL requirement for clash detection (V5-Int only). Clash concerns the tube topology (obvious) AND the connecting bolt topology (not that obvious) as well.

Permalink Reply by Jaime Sànchez on December 8, 2016 at 9:20am

Peter,

I´m terribly sorry for reviving an old thread.

I was running through your 3dm file, and i couldn´t help but notice the overall shape..

were did you get the point info for the first layer in your file? ;), i feel like i´ve seen it somewhere before..(excuse me if this sounds rude by any chance, no harm intended)

I have a feeling that we share something in common haha.

Best regards,

Jaime.

Permalink Reply by peter fotiadis on December 8, 2016 at 9:27am

Hi Jaime,

You are sited in Mexico eh? Other than that ... unfortunately due to advancing Alzheimer I can't remember a thing (or two) on that matter.

Moral: more carrots please.

best

Permalink Reply by zaidoon on February 21, 2017 at 5:43pm