Thanks Christian, I think I have it working now. The array stuff always confuses me. The only strange thing is that I could only get the proper position when running the final output through a Linear Interpolate set to ".5".
[image: Inline image 1] On Wed, Jun 17, 2015 at 1:13 PM, Christian Keller <[email protected]> wrote: > Use a build array from set node with the positions. Then a select in array > with the id +/- whatever to put it on the position. > You've to filter that, because you don't wanna set something on the even > points. That means piping it through a filter node. Odd/even is easy with > modulo... > You've to set the position array into a separate variable first, otherwise > it would not work with the filter node. > Sure you figure that out ! > > -- > Christian Keller > Visual effects|direction > m +49 179 69 36 248 > > [email protected] > Vimeo.com/channels/96149 > > Am 17.06.2015 um 17:52 schrieb Byron Nash <[email protected]>: > > Digging up this old thread. I'm trying to get some data from one set of > points and apply them to another set within one polygon object. I see how > some of the examples shown in this thread can access one point, but what > about every even or odd numbered point? I'd like the odd points to share Y > position with the next even point. How can I find and apply the position > data of (Vertex Index -1)? > > Thanks! > > On Mon, Dec 15, 2008 at 8:49 AM, Alan Fregtman <[email protected]> > wrote: > >> Cool! I wouldn't have thought of using that. :) >> >> Good job exploring stuff, Chris, >> >> -- Alan >> >> >> On Mon, Dec 15, 2008 at 6:20 AM, Chris Marshall >> <[email protected]> wrote: >> > Ah Hah! Got it working. >> > Took some grappling, but was simple solution in the end. From the >> original >> > working setup where you filter the element index, if you run the output >> of >> > the filter node through a "Get Maximum in Set" node, this gives you >> *just* >> > the single vector. This is confirmed by showing the values, before this >> node >> > you get zeros on the cube etc, after this node you just get the one >> vector >> > values displayed at the origin. So it's only spitting out the stuff >> wanted. >> > Phew! >> > Thanks again. >> > Chris >> > >> > Chris Marshall wrote: >> > >> > Thanks for the explanation. It does appear to be confusing. It looks >> like >> > the tools for accessing sets are limited, though it might be possible >> to get >> > the data required with some fiddling. I'll have a dabble. >> > Thanks >> > Chris >> > >> > javier wrote: >> > >> > I quickly scanned thrugh this email, I think the answer is that points >> > in a polymesh are not part of an array but part of a set. so you are >> > extracting the selected element in the array per point, that means all >> > points. >> > >> > It seems to me that ICE is built using 2 differetn paradigmns for >> > point access. Arrays and Sets. >> > A particle cloud or a Polygon's points are points in the set, so >> > youhave to either use the statistics nodes or in your case, I think >> > getting the point by ID should do it. Im not in front of xsi, but i >> > think you could grab the point array, enter the id index into an id >> > node and then maybe plug into a filter node? I agree is a bit >> > confusing >> > >> > >> > Converting arrays to sets seems quite easy if the array is of vectors. >> > you get your array and create a point cloud and stick the array into >> > the AddPoints, then you can grab the point positions as set. >> > I havent tried the opposite. >> > >> > >> > >> > >> > _______________________________________________ >> > Softimage mailing list >> > [email protected] >> > http://listproc.autodesk.com/mailman/listinfo/softimage >> > >> > >> _______________________________________________ >> Softimage mailing list >> [email protected] >> http://listproc.autodesk.com/mailman/listinfo/softimage >> > >
