Farley, I don't think I've ever seen a surface fed directly into the decompose 2D numeric interval before, which is not to say it's incorrect, but if you want the surface UV dimensions the <Dimensions> component might be a better bet.
That being said, I don't think the results you're getting are a problem with the interval component. It seems to have something to do with the way the <Srf4Pt> NURBS surface is created. After baking your 2 example surfaces, here's the info: <Loft> "U": degree =3 CV count = 4 (0 <= U <= 120) "V": degree =1 CV count = 2 (0 <= V <= 240) <Srf4Pt> "U": degree =1 CV count = 2 (0 <= U <= 120) "V": degree =1 CV count = 2 (0 <= V <= 1) After baking your points and making a 4 pt surface in Rhino this is the result: "U": degree =1 CV count = 2 (0 <= U <= 120) "V": degree =1 CV count = 2 (0 <= V <= 240) I don't have an answer for you, but the problem might be a different glitch. -taz On Apr 29, 1:43 pm, farley2076 <farley2...@yahoo.com> wrote: > I don't know if this is really a problem, or just my general ignorance > of how surfaces and intervals are built and function, but the attached > file has two surfaces, one created from four points and the other > lofted from two lines created from those four points. Then I connect > the Interval(^2) Components component and connect to the U1 and V1 > outputs and the lofted interval gives me the correct numbers, but the > 4pt surface gives me the correct U1 number but the V1 number is always > just 1. This will make more sense in the file... > > Small potatoes to other things you have to deal with, David, and of > course and easy work around is to use the one that works, just thought > you might like to know. Or you can tell me what I'm doing wrong, which > is more likely... > > Thanks > > http://grasshopper3d.googlegroups.com/web/Interval%20Bug.ghx?hl=en&gs... > > File is called Interval Bug.ghx if this link doesn't work.
