It's as straightforward as it sounds... On each mesh make an icetree. Grab a simple Integer node and a SetData and plug them together. Call your attribute something and use the same name on all the meshes, for example "self.meshID".
Your "Get Closest Location" node will output a *location* so with a GetData node, plug the output location of the location lookup into the GetData's "Source" input (NOT "In Name") and then set your attribute name in that GetData but without the "self." bit, so if you're using the previous example naming, just use "meshID". That is all, really. It's quite simple. -- If it's something you're gonna do a lot, you may wanna look at the SDK for how to set ICE data from scripting (avoiding making extra icetrees altogether.) On Mon, Dec 16, 2013 at 10:41 AM, Chris Marshall <[email protected]>wrote: > OK That makes sense, but can you just run through how to do that? How do I > set an integer for every mesh? Then how do I read that through the Get > Closest Location node? > Thanks > > > > On 16 December 2013 15:37, Leonard Koch <[email protected]> wrote: > >> There aren't really any super optimal ways of doing that. >> What you can do is just set an integer for every mesh as a per object >> value, giving each a different number and then reading those values out >> through the Get Closest Location-node. >> It is not exactly the best workflow but it does work. >> >> >> On Mon, Dec 16, 2013 at 4:31 PM, Chris Marshall < >> [email protected]> wrote: >> >>> Hi All, >>> I'm using the Get Closest Location on Geometry compound, with 5 geometry >>> inputs. What would be very useful is to somehow identify which of the 5 is >>> the closest, 1 - 5 as an integer. >>> Any thoughts on how to do this? >>> >>> Thanks >>> >>> Chris >>> >>> >> > > > -- > > Chris Marshall > Mint Motion Limited > 029 20 37 27 57 > 07730 533 115 > www.mintmotion.co.uk > >
