hm…you didn’t scale those screenshots down so that we can’t see anything, did you? probably that was the forum, though i thought we just had that fixed recently.
for now please upload in a .zip file again…
first off: it is not your fault, it must be indeed confusing if you’re not into all the details. a similar question was asked recently: https://discourse.vvvv.org/t/13764 and not quite satisfyingly answered…
first, here is how it works in your case:
put the files that come with the animator contribution in this directory:
then in Root reference:
now how should you know? the idea here was that everyone knows:
files ending in .fx are effects and therefore go into \effects
files ending in .dll are plugins and therefore go into \plugins
files ending in .v4p are modules and therefore go into \modules
then of course there may be contributions that come with both .dlls and modules and this already gets weird. thats what we introduced Packs for, which can include that structure internally and the user doesn’t need to know about internals… drawback here: packs need to go in the \packs directory in the vvvv root directory.
i hope this explains a bit of the situation and helps you get going.
my method is using symbolic links for packs I’m developing and vpm vpm for deployment. I’d suggest keeping the pack structure even if you only have plugins or modules so vvvv won’t go crazy.
Other thing I notice here though that nodebrowser apparently will skip any node from packs folder not in direct neighbourhood of the working v4p, not starting with an upper-case latin letter (1st world problem, just sayin’)
@joreg is there an appropriate wiki page for all that to go on? I’d think it good to add the DX11 shader extensions too. I don’t think it’s really documented at all atm, and which means even experienced users don’t necessarily know: https://discourse.vvvv.org/t/14049