A very simple helper component you can use to control the cooking of your DAT networks. Useful if the master table is cooking every frame but the rows you select DAT into a separate chain actually have constant values. Hopefully the select DAT will one day be smart enough to do this itself.
Here’s the component
cookCTRL.tox (534 Bytes)
and an example
example.toe (2.21 KB)
Exellent!
I remember reading somenthing in the release notes saying that “now” an expression cooking in a tab cell would not force the cooking of the rest of the cells. Was I dreaming? I’m not finding that comment in the release notes any more.
with the newly implemented export channel capabilities directly from a DAT, this component is a great solution for multiple channel exporting. Maybe there are others solutions, didn’t try much.
thanks!
I think you mean a release note that referred to local variables cooking and the special case of using tab() on a table DAT. Have a look at this file and change one of the values in the table1 DAT. Only one of the “branches” will cook.
tabcook.toe (4.38 KB)