Jump to content

Python Node Order Of Evaluation?


Atom

Recommended Posts

HI All,

 

I have a few python nodes inside a subnet to control bones on a FBX rig.

 

One python node controls the rotation of bones by providing a set of sliders to the user.

The second python node controls those sliders on the first python node.

 

This worked fine a when I developed it a few versions back before H15.313. Now that I have upgraded to H15.381 this approach seems to be failing when I try to write the animated .bgeo sequence out via a ROP Output. I know, odd, but what used to work no longer works and the only thing I have changed is my version of Houdini.

 

I am guessing that the order of operation for Python nodes may have been changed by the developers.

 

Is there any way to instruct Houdini to evaluate one Python node before another?

Edited by Atom
Link to comment
Share on other sites

Thanks for the idea, I tried parenting them in a series and reverse parenting them but the effect was still the same. The ROP Output driver simply will not evaluate python nodes while generating geometry output.

 

What does work is to place a File node in Write File mode and then simply play the timeline once, which is a lot slower.

 

I am going to use this as a work around for now.

Edited by Atom
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...