Glad it helped you. And yea, now thinking in retrospect, you won't need the 
switch context as the getpointid already does that.

Sent from my iPhone

> On Nov 4, 2013, at 9:23 AM, Cristobal Infante <[email protected]> wrote:
> 
> VERY HANDY Alok, I can confirm you don't need the switch context node, all 
> the rest worked fine..
> 
> By the way, the BIG difference in relation to the default  "Cache on File" 
> read node, is that you are able to move your cached geometry 
> around the scene. So if you have a last minute layout change you can deal 
> with it in rendering. This is way we've stuck with KP op
> reader so far..
> 
> 
> 
> 
> 
> 
>> On 4 November 2013 13:58, Alok Gandhi <[email protected]> wrote:
>> Hi Cristobal,
>> 
>> The node output a single array of pointpositions. So you have to convert the 
>> array to per point attribute. A getpointid plugged into the select in array 
>> and them set pointposition will do the trick. Of course you know that the 
>> target mesh or pointcloud should have same number points as in the pc2 file. 
>> Also you might need a  switch context node before set pointposition.
>> 
>> In case of an empty pointcloud, it is easier. Just plug the output of the 
>> node directly into an add points node.
>> 
>> 
>> Sent from my iPhone
>> 
>>> On Nov 4, 2013, at 8:13 AM, Cristobal Infante <[email protected]> wrote:
>>> 
>>> Hi Alok,
>>> 
>>> Thanks again for sharing this tool, we still rely KP pc2 reader so having 
>>> an alternative is really handy.
>>> 
>>> I was guessing "Read PC2 File" > "Set Point Position"?
>>> 
>>> But I am getting a structure mismatch, probably doing the wrong thing!
>>> 
>>> Thanks,
>>> Cris
>>> 
>>> 
>>>> On 4 November 2013 05:40, Alok Gandhi <[email protected]> wrote:
>>>> Ah I see, I was confused when you said " i haven't tried multiple files 
>>>> per frame (does softimage even export pc2 files this way?)". 
>>>> 
>>>> Well in that, sure you can export single file per frame per object through 
>>>> KP_PointCache manager, you simply have to select the start and end frame 
>>>> as the same. PC2 file format have the notion of  "samples" rather than 
>>>> frame, so if you have one sample per frame set then basically you are 
>>>> exporting one data set (pointpositions) per frame.
>>>> 
>>>> 
>>>>> On Mon, Nov 4, 2013 at 12:26 AM, Steven Caron <[email protected]> wrote:
>>>>> no one said that you could have multiple objects in the same .pc2 file.
>>>>> 
>>>>> 
>>>>>> On Sun, Nov 3, 2013 at 8:37 PM, Alok Gandhi <[email protected]> 
>>>>>> wrote:
>>>>>> I am a little confused...  
>>>>>> 
>>>>>> For sure, you cannot have multiple objects in the same .pc2 file, the 
>>>>>> format simply doesn't support that.
>>>> 
>>>> 
>>>> 
>>>> -- 
>>>> 
> 

Reply via email to