quick report
a few students today didn’t have Freeframe nodes in their NodeBrowser, but if they opened a previous patch, the nodes would appear (just not in NodeBrowser).
Having a similar issue with plugins back at the studio now. I can drag the dll in from the plugins folder and everything works fine, but not appearing in NodeBrowser.
Something to do with the new caching perhaps?
hei sugoku,
yes, this is the new behavior. basically don’t ever put anything into vvvvs \plugins, \effects and \modules directories. and even in the \addonspack directory only put the official addonspack, nothing more.
put your own stuff anywhere else and reference that directory from your root.
please also see nodelist (vvvv) for details.
freeframes and vsts still behave differently: those you’d have to put in vvvvs \freeframe and \vst directories and they show up on next start of vvvv or after pressing Shift+Alt+E “Rescan for Externals” which only scans for freeframes and vsts!
Maybe it would be useful to have this ‘regenerate nodelist’ functionality in the menu somewhere?
ah cool sorry
thanks for the detailed response!
just to confirm. where does this leave ‘rescan for externals’ ?
i’ve edited my above post, since its info was not correct, regarding ff and vst. i.e. the nodelist-generation stuff is actually only useful if you have your own directory full of plugins, modules, effects and vvvv takes too long to start. then you can generate a nodelist for this directory and vvvv will only parse that file instead of the whole directory.