I'm using the python time()expression to animate some node properties, lets say, to move a box along in a certain axis. So I write up parm expression to do this, something like time()*.01.
I'm noticing that whenever houdini needs to reference the current frame in a parm expression, the node evaluation time can shoot up more than 100x.
You can see in my attached image of the performance monitor that using the transform which uses the time()expression is responsible for 63.4% of the cook time, while the normal transform without such an expression accounts for <1%.
I'm sure Houdini does some intelligent patterns for cooking of nodes. But such a big slow down makes animating properties with time() basically impossible for anything but the most basic of scenes.
Am I missing something here about now to use time()/$FF to animate properties? Is there a way to use time() to animate properties that does not involve a huge performance hit?
wyhinton1 I'm using the python time()expression to animate some node properties, lets say, to move a box along in a certain axis. So I write up parm expression to do this, something like time()*.01.
I'm noticing that whenever houdini needs to reference the current frame in a parm expression, the node evaluation time can shoot up more than 100x.
You can see in my attached image of the performance monitor that using the transform which uses the time()expression is responsible for 63.4% of the cook time, while the normal transform without such an expression accounts for <1%.
I'm sure Houdini does some intelligent patterns for cooking of nodes. But such a big slow down makes animating properties with time() basically impossible for anything but the most basic of scenes.
Am I missing something here about now to use time()/$FF to animate properties? Is there a way to use time() to animate properties that does not involve a huge performance hit?
You're comparing animated to not animated. Of course the performance hit is huge. It's infinitely huge.
