That sounds great. And once you have exported them, will we receive a copy of our own exported comps (as FxPlug, etc.) ?

Hi Jaymie (@jstrecker) when I simply replicate a vuo file the same as yours (Make Color Layer patch only) I don't get the bug.

But when I'm working on sub compositions used in my own Vuo files I consistently have this problem. See screenshot. Attached a sub-composition for you to examine. Try creating an output called acceleration. Not possible for me, Vuo will always append the lowest number not used by another output port already. Even if I delete all the output ports first.

Workaround: Instead of Filter Control or Filter and Scale Control, you can use Get Control Values -> Are Equal, as in the attached composition.

I agree that it should be more obvious how to do an exact match instead of a partial match on the control name. Would people still want to do a partial match sometimes? That would affect our implementation.

@DRDN, I'm glad you were able to find and delete the problematic node. If you still have the node, could you attach it to this bug report so we can figure out why Vuo crashed? In fact, it would help even more if you could provide all of the nodes you had installed, in case the problem involves multiple nodes.

(We tried turning this Flashes composition into a subcomposition but couldn't reproduce the problem.)

@Kewl, thanks for the suggestion about AppCleaner. It seems like a useful tool in general, although in this case AppCleaner missed the folders where the problematic node would have been installed (either User Modules or System Modules). We looked into how the Vuo app could inform AppCleaner about those locations and, not finding any documentation, have asked the developers.