algorithmic modeling for Rhino
Hi to all,
I supose it is answered 100 times already, but I really searched the forum and...! :(
I have this vertical line intersecting loft surface, after any combination of lofting, and makes me a problem later with diagrids and meshing. (I know, buaaaa, still doing honeycombs :)
I tried some things, like curves rebuilding, but without success.
Why is this line there and how the logic of the curves Loft works anyway ?
Appreciate any help!
Thanks
Igor
Tags:
Hello igor,
it happened that i was struggling with this earlier. it is the (interior) edge of the surface.
the above surface was created from multiple circles scaled according to a graph mapper.
when trying to split this surface with some curves, the output is surfaces but also polysurfaces where this edge is (after joining them since they were in two parts instead of one). the workaround, only for symmetrical cases like this, was to check this edge for intersection with all the surfaces, cull the ones that intersect (the polysurfaces due to this edge). then rotated the surface, splitted again, check again for intersections with the initial edge and replace the culled polysurfaces with the new intersected ones of the rotated, which are surfaces.
i hope my description makes sense.
cheers
alex
Hi Alex,
Thank you for reply!
I could try your solution :)
My surface starts also with a graph mapper!
it is the (interior) edge of the surface?
Interesting!
Thanks,
Igor
Igor
Always attach your data if you ask for help. There's a variety of ways to resolve loft issues ... but only with some real thing on hand.
Ouuu of course,
It is a scale with Graph Mapper!
Thank you for your reply Dark Lord!
That's elementary my dear Watson:
Lunchbox does cells as ... full hexagons and as ... portions of hexagons at the surf "limits".
Now at the seam he have the left "portions" and the right "portions" . Since the attractor thingy is in different relative position the offsets are different as well .
The solution is also elementary: you must "join" the "portions" (along the seam) in ONE hex polyline (a "full" hexagon) in order to get what do you want. The fact that Lunchbox doesn't make a tree (Lists in 3d space: what's the meaning of it?) makes things a bit spicy but nothing really difficult to address.
I could do it very easily ... but you know my way (The Dark Side == C#) . Notify if you want such a solution.
best, Lord of Darkness
OK, spend a couple of minutes more on that
1. See joinHalfs option (straight from Hamlet).
2. The offset is available via 3 options.
3. Option 2 is the ugliest method known to mankind (OffsetOnSurface). To celebrate that I've left the related code unfinished > only for the brave:
4.Attractors (push/pull + any number of attractors + some bonus, he he) in the trad V4 update (of the V3 update).
best
Yikes > this path leads to the rabbit hole (many entries no exit). Also has a variety of side effects related with ... er ... spirits (but I've recently replaced Vodka with Tequila for better code quality).
Anyway ... get this attached (I can't remember why I did it > blame Alzheimer. Of course I could bypass Lunchbox completely) AND don't touch anything: spot the situation on the left/right side of that @%$@ seam.
What we need is a few lines of code more in order to get the left things and to "add" them to the right things (Note: "culled" in this particular case: only full hexagons play ball, but why I did that?) > a full hexagon "along" the seam instead of 2 "portions" > blah blah.
The salvation in the trad update (V2, that is).
PS: the pill is the black one (not shown)
Load Rhino file first.
best, Lord of Darkness
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