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, Nov 5, 2013 at 1:15 AM, Alok Gandhi <[email protected]>wrote: > 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 <[email protected]> wrote: > >> 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 >> reads the attribute it creates in the animation stack. >> >> The operator itself is being evaluated, and logging to console confirms >> that it is generating the expected output, but when reading the same >> attribute in the ICE tree the values are from the previous evaluation >> rather than the current one. >> >> I had a go at deleting and re-creating the attribute on each update, >> hoping that it would counteract any caching that might be occurring, but it >> had no effect. >> >> Any Ideas? Is using a customer operator to write to ICEAttributes a no-no? >> >> Using Softimage 2013 SP1 >> >> >> >> > > > -- >
