FIXED: Selective cook broken when after DAT > CHOP

2017.31700 099
x64
win 10

Hey I have managed to isolate a phenomenon I’ve not fully tracked down but experienced for a while to a specific issue.

I have a panel COMP, and I am moving the mouse around in it and the u/v values are in a chop.

Then, I have an execute DAT (same result with chop execute) which attempts to write the u/v chop values to a table.

Then I convert this table of values to a chop, then I multiply it to 0 with a math chop.

Then I put a null with selective cook after this assuming it will control cooking to only when the value changes. However this seems to be broken in this scenario.

Is this in some way intended or correct behavior? or perhaps a bug?

Thanks! Full example attached.
selectiveCook_brokenWithDatToChop.1.toe (4.86 KB)

It is a bug with CHOPs that is getting inputs from DATs and will be fixed in builds 099.2017.14900+. Thanks for the report!

Awesome! Glad to hear.
Will that mean it’s also hitting experimental builds?

Yes, the fix should be in experimental builds 2017.32960+