hexagonal grid pattern based on Al Bahar Towers

Hello,

I am a new user and this is the first thing i try to make on my own in GH from scratch (i attached the file). So i tried to recreate Al Bahar Towers pattern but in 2D (so simplified).

After some struggling i managed to get the effect i wanted but i have three problems:

1) i can't really scale these, hexagons were moved in the easiest way, so i have no control over the pattern

2) i feel that i made it pretty messy with all the dispatches, rotations etc - does it make the definition run slow? how could i simplify my definition?

3) most important i have no idea how to transfer it to hexagonal grid (so i can use jpg as attractor) for a bigger pattern. i tried starting from the hexagonal grid but couldn't get it and eventually got lost, but maybe thats the right way?

Pardon my english, hope i will get some help from you, have a good day :)

Attachments:

hex3.gh, 18 KB

Replies to This Discussion

Permalink Reply by nikos tzar on October 3, 2014 at 3:43pm

Hello Wujo,

If you get used to working with data trees you can really simplify your definitions.

You could start from a triangular grid and create the lines you need inside every cell (triangle) of the grid simultaneously.

Here is my approach:

This way you can have parametric values for the number and size of cells as well as for the opening of each cell.

Next step is to add a point attractor which will determine how open each cell is but I'll leave this for you to search and apply to your definition.

feel free to ask any questions about the definition,

cheers,

nikos

Permalink Reply by nikos tzar on October 3, 2014 at 3:43pm

forgot the file:

Attachments:

hex3-nt.gh, 15 KB

Permalink Reply by Wujo on October 3, 2014 at 4:17pm

Nikos,

Thank you very much!

That is very helpful! I briefly looked through your definition and i think i get your approach :). Understanding data trees will be painful (but as far as i know there are good tutorials by digitaltoolbox i need to get into). As i understand reparametrize, graft, flatten and simplify remain tricky for me. I will come back to your definition tomorrow and try to understand as much as i can :). If I had any questions I'll ask them here.

Once again thank you for your time and help!

Have a nice weekend,

Wujo

Permalink Reply by Pieter Segeren on October 5, 2014 at 11:38am

Hi Wujo,
thanks for bringing this shape to my attention, I like it.
I loosely approximated it and thought I'd share. It's not using an image sampler (noticed that just now) but attractor geometry. Still I hope it contributes to your goal :)

Attachments:

Al_Bahar_PSG.gh, 59 KB

Permalink Reply by Wujo on October 5, 2014 at 11:52am

Hi Peter,

thanks for your reply, your results looks really cool, and it's 3d ;). Looking forward to checking out your definition.

Once again, thanks a lot,

Have a good day :)

Permalink Reply by nikos tzar on February 7, 2016 at 1:55pm

Hello Mahya,

I believe something like this should work.

The problem with your definition was about data matching. If you search about this you will find a lot of info about how gh components work when they get more than one inputs.

Hope this helps a bit...

Attachments:

3dhexagongrid.gh, 13 KB

Permalink Reply by nikos tzar on February 7, 2016 at 2:09pm

I am afraid you would need a definition of different logic in order to have these panels on a 3d surface. Have you checked Pieter's definition (above)? I didn't get a chance to look at it but it seems to be closer to what you are after...

Permalink Reply by nikos tzar on February 8, 2016 at 4:33am

Hello Mahya,

Sorry for the delay (time difference...)

Although the logical steps you are describing seem... ...logical, this is not the way grasshopper works.

You can't (always) take a definition that is coded for one object and apply it to many objects, or take a definition that is designed for 2d and apply it to 3d.

I put together a simplified version of Pieter's definition for applying these triangular panels on a surface.(you need to install lunchbox plugin)

Please compare this to the previous definition I posted to locate the differences (from 2d to 3d).

Note all these "graft", "simplify" and "flatten" operations on some components inputs. These are crucial in order to achieve proper data matching between components and avoid these mixed lines connections you are referring to.

I am afraid you can't really advance in GH without a good understanding of data matching (items, lists of items, lists of lists of items...) and it cannot possibly be explained in a single post (there are many tutorials about this, just make sure you don't read a really old one, since many things have changed in GH).

Hopes this helps to get you started,

best,

Nikos

Attachments:

Al_Bahar_3d.gh, 14 KB

Permalink Reply by Ethan on February 23, 2016 at 10:20pm

@Pieter Segeren, I happen to work with the author of the Al Bahr Towers, and want you to know he very much enjoyed this image :)

Permalink Reply by Pieter Segeren on February 24, 2016 at 2:17am

Hi Ethan,
how very nice of you to inform me, thanks. Happy to hear that.
Who at Aedas Architects actually designed it then? Please give him/her my regards.

RSS