I don't think this is by design for performance or optimization. All the
operators _should_ update as a default behavior. I suggested it because
I have seen stranger things happening than this, especially in regards
to scene graph updates. So it's worth a try. I would put this under a
bug category, but one which is not easy to repro. There could be a
number of things going wrong under the hood. There are hundreds of
libraries with thousands of update calls/functions in their modules
during the run time.
On 12/10/2013 10:27 AM, Morten Bartholdy wrote:
Thanks, I will try that. If this is the case, I'd say the
implementation of ICE is somewhat flawed. I understand this should be
for performance reasons - it would be nice with an "evaluate whole ICE
Tree" functionality which could be turned on by the user, to avoid
wasting so much time getting a simple thing working.
Morten
Den 10. december 2013 kl. 14:35 skrev Alok Gandhi
<[email protected]>:
> It seems that farm is not updating the deoformer operators when
opening the scene at the particular frame. Try plotting all the
parameters on the operators, even if they have constant value.
>
> Sent from my iPhone
>
> > On Dec 10, 2013, at 8:09 AM, Morten Bartholdy
<[email protected]> wrote:
> >
> > It is a simple grid, a long strip in the root of the scene. A non
simulated ICE tree for some Turbulize Mesh deformation and then a
curve deformation.
> >
> > MB
> >
> >
> >
> >
> > Den 9. december 2013 kl. 17:41 skrev Eric Thivierge
<[email protected]>:
> >
> > > Ref models are fine with ICE Deformers. You just need to ensure
that
> > > the 'Get Data' nodes are using 'this_model' and / or 'self'
instead of
> > > the full name. Since when you import a ref model it will most
likely
> > > change the top model name and your ICE deformations will crap out.
> > >
> > > Can you open the rig on one of the farm machines and VNC /
remote in
> > > and see if it's functioning and check if the ICE Trees are
evaluating
> > > properly?
> > >
> > > On Monday, December 09, 2013 11:37:28 AM, Benoit Delaunay wrote:
> > > > Are refmodels a bit buggy ?
> > > >
> > > >
> > > > On Mon, Dec 9, 2013 at 4:00 PM, Alan Fregtman
<[email protected]
> > > > <mailto:[email protected]>> wrote:
> > > >
> > > > Are you using refmodels?
> > > >
> > > >
> > > >
> > > > On Mon, Dec 9, 2013 at 10:58 AM, Morten Bartholdy
> > > > <[email protected] <mailto:[email protected]>> wrote:
> > > >
> > > > __
> > > >
> > > > I have a weird problem, which might have a simple fix,
but I
> > > > don't know what.
> > > >
> > > >
> > > > I have a mesh which I deform with Turbulize Mesh in a non
> > > > simulated ICE tree. It works fine in the viewport and the
> > > > renderregion, plus when rendering on my workstation.
However
> > > > when I render on the farm (RoyalRender) the ICE
deformation is
> > > > lost. I have inserted a Log Values node to see if it
is ICE
> > > > optimization causing this, but same, same, no
deformation. I
> > > > guess I can cache the deformation and then it should
render
> > > > fine, but I wonder what might be the issue here. I see no
> > > > problems in the render logs.
> > > >
> > > > Softimage 2013 SP1, no installation changes recently.
> > > >
> > > > - Morten
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > --
> > > >
> > > > http://www.bendelaunay.com/
> > >
--
ALOK
GANDHI
/ directeur technique senior- senior technical director
[email protected] <mailto:[email protected]>
T:
*450 430-0010 x225
F:
*450 430-0009
www.modusfx.com <http://www.modusfx.com>
---------------------------------------------------------------------------------------------
MODUS
FX
120 Rue Turgeon,
Sainte-Therese (Quebec) CANADA J7E 3J1
Follow us on
Facebook <http://www.facebook.com/ModusFX>
&
Twitter <https://twitter.com/Modusfx>
**
