Re: Bad Operator Update

Date : Tue, 12 Sep 2006 15:58:26 +0100 (BST)
To : XSI(at)Softimage.COM
From : "Andy Nicholas" <andy(at)andynicholas.com>
Subject : Re: Bad Operator Update
Hi Dan,

You could try this to see if it makes a difference:

var xform = XSIMath.CreateTransform();
xform.SetTranslation(pos);
out.value.transform = xform;




> Hi there.
>
> I have an huge problem with a scripted self installing operators wrote in
> JScript. What the operator does is not important. the Output is the Global
> kineamtics of an objects. the last few lines look like this pseudo code:
>
> // output is obj.kinematics.global
> outTrans = output.Transform
> outTransform.SetTranslation = Vector3
> output.Transform = outTransform
>
> The operators seems wor5ks fine in most of the cases, but somtimes it has
> a
> bad update and the object is transformed not corecctly but with a kinda of
> delay. This happens when the object are a constrainer or a deformer for an
> envelope.
>
> I tried to change the code in something similar to this:
> output.Posx = Vector3.x
> output.Posy = Vector3.y
> output.Posz = Vector3.z
>
> This works better, but sometimes I still have problem. For semplicity I
> talked just about position but I have Rotation as well. I can't belive I
> have to pass as input 6 channel instead of the Kinematics.Global node for
> avoid a bad update.
>
> Anybody knows a workaround for this problem? Somebodies know if it's
> possible force XSI to update an operator correctly. Always Evaluate is set
> to true.
>
> Cheers,
> Daniele
>
>
> ---
> 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


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.