Thanks, but that doesn't seem to be it. Changing the other types of inputs to my operator (such as primitives) behaves in the expected manner. The reason this is an issue is that I have a custom command which writes to two different UserDataBlobs which are both inputs to my operator. After the first is written, the operator updates and tries to read both blobs while the command is writing the second one : Crash.
--- On Thu 08/03, Andy Nicholas < andy(at)andynicholas.com > wrote:
From: Andy Nicholas [mailto: andy(at)andynicholas.com]
To: XSI(at)Softimage.COM
Date: Thu, 3 Aug 2006 15:11:42 +0100 (BST)
Subject: Re: input pushing operator update?
Ah right, I see what you're getting at now.The only thing I can think of that you may want to do a little digging on,is the classification of the parameter you've got your operator connectedto. If you have a look at the AddParameter2 function, you have thesiParamClassification argument that tells XSI how that parameter is to beused. I'm guessing that it gives a hint to XSI to tell it when it shouldpull that parameter to update it at the appropriate point.I don't know if that'll be of any help to you though, even if it is thecause of the problem.>>> Well, my impression was that the scene keeps track of when an operator has> inputs that have changed (are "dirty") but only pulls an update of the> operator when its output value is required.>>>> --- On Thu 08/03, Andy Nicholas < andy(at)andynicholas.com > wrote:> From: Andy Nicholas [mailto: andy(at)andynicholas.com]> To: XSI(at)Softimage.COM> Date: Thu, 3 Aug 2006 14:52:01 +0100 (BST)> Subject: Re: input pushing operator update?>> If I
understand what you're saying, that sounds like it's working the> wayit should.If you change an input to an operator, it will update. The> output isdependent on the input, so if the input updates, it makes sense> that theoutput should change too.>> I can't quite figure out this> behavior:> I've got a SICO with multiple inputs and a single output. The> output is a> UserDataBlob which is pushed to Mental Ray. Nothing else in> the scene has> anything to do with the output blob after it is created. So> I figure that> the operator should only be pulled when a render is> started. However, some> of the operator's inputs are also UserDataBlobs> and when write to one of> them, the operator Update callback is> triggered.> Any ideas why this is happening?> Ben>>>>>> _______________________________________________> Join Excite! -> http://www.excite.com> The most personalized portal on the Web!>>> --->> Unsubscribe? Mail Majordomo(at)Softimage.COM with the following text in> body:>
unsubscribe> xsi>---Unsubscribe? Mail Majordomo(at)Softimage.COM with the following text> in body:unsubscribe xsi>> _______________________________________________> Join Excite! - http://www.excite.com> The most personalized portal on the Web!>>> ---> Unsubscribe? Mail Majordomo(at)Softimage.COM with the following text in body:> unsubscribe xsi>---Unsubscribe? Mail Majordomo(at)Softimage.COM with the following text in body:unsubscribe xsi
_______________________________________________
Join Excite! - http://www.excite.com
The most personalized portal on the Web!
---
Unsubscribe? Mail Majordomo(at)Softimage.COM with the following text in body:
unsubscribe xsi
