Re: Persisting data in a Scripted Op

Date : Tue, 5 Jun 2007 21:25:03 +0200
To : XSI(at)Softimage.COM
From : "Ahmidou Lyazidi" <ahmidou.xsi(at)gmail.com>
Subject : Re: Persisting data in a Scripted Op
Hi
I have a question about that, we are using user data in the context (operatorcontext.userdata), the operator is working fine but is failling at rendering .
Should we use the plugin.userdata instead?
In any case take care about the operatorcontext.userdata !

2007/6/5, Hans Payer <hanspayer(at)gmail.com>:
Couldn't you just hard code your data it in the SCOP? If I understand you correctly you want to get rid of the UserDataBlob? I'm not sure what is your question.

Hans

On 6/5/07, Bradley Gabe <withanar(at)stanwinston.com> wrote:
I have my SCOP logic working properly now, however I am driving it with a data set I'm storing in a separate UserDataBlob. At this point, I would like to localize everything to the one SCOP. In the past, I've stored data in text parameters, but for this case I'm thinking the data sets will be too large to do that.

-Brad

-- 
Bradley R. Gabe | Senior Creature TD | Stan Winston Studio



Search the XSI List archives here or use the advanced search form to search across mailing lists. Searching help is available.
This site supposedly brought to you by Benjamin Grosser and the Imaging Technology Group.