rendering by unc
this is the first beta28 addonpack.
it comes with a bunch of new stuff by unc regarding realtime cubemapping, ie modules for conversions between different formats. and lecloneur spent you all a humble bundle of 30 TextureFX modules. just type his name into the NodeBrowser to see the list.
there is a new TypeWriter (String) based on original code by bo27 that should come quite handy for creating onscreen keyboards.
besides that a series of fixes and new nodes by yours truly vux and woei as documented in the change-log.
remember: everything thats in the addonpack (and more) is open-source: https://github.com/vvvv/vvvv-sdk
anonymous user login
~3mth ago
~3mth ago
~3mth ago
~3mth ago
~4mth ago
~4mth ago
~4mth ago
~4mth ago
~4mth ago
~4mth ago
Small question, is one supposed to replace the normal lib/nodes/nodelist.xml with the addonpack's or not? Should the two be even concatenated?
/edit:
Judging from the content (each file listing only its packages' nodes) obviously they are supposed to be concatenated. Do I have to do that manually or is there some way of installation that I am missing?
The page about-the-addonpack speaks of overwriting any file when asked, but that causes several standard nodes not to be found ( Camera (Transform Softimage) is an example) unless "Opened in Patch".
after extracting the addonpack your directory structure should look like this:
Aaah. Okay thanks, didn't see it like that.
The addonpack folder in the addonpack zip having similar content to the lib folder leaves room for confusion, I will edit the addonpack installation page in the near future - if that's okay - as soon as I think of a way to clear up this possible misunderstanding in a way that is similarly concise as the current installation sentence.
Ah, I'd done this wrong too. Thanks for clearing it up!
I will use this opportunity again to suggest a quest for finding a more intuitive way of installing the addonpack. My estimate is that even when I show exactly how it is done, 25% of the students gets it wrong.
Couldn't we either have a "download and extract suitable addonpack" function in crack.exe or alternatively a little utility that did it that was in the vvvv folder?
I have heard that it has something to do with licenses that it is the way it is, but it would remove quite a lot of frustrations among beginners if it was made easier/more intuitive to install the addonpack correctly