Mailing List
Home
Forum Home
Softimage
Carrara
trueSpace
Dir3d-l
Maya - a powerful 3D animation and visual effects software
Macromedia Flash Development
Subjects
Cameras
scaleDown command
black out solved
Aircraft Tutorial
Mathematical XYZ ?
Its done This vs That
Its done first week
recommendations for screen video captures?
3DExplorer "Oddity "
New Director
ProTeam renewals
Fuel 's new websites (X post)
Blue peter create a make toy
targeting groups question
XPost: Shockwave 3D game ( sort of )
RES: RES: RES: Fish Modeling
Emitting particles from object intersection
Fuel 's new websites (X post)
Texturing
Big Break Contest Videos
New Plugins
Models and Texture on my updated site
Error Installing Patch tS6 6
Plasma?
Looking for Inspiration
Weird EMail Q
It 's done first week ?
Cherry not cranberry
New game
Camera Animation Problem
Particle plugins?
 
Operators evaluation order

Operators evaluation order

2004-03-09       - By Jose Luis Gomez

 Back
Reply:     1     2     3  

Thanks for the answer Jill.

I have found a workarround to solve my problem that I think was caused
for the use of bones and not by the evaluation order as I thought.

Anyway, if you see the scene attached I have a graph like the following:

root
| -- eff (scop)
       | -- root1
              | -- eff1 (scop)

Which is more or less what we where speaking about yesterday. I have
created a SCOP just for testing, and if you see in the script editor the
logmessages, the one with "root" as parent (and input) is eveluated
before the one with "root1" as parent. The operator is applied to
...kine.global and have root?.kine.global as input.

If I have understood your post "eff1" should be evaluated before "eff"
but this is not what is hapening. This is acting the way I wanted and I
suppose it is because the input of the "eff1" operator (root1) depends
on the result of the "eff" operator as "eff" is its parent. Is this the
way it is working??

Sorry for taking your time

/Jose

Jill Isner wrote:

>The child1 will only be evaluated when Child is dirty.  Child1 will always be
applied first, since you have labeled that Child dependent of the value form
Child1.
>
>If you need child1 to be applied after Child and needs the value of child try
this setup
>Parent
> | -- Child1 (Operator applied)   - add input to Parent and to Parent1
> | -- Child (Operator applied)
>                    
>
>Note watch out for cycles using the CycleChecking command.
>
>-- --Original Message-- --
>From: owner-xsi@(protected) [mailto:owner-xsi@(protected)]On Behalf
>Of Jose Luis Gomez
>Posted At: Monday, March 08, 2004 11:22 AM
>Posted To: xsi
>Conversation: Operators evaluation order
>Subject: Operators evaluation order
>
>
>Hi list,
>I have created a compiled operator that calculates the position of an
>object according the position of his parent. Now I have two objects with
>the operator applied but the parent for the second object is child of
>the first object that has the operator applied. It is something like
>this for those of you already lost:
>
>Parent
> | -- Child (Operator applied)
>           | -- Parent1
>                    | -- Child1 (Operator applied)
>
>I need the "child1" operator to be applied always after the "child"
>operator... Is there anyway I can do it?? Child1 has Paren1.kine.global
>as input... isn't it supposed to be re-evaluated when "Child" position
>changes???
>
>I hope this makes sense for somebody....
>
>cheers
>
>/Jose
>
>---
>Unsubscribe? Mail Majordomo@(protected) with the following text in body:
>unsubscribe xsi
>
>---
>Unsubscribe? Mail Majordomo@(protected) with the following text in body:
>unsubscribe xsi
>
>.
>
>  
>