Skip to main content

Art assets

In these two videos, you’ll learn how to use Anchorpoint together with Git-based version control for managing your art and game development assets.

Why using version control?​

You can also manage art assets on a NAS or in Dropbox/Google Drive. That works for simple file sharing, but it breaks down as soon as more than one artist works on the same file:

  • No silent overwrites. On a NAS or cloud drive, whoever saves last wins, and the other person's changes are gone without a warning. Art files like .blend or .psd are binary, so they can't be merged like text can. With Git, Anchorpoint locks a file the moment someone starts working on it, so nobody else can save over it.
  • A full history, not just the last save. Google Drive keeps a limited version history, and a NAS usually keeps none at all. Every Git commit is a permanent checkpoint, so you can go back to any point in the project, not only the most recent versions.
  • You know who changed what, and why. Each commit has an author and a message attached. On a shared drive, all you get is a "last modified" timestamp.
  • No corruption from simultaneous writes. Two people, or two sync clients, writing to the same file at the same time is a common way art files get corrupted on a NAS or Drive. Locking prevents that from happening.

For light projects such as mobile or browser games, GitHub is the easiest choice, especially with Anchorpoint’s GitHub integration that removes most of the manual setup.

This tutorial shows how to set up a GitHub integration in Anchorpoint and create a project. If you already have a Git server running, just skip the first part.

This tutorial explains how to work with version control in your daily workflow, including pulling changes, pushing updates, locking files, and reverting mistakes.