We had a very lengthy discussion on this topic a few months ago. Short answer - not really as ICE doesn't expose the necessary functionality. There is a workaround for a very narrow set of cases, but its quite involved and more or less negates the benefits of using ICE.
For now you'll need to use the standard SDK and write a script or custom operator. Easy to code, but the standard SDK is single threaded which will be the limiting factor in your operator's performance. In my tests, the number of subsurfaces in the NURBS Surfacemesh is the biggest influence on performance as each subsurface represents another closest locations search operation. You won't notice any performance difference vs. ICE if your NURBS SurfaceMesh only contains one or two subsurfaces, but if the SurfaceMesh has more than 2 subsurfaces you will notice a big performance hit very quickly. ICE makes this seem practical only because it can do this in a multi-threaded context. Matt ________________________________ From: [email protected] [[email protected]] On Behalf Of Jeremie Passerin [[email protected]] Sent: Monday, October 21, 2013 8:44 AM To: softimage Subject: [ICE] location subsurface index Hey guys, So i'm still working on a deformer and i'm using a 'Get Closest Location Node' with a surface with 4 sub surfaces. I don't see any way to find the index of the subsurface of the location. I can get the UV and even the number of subsurface, but how do I get which subsurface the location is actually on ? thanks for your help, Jeremie
