isocurve lofting issues

Dear all,

I started working on a definition with the latest grasshopper and I found couple of problems which I didn't have before. One of them was the division and selection of a single control point on a surface without "explode" and the other one is the orientation of the U isocurves when lofting. It is ok with the V ones. I'm attaching the samples so everyone can have a look at them. Does anyone have an idea why it happens. I could possibly try to determine a vector direction but what is the point having one of them working and not the other one? Are there problems with the current grasshopper built or this is the way it will be in future?

Can anyone help please? Just not sure why I'm having these issues with the latest grasshopper.

Attachments:

Screen shot 2011-02-08 at 12.24.14.png, 292 KB
Screen shot 2011-02-08 at 12.24.57.png, 307 KB

Replies to This Discussion

Permalink Reply by morteza farhadian dehkordi on February 8, 2011 at 5:55am

it s working for me

Attachments:

01.ghx, 95 KB

Permalink Reply by Todor Demirov on February 8, 2011 at 7:30am

this is exactly what I tried to do))) I just didn't think I need the "flip"

Permalink Reply by Chris Tietjen on February 8, 2011 at 6:04am

I agree that it looks like a bug.

Chris

Permalink Reply by Todor Demirov on February 8, 2011 at 7:23am

nice and simple! thanks. It looked like a bug to me but I wasn't sure. thanks a lot

Permalink Reply by Mateusz Zwierzycki on February 8, 2011 at 6:43am

maybe try to reparametrize ?

Permalink Reply by morteza farhadian dehkordi on February 8, 2011 at 7:00am

so what is this ?

Attachments:

pic.bmp, 1.4 MB

Permalink Reply by morteza farhadian dehkordi on February 8, 2011 at 7:19am

Permalink Reply by Chris Tietjen on February 8, 2011 at 7:01am

This is what it looks like without the flip components. No combination of reparameterizing changed this outcome.

Chris

Permalink Reply by Danny Boyes on February 8, 2011 at 7:04am

Remember there are duplicate curves with this method as illustrated. You need to whittle it down to one set for each direction and then pair them up accordingly.

Permalink Reply by Todor Demirov on February 8, 2011 at 7:20am

thanks so much for the solution. makes sense now.

Permalink Reply by Mateusz Zwierzycki on February 8, 2011 at 7:33am

it's not a bug... that is how this component works. it just takes isocurve point after point so u coordinates (of point) are as rows and v coordinates are as columns. after all you dont see difference but just look at this : (and imagine cutting surface with knife ;])

Attachments:

Untitled-1.jpg, 589 KB

Permalink Reply by Todor Demirov on February 8, 2011 at 7:43am

ok, this explains why it happens then. I thought it doesn't consider the points in such a way if I'm using the isocurves )) thanks for the explanation