This one is strange and I’m unable to reproduce this in a simplified network, essentially, there are certain conditions where a merge dat when inputs are disconnected, maintains it’s data within the node.
Here’s a detailed video(with audio) of the bug and some interesting things I’ve noticed about it. Hope this helps!
http://www.enviral-design.com/downloads/TMP/merge%20dat%20bug.mov
Ok I’m still experiencing this, and I have more specific info and a way to create now, woo!
mergeDatBug_V2.2.toe (4.3 KB)
Check attached file, should open like this:
If you click connect, you’ll correctly get this:
If you click disconnect, you’ll get this:
If you turn off “By Name”:
and click disconnect, reconnect, it works fine. So, this bug is related to the parameter By Name.
Thanks for all of the details. I was able to reproduce the issue using your file and am working on a fix for it now.
@lucasm Sorry for the delay in getting back to you, a fix for this was made and should be in the currently posted 2020.22080 build.
Let us know if you find otherwise.
Thanks
