Hey Sebastian, hey Chris,
awesome, both solutions work perfectly - cheers for that! :-)
Wasn't aware at all of both *"Get Element Index"* and *"Build Array From
Set". *
Thanks again,
Martin
--
Martin Chatterjee
[ Freelance Technical Director ]
[ http://www.chatterjee.de ]
On Mon, May 7, 2012 at 12:33 PM, Chris Chia <chris.c...@autodesk.com> wrote:
> Hi Martin,
> I think you are looking for this.
> You can use "Select in Array" ice node to query the individual vertex's
> position.
>
> [cid:c02c4ea5-dd64-448b-91cb-a7022225c756]
>
>
>
>
> Regards,
>
> Chris Chia
>
> Softimage QA Analyst
>
> Autodesk Media & Entertainment
>
>
> ________________________________
> From: softimage-boun...@listproc.autodesk.com [
> softimage-boun...@listproc.autodesk.com] on behalf of Martin Chatterjee [
> martin.chatterjee.li...@googlemail.com]
> Sent: Monday, May 07, 2012 5:11 PM
> To: softimage@listproc.autodesk.com
> Subject: [ICE] curve manipulation issues
>
> Hello clever people out there,
>
> I'm experiencing some annoying issues when trying to deal with Curve
> Manipulation in ICE - hopefully somebody can help me out here with some
> insight?
>
>
> 1.) I am looking for the Curve equivalent to self.ID (for PointClouds) or
> self.VertexIndex (for polyMeshes). Bottom line I want to be able to access
> a Curve Point Location in the same way I can access PointCloud points via
> "ID to Location" or Polymesh vertices via "PointIndex To Location"
>
>
> 2.) While attempting to workaround this issue I have stumbled over this:
> (see attached screenshot)
>
> When trying to get a full array of all Point Locations of a curve via "Get
> Closest Points" I NEVER get the correct point count...
>
> When the curve is closed, it will give me one more, when the curve is open
> I will get two less than the actual point count.
>
> Has anybody out there succeeded in working around this somehow?
>
> Thanks a lot in advance for any hints,
>
> Cheers, Martin
>
> --
> Martin Chatterjee
>
> [ Freelance Technical Director ]
> [ http://www.chatterjee.de ]
>
>
