Bending Hexa Grid and Surface Bending Conundrum

[enzyme69]

bend_hexa_error_001_2017_12_11_00_42.zip

Whenever I am using Hexa Grid and wanting to Extrude it, I always got a bit confusion. "Join" seems to fix it when I just simply want to extrude Hexa Grid.

However, Hexa Grid -> Bend Surface -> Extrude Region, once again puzzles me. It does not work. Wonder why?

Why can't "Mesh Join" simply combine Hexa Grid back?

[Durman]

Neha grid node has incorrect output. bend_hexa_error_001.zip

[enzyme69]

Ok, the list del 1,2, - 2,3, 0,3, etc sometimes confuses me :D But thanks!

[DolphinDream]

@Durman why do you say HexaGrid node has wrong output ?

For a non-vectorized input the output of the node is (e.g. for rectangular type Nx=2, Ny=1, or any layout type that has more than one tile):

v = (x,y,z)

tile1 = [v1, ..., v6]  
tile2 = [v1, ..., v6] 

and the combined tiles (not joined):

[tile1, tile2] -> [ [v1, ..., v6], [v1, ..., v6] ] 

while for vectorized input (e.g. input Nx = [1,2]) there are two grids, each one with its own set of tiles:

grid1: 1x1

[tile1] -> [ [v1, ..., v6] ]

grid2: 2x1

[tile1, tile2] -> [ [v1, ..., v6], [v1, ..., v6] ] 

and the combined output including both grids:

[grid1, grid2] = [ [tile1], [tile1, tile2] ] ->

[ [[v1, ..., v6]],  [[v1, ..., v6], [v1, ..., v6]] ]

[enzyme69]

Maybe “wrong” in term of what required for that particular node? But cheers for this explanation! It helps also.

After years using Sverchok, seems like I still have to understand the levels of Vectorization. Matryoshka is a mystery. --

---

• Jimmy Gunawan http://blendersushi.blogspot.com.au http://mayaspiral.blogspot.com.au http://houdoodles.blogspot.com.au http://puppetar.blogspot.com.au

[Durman]

@DolphinDream Sorry, I supposed that structure of data from picture below is single true but maybe i am mistaken because I know for example UV connection node supports 3 level nested lists. Eitherway if press on join button data will be correct.

[DolphinDream]

@Durman Yeah. I see where the confusion may come from. The join option groups together the tiles of each grid into one VEP list, which is more in line with other nodes output.

[nortikin]

@DolphinDream in such cases optimal to use separate flag to make controllable behaviour hexa grid has join flag, but to be clear i propose vice versa - separate flag.

[DolphinDream]

@nortikin I agree. That probably makes more sense. It’s an easy change. What would be the best way to do this ? Do I need to create a new node MK1 ? or can I just change the default behavior ? Also, if I replace join with separate.. should the default be separate ON or OFF ?

[nortikin]

default always off. separate appears in insertion of node, so make mk1... sadly yes.