Hi Evan, please note that the extraction point for IsoCurves needs to be supplied in UV coordinates. By the looks of your definition you're feeding in Curve Division points directly, which are specified in XYZ coordinates.
This is why the isocurves shift when you move the surface in world space (because the edges move along with the surface and so do the division points). Also note that you can extract isocurves BEYOND the edge of most surfaces. Especially well defined surfaces such as revolutions, spheres and planes will give you very predictable isocurves outside of the surface domain. You need to project your division points onto the surface in order to convert XYZ points into UV points. You can do so with the "Surface CP" component. -- David Rutten [email protected] Robert McNeel & Associates On Feb 26, 5:21 pm, evanc <[email protected]> wrote: > Okay, the component makes a little more sense now. > > I'm having a similar problem as Dana - the isocurve component is not > drawing curve on the surface, but their placement changes depending on > where the input surface is located. > > here i've done a quick test, with a surface placed at the > orgin:http://www.flickr.com/photos/evandagan/3311947410/sizes/l/ > > and moved off to the > side:http://www.flickr.com/photos/evandagan/3311947450/sizes/l/ > > i hope it's clear from the images, if not i can upload my def.... > > maybe this is a good place for a suggestion for the next release - i'm > trying to get a grid of points on the surface so that the spacing is > even (ie a 'divide curve by length' extended into 2D) ... if the > isocurve component wasn't doing this (above) it would work... i would > place points at the intersection of each UV curve, as defined by the > division of the two edges.... this would be different than, say, > generating surface frames, which doesnt keep an even distance between > points.... does that make sense? > > -evan > > On Feb 26, 10:23 am, David Rutten <[email protected]> wrote: > > > Hi Dana, > > > If I make a very simple test (Project a point onto a surface, feed the > > resulting uv coordinate into the IsoCurve component), it works fine. > > > I'll need to see your model in order to make a useful comment. It is > > possible that there is a bug in Grasshopper which only surfaces (if > > you'll forgive the pun) after a specific set of operations. > > > -- > > David Rutten > > [email protected] > > Robert McNeel & Associates > > > On Feb 26, 2:40 pm, dana <[email protected]> wrote: > > > > Hi All, > > > I have a problem with extracting u and v isocurves as well. When I > > > input multiple points on the surface this components gives me strange > > > curves somewhere in x,y,z coordinate space, but no actual isocurves on > > > the surface. What am I doing wrong? > > > dana
