RE: SCOPs with more than one output...

["kim aldis" <xsi(at)kim-aldis.co.uk>]

And double check that the op is or isn’t being called by printing the output name at the start of your update code.

 

Also, sometimes when you put a parameter onto an output port the parameter’s parent operator or property gets stuffed in there instead. The exact reason or circumstance for this evade me at the moment but there’s some explanation in the docs somewhere. I was caught by it only the other day.

 

 

From: owner-xsi(at)Softimage.COM [mailto:owner-xsi(at)Softimage.COM] On Behalf Of Bradley Gabe
Sent: 27 December 2007 19:28
To: XSI(at)Softimage.COM
Subject: Re: SCOPs with more than one output...

 

What has often got me in the past, cap sensitivity. Double check your variable and port names in your script. SCOPs *are* cap sensitive, and on output you won't get any error messages if you attempt to set a value on a port with the wrong name.

On Dec 27, 2007 12:20 PM, Dan Yargici <danyargici(at)gmail.com> wrote:

I have a SCOP with 2 outputs.  I'm  trying to set these using the technique in the Docs - i.e.

if(Out.name =="blah")
{
   Out.Value = oBlah;
}
else........

But I only have one output being updated!  Am I missing something reeeeally obvious here?

One is a Weightmap, and the other is a UserDataBlob...

Cheers,

DAN