We currently use PlasticSCM in Gluon mode for our Asset server, which comes with a few advantages like being able to download single assets or folders, file locking etc. Previously I've used both SVN (ancient as it is) and Git for art assets, and I think neither works very well. Honestly, much more than version tracking,…
Really interesting discussion here, and I'd totally agree. We have a feature (currently in alpha), that supports Multiplayer Blender. A user can click on an blender compatible asset in the platform, and it launches a blender session within the browser. Multiple users can join this same session to collaborate together. Some…
Add one more person to that team, and you're now paying through the nose :D Perforce seems nice, but the cost turned us off of it. As Poopipe says: version control already exists, try to add something on top of that that makes versioning and reviewing visual and fast. Tie project and task management into it. A few are…
Perforce is hands down the best currently available version control for art resources - for code I'm not really up to speed enough with Git to say which is better - I know SVN is a shitshow for everything though because I've been forced to use it for the last 5 years. p4 and git can both be cloud or local and have…
There's a couple of issues. 1: no studio is going to be happy hosting their data somewhere they don't have full control. AWS or Azure is usually okay for outsourced content once you shout at legal for long enough but even that's a hard sell. 2: studios aren't interested in adopting anything that can't be plugged into their…
Really helpful feedback here all! I want to quickly summarize what I'm hearing, and then suggest the solution I'd like to build. I'd love your feedback (if you'd indulge me a little bit longer :) ) Summary of pain: Reviewing assets together as a team and leaving in-context feedback on assets is a pain point. Quickly seeing…