I do have the same number of motion vectors as I have points to move. I am using version .6.0006.
I flattened the Move.T input, and that seems to have done the trick! Thanks for your quick help. By the way, with regards to your advice to "plug both vector arrays into the T input", I must be missing something because Grasshopper will only let me plug one input in at a time. On Apr 1, 3:26 pm, David Rutten <[email protected]> wrote: > Hi Justin. > > if you're certain that you have the same number of motion vectors as > you have points to move, then the problem may lie in the Data Tree > mismatching. > Are you using a version higher than 0.6? > > If yes, try flattening the input of the [Move.T] input. > > Also, There seems to be a bug with Merge, instead of merge, plug both > vector arrays into the T input of Move and see if that makes a > difference. > > -- > David Rutten > [email protected] > Robert McNeel & Associates > > On Apr 1, 11:09 pm, Justin <[email protected]> wrote: > > > Hi, > > > I am an Architecture student and I am having a lot of fun using > > Grasshopper in school. Thanks for all your hard work. > > > Here is an image of what I am working with: > > >http://grasshopper3d.googlegroups.com/web/gh.png?hl=en&gsc=l_xZMxYAAA... > > > I have a pretty simple issue that I can't figure out how to remedy. > > Basically I want to generate a series of numbers that will be used to > > move a list of points in the z direction. I would like the series of > > numbers to range from minimum to max, then back to min (step 2 in the > > image), such as: > > > 8.55 > > 9.10 > > 9.64 > > 10.19 > > 10.74 > > 11.29 > > 11.83 > > 12.38 > > 12.93 > > 13.48 > > 14.02 > > 14.57 > > 15.12 > > 15.67 > > 16.21 > > 16.76 > > 17.31 > > 17.86 > > 18.40 > > 18.95 > > 19.50 > > 19.50 > > 18.95 > > 18.40 > > 17.86 > > 17.31 > > 16.76 > > 16.21 > > 15.67 > > 15.12 > > 14.57 > > 14.02 > > 13.48 > > 12.93 > > 12.38 > > 11.83 > > 11.29 > > 10.74 > > 10.19 > > 9.64 > > 9.10 > > 8.55 > > 8.00 > > > So I got that part working, the issue is when I try to 'Move' the > > points (Step 3 in the image), the translated geometry coming out of > > the 'Move' module is moved in a linear fashion e.g. 8 -> 20 instead of > > the desired 8 -> 20 -> 8. > > > Could someone help me understand why this is happening? > > > Thanks
