one other thing you could try if the caching is to slow, is to set your ICE data through script and disconnect the tree to prevent re-evaluation. then, if something needs to be changed in the data, reconnect the tree, evaluate and set the data again with script. just an idea, didn't test it, but I have similar setups where the user selects some polygons and assigns ICE data to them. Those are persistent when set by script. Other trees can read them and do stuff with it. Hope this makes sense :)
Cheers Vladimir On Thu, Mar 14, 2013 at 5:02 PM, Jules Stevenson <droolz...@googlemail.com>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 www.elefantstudios.ch ---------------------------------------
