truss/grid/scaffold system from topography/landscape/mountain/contours

I am reasonably new to grasshopper and want to make a 3 dimensional truss/grid/scaffold system from topography.

I am able to make a 3 dimensional grid system quite easily, but am struggling to map it to my landscape/mountain/contours

Attached are images of an example.

Any help or push i the right direction would be greatly appreciated

Attachments:

CFVH_Second_Community_03.jpg, 1.4 MB
CFVH_Second_Community_04 (1).jpg, 1.9 MB

Replies to This Discussion

Permalink Reply by peter fotiadis on May 22, 2015 at 4:49am

Fix What? Where? Why? When? ...

I'm kidding: has to do with the location of your breps (near-by Alpha Centaur +/- some parsecs).

See attached - added your terrains (load R file first). But have these ultra "thick" collections of mini trusses any meaning? (Suggestion: play with the skin mode).

Attachments:

TRUSS_VOLUME_VOXELS_V3A.gh, 367 KB
TRUSS_VOLUME_VOXELS_V3A.3dm, 2.1 MB

Permalink Reply by Thomas Linschoten on May 22, 2015 at 8:19pm

if by the skin mode you mean switch from mini bboxes to stupid truss system then yes i have.

at the moment the mesh is still not working. i think it may have to do with this error which i am struggling to fix at the moment (attached)

yes they are deliberate, but will not appear thick behind a blank canvas due to light. it is in theory a shelf system in a mountain

Attachments:

piker.jpg, 394 KB

Permalink Reply by peter fotiadis on May 23, 2015 at 12:34am

Skin mode OFF (using your small terrain) - meaning BBoxes sampled on a per "volume contains this or that" basis:

Skin mode ON (OBVIOUSLY highly sensitive to BBox "resolution") - meaning BBoxes "touching" the "skin" of the brep/mesh used :

Plankton mesh (MeshMachine speaks the planktonian language > latest Rhino SR + latest GH + plankton.dll (search forum for that one)):

What do you mean by thickness? Maybe going from struts as lines to struts as MERO components (and nodes as balls?) If yes and due to the vast amount of these @$#@$# mini trusses ... the pro solution is to define some instance definitions (blocks in plain English) and then put them (kinda the way that the GH orient component works: planeToPlane transformations) in a zillion places: it's very easy (ONLY with code that one, mind) but it could be utterly cryptic to you if you are not familiar with these mysterious C# matters.

If you insist, I could make a small demo - but be warned: this IS NOT an easy-busy thing for a newcomer.

And what could be the result? 1M mini trusses consisting from 1Z blocks so small that even Sherlock Holmes couldn't distinguish/spot/find them?

Permalink Reply by Thomas Linschoten on May 22, 2015 at 8:20pm

i suppose the next step would be to add a thickness to the truss system but that would be as easy as piping the curves?

Permalink Reply by peter fotiadis on May 23, 2015 at 5:48am

BTW: this means that we depart from make lines working with the 8Box corners on a per BBox basis (== overlaps in edges == therefor stupid) to some proper strut data structure as we do in real-life Easily doable but - again - only with code as far I'm concerned.

Permalink Reply by Thomas Linschoten on May 31, 2015 at 4:59am

how hard would it be to attach the voxel/truss to a line as apposed to a brep?

Permalink Reply by Thomas Linschoten on May 22, 2015 at 10:44pm

'1. Data conversion failed from Goo to Mesh'