ICE Closest location on Geometry

2013-12-16 Thread Chris Marshall
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

Re: ICE Closest location on Geometry

2013-12-16 Thread Leonard Koch
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

Re: ICE Closest location on Geometry

2013-12-16 Thread Chris Marshall
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 leonardkoch...@gmail.com wrote: There aren't really any super optimal ways of

Re: ICE Closest location on Geometry

2013-12-16 Thread Alan Fregtman
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

Re: ICE Closest location on Geometry

2013-12-16 Thread Chris Marshall
Oh I see! I was thinking of it all being self contained in the one tree, but I understand now about making an Ice tree on each. I guess it would be useful to be able to do it all in one through scripting, but that'll be beyond my ability. I can get by without doing that. Thanks both! On 16

Re: ICE Closest location on Geometry

2013-12-16 Thread Leonard Koch
Oh and the Color to RGBA and RGBA to Color nodes are just there to strip the alpha out of the display color, which is 0. On Mon, Dec 16, 2013 at 5:06 PM, Leonard Koch leonardkoch...@gmail.comwrote: You can definitely have it in the same tree. That actually isn't a problem. I have attached a

Re: ICE Closest location on Geometry

2013-12-16 Thread Chris Marshall
Thanks Leonard! That's very helpful. The only issue is that you need to know in advance the name of the four meshes, which are hard wired into this ice tree with the set data node. But that's fine, I can live with that. Thanks again!! On 16 December 2013 16:09, Leonard Koch

Re: ICE Closest location on Geometry

2013-12-16 Thread Benoit Delaunay
You already have theses nodes in your ice tree as they are plugged in the closest location compound. Maybe you can plug the 'out name' of your geometry nodes in the 'in name' of your set data nodes ? (1 for each geometry)

Re: ICE Closest location on Geometry

2013-12-16 Thread Chris Marshall
OK I'm sure I just tried exactly that and it gave me a context error. I'll give it another go. Thanks a lot On 16 December 2013 16:26, Leonard Koch leonardkoch...@gmail.com wrote: Oh you can totally do that. See the attached screenshot with the updated setup. On Mon, Dec 16, 2013 at 5:23

Re: ICE Closest location on Geometry

2013-12-16 Thread Chris Marshall
Got it working! Thanks for that On 16 December 2013 16:28, Chris Marshall chrismarshal...@gmail.com wrote: OK I'm sure I just tried exactly that and it gave me a context error. I'll give it another go. Thanks a lot On 16 December 2013 16:26, Leonard Koch leonardkoch...@gmail.com wrote: