David: Ok. I pared down my file, and I uploaded it as scaleBug.zip for your review. The def file contains four different versions of the same construct. The two on the right scale up 3 surfaces based on 3 centers. The two on the right scale up four based on four. The top versions contain my original code, which did include only one scale factor. The bottom version creates a list of scale factors with one integer for each item in the list. As you can see, the 3 version works. The 4 version seems to scale each surface around some unknown point. Maybe I'm missing something. But I can't figure it out.
I appreciate your help greatly. I love the software. -henry On Feb 11, 7:59 am, David Rutten <[email protected]> wrote: > Hi Henry, > > the reason you only get a single surface with Shortest List is > probably because you only specify a single scaling factor. Thus, the > shortest input list has a length of 1 and there will only be a single > output value. > > Scaling works fine here with 16 planes and 16 center points, perhaps > when you generate more than 4 points the order get messed up? I'd have > to see your file in order to say anything intelligable about it. > > -- > David Rutten > [email protected] > Robert McNeel & Associates > > On Feb 11, 2:56 am, hgrosman <[email protected]> wrote: > > > I have a set of planar surfaces with three sides and a set of centers. > > I feed them both to the scale component. When I have 3 or fewer > > sufaces and centers, scale works fine. The sufaces scale about the > > centers as expected. Also as expected the behavior is the same whether > > data matching is set to "longest list" or "shortest list" (the number > > of surfaces and number of centers is the same). If, however, I have 4 > > or moer sufaces and centers, everything goes crazy. When the data > > matching is set to "shortest list" the output is only one surface. > > When the data matching is set to "longest list" I get four surfaces, > > but they seem to be scaled around points other than the centers. > > > I tried to hack up a version of using Scale NU instead of Scale, and I > > got similar behavior. Has anyone else had this problem? > > > Any help is greatly appreciated. > > -henry
