not sure how everyone is working but the current way of how gamma is saving bits and pieces is creating continous problems for us.
when we work with beta, unity, unreal or cables, everything belonging to this project is in the project folder. all assets, every plugin, package and in case of beta, even the software. this makes it a no brainer to switch machines, let the creatives checkout the state of the software, deploy the software on to the release machine.
we seem not to be able to establish the same workflow with gamma. a simple websockets bridge project, which worked in university, didn’t work on the machine in the office. confusing error messages saying the websockets package is not installed but the nodes are there…or the other way round. and i’ve never messed with any settings. i would expect when i checkout a patch with no special custom libs of my own, that it just works on a second machine, without doing some black magic.
ok, second case. bjoern did a gamma project for us, julia tried to follow the progress of this project by pulling the git repo. having an identical vvvv installation and also had massive problems getting it to work. It never fully worked on her machine and we gave up. at least the export worked on the release machine.
i really would like to see a way to make projects self-contained. no additional package installation on every machine, no magic auto installation. some way to put everything needed into a folder with local references.
having many things related to a vvvv project (sketches, packages) scattered on the hard disc is a bad idea in my opinion.
and please, don’t regard this as a rant but really a cry for help. i really want to work with gamma next year in a bigger project but confidence due to the many weird behaviours is not high.