And the inputs to the weighting tree aren't changing?

I can't test this quickly myself, but maybe try setting the weights using a 
tree on a different object, e.g., a "weighter" null.

gray

From: [email protected] 
[mailto:[email protected]] On Behalf Of Jules Stevenson
Sent: Thursday, March 14, 2013 04:02 PM
To: [email protected]
Subject: Re: Forcing data on ice-trees to be persistent.


Hey Steven, yep
On Mar 14, 2013 6:53 PM, "Steven Caron" 
<[email protected]<mailto:[email protected]>> wrote:
hey jules

so you are setting the weights in the modeling stack? and using them in the 
animation stack?

s

On Thu, Mar 14, 2013 at 11:44 AM, Jules Stevenson 
<[email protected]<mailto:[email protected]>> wrote:
Hmm, actually this is not so cool - just the process of reading in the cached 
attribute required (a copy of EnvelopeWeightsPerDeformer) and setting it to the 
envelope weights is slowing down the env operator to a pretty unintuitive 
level... This leaves no room for optimization as far as I can see, there's 
nothing simpler I can do. Any one have any other thoughts on methods to use for 
this?

On Thu, Mar 14, 2013 at 4:19 PM, Jules Stevenson 
<[email protected]<mailto:[email protected]>> wrote:
Doh, of course. Thanks Vladimir.

On Thu, Mar 14, 2013 at 4:09 PM, Vladimir Jankijevic 
<[email protected]<mailto:[email protected]>> wrote:
cache it and use a switch to load the cached data or re-evaluate the tree.

On Thu, Mar 14, 2013 at 12:02 PM, Jules Stevenson 
<[email protected]<mailto:[email protected]>> wrote:
I'm building a tool which sets data to weights via ICE (an auto weighter). What 
I need it to do is working great, however, as it's ICE, it executes all the 
time - whenever a deformer is moved it re-evaluates the tree. The tree is slow. 
What I really need is some way of making the ice data persistent without 
constantly re-evaluating, In an ideal world this would mean when I disconnect 
the Ice Node, the data that it has written to the weights *doesn't* disappear.

I know the easiest way to achieve this is freeze the object, but because this 
is an iterative user tool it's not an ideal workflow. Anyone got an ideas if 
something like this is possible?

Many thanks,

Jules





--
---------------------------------------
Vladimir Jankijevic
Technical Direction

Elefant Studios AG
Lessingstrasse 15
CH-8002 Zürich

+41 44 500 48 20<tel:%2B41%2044%20500%2048%2020>

www.elefantstudios.ch<http://www.elefantstudios.ch>
---------------------------------------



<<attachment: winmail.dat>>

Reply via email to