Water responsive material

Hi guys,

Essentially I have created some panels created around a frame, and would like to wrap these panels around the frame somehow (similar to the Chao Chen project http://www.chaochen-design.com/water-reaction-1.html).

The following gh attached below is how I've generated the frame and wood panels. What I need now is to be able to wrap the wood panels around the frame (similar to the photo you see below)

Any help would awesome, and thanks in advance!

Attachments:

Wood panels.png, 2.3 MB
C1 Individual Panel II- annotated (2).gh, 14 KB

Replies to This Discussion

Permalink Reply by peter fotiadis on May 15, 2016 at 5:03am

Very easy - see attached (ONE object: adjust accordingly for many).

That said the holes are NOT properly done this way (since they are "affected" the wrong way by the Morph Method) ... but if the R is small ... who's gonna notice it?

And of course the length of the target curve should match the length of the source curve ... but who's gonna notice it?.

BTW: I can't get the gist of the bend [disabled] morph component: what sort of input requires??.

Anyway I've used the orthodox way (FlowSpaceMorph).

Attachments:

Morphs_Flow_V1.gh, 129 KB

Permalink Reply by Jay on May 15, 2016 at 5:41am

Hi Peter,

Thanks so much! This script works pretty well, however I seem to be having an issue where the I have three separate surfaces that I would like to morph, but the geometry base takes all the panels as one (so it morphs it kind of weirdly). I have managed to get separate base and target curves but just the surface is being a little bit of an issue at the moment. My grasshopper knowledge is a tad limited (my first semester using it), so the only way I can think of doing this is exploding the trees and running your script through each branch individually (probably a crude and messy way to do it. And it wouldn't help if we need to aggregate it later on). I've attached the amended script below.

Thanks!

Jay

Attachments:

Bending-Panel-II.gh, 24 KB

Permalink Reply by peter fotiadis on May 15, 2016 at 12:36pm

Er ... hmm ...

I have the usual good, bad and ugly news:

1. Good: You tell me.

2. Bad: Flow has rather a very bizarre way to think what to do. Additionally it's very slow. Oops, that is.

3. Ugly: Not a single native component is used for the salvation (life sucks).

I hear you: but since you do business with sweep1 and Flow is not used anymore why the def is named "Morphs_Flow_x" ? Good question, can I have the next please?