so here is why your patch is a bit problematic: you create a new enum in each “bg” subpatch instance. So basically for vvvv, there are 4 CreateEnum nodes, some of them get evaluated, others not, and at some other point in your patch you select the enum from a global list by referring to it by name. The big question would be: which one does vvvv pick?
It looks like in this example you didn’t get lucky and it picked an enum that didn’t get evaluated yet (as the surrounding patch didn’t get evaluated).
So this is a pretty special case, but I can imagine 2 solutions:
One Enum: In your case the enums all come with the same entries. They all refer to the same directory. So, in this case, you could create just one enum and refer to that. In the attached zip open root_1Enum to have a look at that approach.
Private Enum: The other solution would be to actually create an enum for each subptach instance, but somehow not refer to the enum by name. In the example, the enum io box now is connected directly to the CreateEnum node to make sure that it’s about this enum type instance (and not another one that goes by the same name). In attached zip open root_privateEnum.
THIS IS ONLY WORKING WITH NEWEST RELEASE CANDIDATE:
enumSolutions.zip (9.8 KB)
didn’t zip the pics again, so paste the patches into your original folder please.