The GH results are not wrong. Planes have a specific way of determining their intersection which deals with the orientation of the two planes and the order by which they are intersected. Since there is no geometry behind a plane it must be solved in this manner. Typically, when dealing with plane plane intersections, you're just looking at the intersection almost as a vector not as a physical representation of where that intersection lies. This is mainly because the intersection between two planes extends infinitely in both directions.
I would suggest either A) translating the "raw" plane plane intersection into something thats more useful within your definition by scaling or moving the end points of the intersection or B) making planes that represent the intersection that you're looking for much as the first part of your example. -Damien On Jan 19, 8:44 am, "digitag&" <[email protected]> wrote: > We have a problem. > We are trying to make a tassellation of a surface and we have to > define the edge for tassellation with a 2 planes intersection..... but > the results are wrong. Baking the planes and making the intersections > in rhino is ok but the GH results are wrong. > I put the image and the GH definition > example.http://groups.google.com/group/grasshopper3d/web/planes%20intersectio...http://groups.google.com/group/grasshopper3d/web/Planes%20intersectio... > > As you can see on the image the intersection lines (with pipe) are too > little and in some cases are in wrong positions.
