As an operator apparently cannot have ICEAttribute output ports, I instead
pass the polymesh and pointcloud primitives and add the operator to the
pointclud.
CustomOperator customOperator =
> pickedObject.GetActivePrimitive().AddCustomOp( L"HairCommandsGenerate",
> inputs,L"HairCommandsGenerate",s
Ok, I get it. Can you share how you are pushing the data from the operator to
ice tree ?
Sent from my iPhone
> On Nov 4, 2013, at 7:23 PM, Mathias N wrote:
>
> To be more specific, in addition to reading the point positions I also grab a
> myriad of custom properties (userdatamaps and userda
To be more specific, in addition to reading the point positions I also grab
a myriad of custom properties (userdatamaps and userdatablobs) which are
combined to generate the attribute data.
Seeing as the operator itself is evaluating correctly, I felt it best to
use a simplified example.
On Tue,
Is there a particular reason you are reading the pointposition from a
custom operator and not from the ice tree which is supposed to have the
data ?
On Mon, Nov 4, 2013 at 6:48 PM, Mathias N wrote:
> I have set up a custom operator that reads the point positions of a mesh
> and spits an array i
I have set up a custom operator that reads the point positions of a mesh
and spits an array into a per-object ICEAttribute.
For the most part this setup is working flawlessly, but it appears to be
updating on a 1-frame delay.
The custom operator is in the modeling stack, with the ICE tree that re
5 matches
Mail list logo
