RE: ICE | Grouping Points by Polygon Island? Options

[Matt Lind]

Finding polygon Islands is recursive in nature, so I don't think you want to do that in an ICE tree as that would be a lot of overhead.  You'd be better off running a script to create clusters based on polygon islands and connecting your ICE tree to the cluster.

Matt

 

 

 

 

Has anyone figured out a clever way to create arrays of point ID's broken
out by Polygon islands?
I can do this when my islands have a regular point count, but not for a mesh
that's broken out randomly, like something that's been shattered.

A link to a compound would be cool, but I'm happy just getting solution
examples for an approach that has worked for somebody.

Thanks in advance!

-Bradley

 

[Bradley Gabe]

That's what I'm doing. :-)
I have a compound that assigns an ID based on cluster membership, and a script that builds an ICE tree from selected clusters.

I was just wondering if anyone has figured out a clever shortcut that is more easily self contained, and has better performance.

[Grahame Fuller]

It may not be the fastest or the cleverest, but can you use a method like this compound (attached)?

gray

From: softimag...@listproc.autodesk.com [mailto:softimag...@listproc.autodesk.com] On Behalf Of Bradley Gabe
Sent: Friday, March 05, 2010 03:18 PM
To: soft...@listproc.autodesk.com
Subject: Re: ICE | Grouping Points by Polygon Island? Options

That's what I'm doing. :-)
I have a compound that assigns an ID based on cluster membership, and a script that builds an ICE tree from selected clusters.

I was just wondering if anyone has figured out a clever shortcut that is more easily self contained, and has better performance.

[Matt Lind]

What are you trying to do with the ID info once you have it?  perhaps that info would lend optimization ideas.

Otherwise, I'd say try a hash table / map that your ICE tree can read so it can do fast lookups across the entire mesh.  The table could be created by script and fit in a single ICE node and can be an exposed port on your compound to make it generic enough for multipurpose use - this would eliminate need for clusters.  However, if your mesh has a ton of polygons, you might have to find a better way to store the data.

 

Matt

[Bradley Gabe]

That's hella clever, you kidding? :-)

I tried to do something recursive with Point Neighbors, but couldn't work around context issues with assigning my results. This should work. Thanks!

-B