Having a problem is extruding/offsetting my grasshopper piece

Hi guys,

I am really new to grasshopper and followed a tutorial to make a vase type structure by using the graph mapper: http://designalyze.com/tutorial/fun-graph-mapper

I really like what it has produced and wanted to 3D print a version, however i am struggling in extruding the surfaces so it can be 3D printed. I've tried doing other tutorials but in using the process, i end up loosing the shape I want.

I hope to get a bit more understanding and advice on what I could do.

Thank you

Attachments:

EM2.gh, 8 KB

Replies to This Discussion

Permalink Reply by peter fotiadis on March 24, 2016 at 7:59am

Hmm ... I have good, bad and ugly news:

Good: Easy ... provided that you know a lot of things (that a novice doesn't). BTW: suggested movie: CATCH 22 (a classic).

Bad: A lot of steps are required in order to exploit/check "proper" result(s) for proceeding to the next step. Not a task for a novice. Note: only one (out of many) is provided in the def attached (for instance: IS the lofted surface suitable for going further? ARE profiles the "good" ones? etc etc).

Ugly: Rhino is incredibly slow with anything that is "solid": for instance the final (disabled) Union thingy that does the one piece object from all the (hopefully properly prepared) others. Like the one captured above, that is

Suggestion: what about some other case? But if you insist > open the attached and "enjoy".

best

Attachments:

EM2_V1.gh, 133 KB

Permalink Reply by Arda Awais on March 24, 2016 at 9:23am

Thank you so much for your help!

Permalink Reply by peter fotiadis on March 24, 2016 at 9:27am

This is slightly(???) smarter and slightly(?) faster (blame the lack of espresso for the V1: instead of recreating (*) the wing N times ... you just rotate a "clone" wing) plus there's some more checks for "solid" bool ops validity (not a given, mind).

(*) But of course this thingy begs for different wings (instead of one rotated - that's why the V1 was written that way) ... which brings us back deep into the "solid" ops response rabbit hole.

Attachments: