I’m currently working with multiple machines and using an external file mirror program to match the content on all machines.
what do you mean with content?
during patching on a multiple machine setup i usually have the projectfolder only on ONE machine, shared in LAN with write access.
same with the betafolder (vvvv.exe, modules).
*the big advantage:
**you keep everything consistent.
**you don’t have to have an eagle’s eye on several modulesfolders.
++(perhaps you made a little improvement on a module of pc#3 and change a shader on pc#5, you know its almost impossible to keep track of this in “war patching”-situations on construction sites)
**assumed vvvv/project are located on pc#1, you should quit your rootpatch on this machine at last. otherwise you can’t save the patches on pc#2-pc#n anymore.
**you can’t use plugins in a “LAN started” vvvv.exe. no problems with other externals though. i already claimed this being a bug. joreg doesn’t think that this is important at all…
**when aborting node creation a “LAN started” vvvv.exe takes a break of ~10 seconds. i can live with that.
**perhaps some little issues i don’t remember right now
only when finished patching i mirror both beta- and projectfolder on all machines and run them local.