There’s an issue in RayTK operators where in some cases lots of internals are cooking when certain parameters change.
The attached file has a simplified non-RayTK example that reproduces the issue.
cook_dependency_bug.toe (10.6 KB)
In the example, there’s a comp with a child comp.
The child has a parameter that refers to the parent.
Then inside the child, there’s an eval DAT that uses op(parent().par.Thing).name, which produces the parent comp’s name.
Using the mouse to change some but not all of the parameters on the parent comp causes the eval DAT to cook excessively, even though the op name isn’t changing.
Using an expression on those parameters doesn’t cause the excess cooking, even if the expression changes on every frame.
Related issue: Excessive cooking when ROP parameters change · Issue #983 · t3kt/raytk · GitHub