try it? i cached using the cache manager just now, one file per object for the entire sequence. i haven't tried multiple files per frame (does softimage even export pc2 files this way?)
we know the pc2 support in softimage is limited. so alok's contribution is very welcome. On Sun, Nov 3, 2013 at 6:33 PM, Alan Fregtman <[email protected]>wrote: > Does the CacheOnFile node support Kai's single-file pc2 sequences? because > KP_PointCache produces a single file per mesh for the whole export. I > imagine Alok's must support this (along with a file-per-frame.) > > > > On Sun, Nov 3, 2013 at 1:45 AM, Steven Caron <[email protected]> wrote: > >> actually, the cache on file node can read .pc2 files already. give it a >> shot! >> >> but great to have more robust control, kai's version had better support >> for the format. >> >> >> On Sat, Nov 2, 2013 at 9:32 PM, Alok Gandhi <[email protected]>wrote: >> >>> Hey All, >>> >>> I made a custom ice node for directly reading .pc2 file in ICE. Not sure >>> if somebody already wrote that, but it was fun spending almost an hour of >>> weekend. >>> >>> This implements most of the logic from KP_PointCache by Kai Wolter >>> (available with source code on http://rray.de/xsi/) >>> >>> You can download the addon here <http://bit.ly/Hn9kJ3> (Windows 64 bit >>> only / Works with Softimage 2011 and upwards) >>> >>> The addon has two files: >>> 1. A Custom ICE node for reading .pc2 files. Almost all parameters from >>> KP_PointCache are available in the node. >>> >>> 2. A Compound as wrapper around the low level node to implement the PPG >>> (as there is no way to write a PPG Layout for a Custom ICE node in C++). >>> >>> It is not super useful as you can always put a point cache operator on a >>> mesh and read point positions from that in an ICE Tree but it eliminates >>> altogether the need of an .obj / mesh to read .pc2. >>> >>> Hope it helps somebody somewhere. >>> >> >> >
