Wrap closed surface hex tessellation

Hi guys! im having a bit of a problem with my GH definition im using a hexgrid mapped over a surface. However every time i run it over a closed surface i cant get it to overlap the last and the first column of hexagons and im getting this:

Im trying to get it all wraped up . I'd really appreciate if someone could help me out. Here im posting the core of the definition:

Replies to This Discussion

Permalink Reply by peter fotiadis on June 22, 2015 at 1:50pm

Try this attached (load Rhino file first AND watch CLOSELY what the C# info panel has to say).

Attachments:

hex-on-surface_V3.gh, 342 KB
hex-on-surface_V3.3dm, 461 KB

Permalink Reply by ovizoso on June 22, 2015 at 3:19pm

Im actually new at this. i dont have any experience on scripting. Isn't there a way to simply tell grasshopper to overlap the last two points over the surface? i think that would close the gap.

Permalink Reply by johnnyUtah05 on June 22, 2015 at 2:53pm

Did you try Lunchbox's surface Hex component for this?

Here is a simple definition that is what I think you are trying to accomplish using attractor curve.

Permalink Reply by ovizoso on June 22, 2015 at 3:12pm

i tried with lunchbox but i still get the same result.

Permalink Reply by ovizoso on June 22, 2015 at 3:46pm

here's my current definition so you can get an idea of what im trying to get done.

Thanks in advance!

Attachments:

hexapanel.gh, 37 KB

Permalink Reply by johnnyUtah05 on June 22, 2015 at 4:58pm

Alright I see now. Lunchbox works, but only if you have the right ratio of your input x and y sliders and if you can deal with the vertical line unless you want to cull them out and redraw your polylines (a painful process).

In this application I would just draw the Hex Cells into isotrimmed surface edges. Very simple hack. See below. No vertical lines. If you want top and bottom circles, just pipe the input curves.

Permalink Reply by johnnyUtah05 on June 23, 2015 at 7:48pm

Ok so after checking your definition, I realize that wrapping a periodic surface like your cylinder will return the seam of the surface. It would be possible to cull this out, but is a pain.

I suggest to save your time, use Peter's definition, which finds these half hexagons and joins them automatically. Using his definition as the input for your definition will definitely work as far as I am concerned.

I am also interested if anyone out there knows how to get rid of a surface seam on a periodic surface without C# though.

Permalink Reply by peter fotiadis on June 23, 2015 at 11:07pm

I could translate the right thing (the Dark Side) to the wrong thing (the Other Side, he he) ... but is not a very pleasant task.

Permalink Reply by johnnyUtah05 on June 23, 2015 at 11:34pm

Here is one option I worked out. I am guessing there is a much simpler option...

Permalink Reply by Jesse Kilp on December 10, 2017 at 10:15pm

Hi, any chance you could repost this image with the full names of the components visible, rather than the symbols?

Permalink Reply by peter fotiadis on June 24, 2015 at 12:35am

Well Erik ...

...in case that some day you decide to cross the Rubicon (one way ticket that one) get this and have fun.

BTW: dividing any collection of surfaces with any pattern imaginable (and then do whatever thing you like) is very easy (via the Dark Side).

BTW: spot the 2 modes: design ... and apply

best, Lord of Darkness

Attachments:

surface-subdive-with-patterns_V2.gh, 629 KB
surface-subdive-with-patterns_V2.3dm, 196 KB

Permalink Reply by johnnyUtah05 on June 24, 2015 at 3:33am

Peter,

Thank you for sharing this robust code. It can do quite a lot. Much appreciated!

BTW, when you speak of the dark side, I assume you refer to C#; however, I wonder where python sits in this regard. Since you speak only of galactic power, Python must be one step above on the level of dark matter/energy.