algorithmic modeling for Rhino
Hi,
I'm trying to panelize a simple surface and to control the points on the surface's grid. I've used the surface division, but instead of getting a 4 point definition for each component i get only 2 ( see the attached image), which, I think, is causing me a problem with connecting the list item, with index numbers from -0-3, since I only get 2 point (o and 1) for each panel. how can i overcome this ??
Please help.
Tags:
The output data structure has changed you will either need to flatten or use the path mapper to collapse the branches of the 'columns' up to the level of 'surface' something like {A;B;C}(i)-->{A;B} where C is the data path of your 'columns' of Points and B is level of different surfaces.
Here is the best explanation for the change of data structures talking about sDivide in particular: http://www.grasshopper3d.com/forum/topics/gh-ver-080001-divide-surf...
Flattening is only suitable for getting all the points of individual surfaces together for multiple surfaces Pathmapper can be used (in your specific case {A;B;C;D;}(i) --> {A;B;C}. But as you are only after the corner points of each sub surface you could use the BRep Explode and get the vertices together in a list for each one.
I've seen a similar problem on someone else's thread recently. The double line coming out of the first list item should be dashed like the other. Can you post this specific example for me to have a look at please.
With regards to the line you are not choosing to draw a line on a surface just a simple line between two points. Otherwise this would be a way of getting them on the surface:
Here you are finding the UV co-ordinates of the corner points for each surface and then supplying those as locations for the interpolated curve on the surface.
I've attached the ghx and the rhino file.
I've noticed the dashed prob' too- you can see in the image below that there's a difference between the data outcome of the 2 upper item components and the lower ones. I 'm not sure how's is it best to fix it.
The last option you suggested works great for creating curves on the surface in one direction, but when i copy the CullN and the CrvSrf and give a different N parameter the curves go nuts....
You have the first two List Items set to cross reference. Change them to Longest List.
For the Culling issue either shift the list along with a shift list component with wrapped set to true before the CullN component or switch to a Cull Pattern Component that you manually set the order of True/False inputs.
Welcome to
Grasshopper
Added by Parametric House 0 Comments 0 Likes
Added by Parametric House 0 Comments 0 Likes
Added by Parametric House 0 Comments 0 Likes
Added by Parametric House 0 Comments 0 Likes
© 2024 Created by Scott Davidson. Powered by