Return to Answer

Open-source, centralized

Blender files - I'm not entirely sure if .blend files are binary (they look like it), but I have had no problems adding them to Subversion. Having done a few experiments, the file size increase for changed files appears nominal, so it's not simply copying in the entire file.

Large projects - It works, though it can get quirky. It's definitely able to handle repositories of at least 5.5 GB (total size of repository dir on server; mostly binary assets).

Duplicated Data on the Client - Subversion keeps a duplicate copy of every file in the user's workspace as a pristine copy. The advantage of this is you can do a diff or revert without going back to the server. The disadvantage is that your 10 gig of working files takes 20 gig of disk space.

The ignore list is a property of a directory (simple with a gui, annoying on the command line).

Open-source, centralized

Blender files - I'm not entirely sure if .blend files are binary (they look like it), but I have had no problems adding them to Subversion. Having done a few experiments, the file size increase for changed files appears nominal, so it's not simply copying in the entire file.

Large projects - It works, though it can get quirky. It's definitely able to handle repositories of at least 5.5 GB (total size of repository dir on server; mostly binary assets).

Duplicated Data on the Client - Subversion keeps a duplicate copy of every file in the user's workspace as a pristine copy. The advantage of this is you can do a diff or revert without going back to the server. The disadvantage is that your 10 gig of working files takes 20 gig of disk space.

The ignore list is a property of a directory (simple with a gui, annoying on the command line).

Subversion allows locking of files/assets - which is really helpful if multiple artists and designers work on the same files.

Externals are a great way to handle shared (e.g. library or base) code between projects.

Open-source, centralized

Blender files - I'm not entirely sure if .blend files are binary (they look like it), but I have had no problems adding them to Subversion. Having done a few experiments, the file size increase for changed files appears nominal, so it's not simply copying in the entire file.

Large projects - It works, though it can get quirky. It's definitely able to handle repositories of at least 5.5 GB (total size of repository dir on server; mostly binary assets).

Duplicated Data on the Client - Subversion keeps a duplicate copy of every file in the user's workspace as a pristine copy. The advantage of this is you can do a diff or revert without going back to the server. The disadvantage is that your 10 gig of working files takes 20 gig of disk space.

Quirks - Adds an .svn folder to every directory in the entire repository hierarchy. Can be confused (sometimes fatally) by relocating the repository in the filesystem. The ignore list is a property of a directory (simple with a gui, annoying on the command line).

Open-source, centralized

Blender files - I'm not entirely sure if .blend files are binary (they look like it), but I have had no problems adding them to Subversion. Having done a few experiments, the file size increase for changed files appears nominal, so it's not simply copying in the entire file.

Large projects - It works, though it can get quirky. It's definitely able to handle repositories of at least 5.5 GB (total size of repository dir on server; mostly binary assets).

Duplicated Data on the Client - Subversion keeps a duplicate copy of every file in the user's workspace as a pristine copy. The advantage of this is you can do a diff or revert without going back to the server. The disadvantage is that your 10 gig of working files takes 20 gig of disk space.

The ignore list is a property of a directory (simple with a gui, annoying on the command line).

Open-source, centralized

Blender files - I'm not entirely sure if .blend files are binary (they look like it), but I have had no problems adding them to Subversion. Having done a few experiments, the file size increase for changed files appears nominal, so it's not simply copying in the entire file.

Large projects - It works, though it can get quirky. It's definitely able to handle repositories of at least 5.5 GB (total size of repository dir on server; mostly binary assets).

Duplicated Data on the Client - Subversion keeps a duplicate copy of every file in the user's workspace as a pristine copy. The advantage of this is you can do a diff or revert without going back to the server. The disadvantage is that your 10 gig of working files takes 20 gig of disk space.

Open-source, centralized

Blender files - I'm not entirely sure if .blend files are binary (they look like it), but I have had no problems adding them to Subversion. Having done a few experiments, the file size increase for changed files appears nominal, so it's not simply copying in the entire file.

Large projects - It works, though it can get quirky. It's definitely able to handle repositories of at least 5.5 GB (total size of repository dir on server; mostly binary assets).

Duplicated Data on the Client - Subversion keeps a duplicate copy of every file in the user's workspace as a pristine copy. The advantage of this is you can do a diff or revert without going back to the server. The disadvantage is that your 10 gig of working files takes 20 gig of disk space.

Quirks - Adds an .svn folder to every directory in the entire repository hierarchy. Can be confused (sometimes fatally) by relocating the repository in the filesystem. The ignore list is a property of a directory (simple with a gui, annoying on the command line).