Reality: If you're a project manager charged with keeping track of various branches - kind of like what a AAA studio would encounter - then, perhaps. Misconception: "Version control systems are difficult." You do not have to be a programmer to use these well enough to do your job. I would like to add, at this point, that just because a programmer uses something does not mean that it's simply not a tool for artists as well.ĮDIT concerns) - Modern version control systems have a generally user-friendly front end (TortoiseGit and TortoiseSVN are two such front ends I have direct experience with) that insulates the user from really technical stuff and lets you easily perform the basic tasks (commit, checkout, etc.) It's incredibly easy, many consider it intuitive, and the installers typically don't ask you difficult/technical questions. Joe the Artist has been saved by an archival system intended to support an entire team, not merely a programmer's tool.
#Smartsvn how to revert software
What if Joe the Artist's best friend comes over to his house, downloads some malicious software that erases Joe's hard disk? Not much of a problem if Joe has committed his work to a remote repository he would have to re-setup his computer, and checkout his little branch of the project. Reality: False! Version control systems exist not only to store assets and information about the things that changed, they exist to provide a backup point. Misconception: "Version control systems are only for programmers."
#Smartsvn how to revert full
Often, the reason cited is complexity: "a version control system is overly complex compared to simply putting a file in a folder." This is false in most version control systems, it's easier - you keep the change where you left it, right click the folder, and select an option to perform a commit to the repository in question, and write a small comment about what you did, for posterity!Įven if a practitioner of a different discipline has a different setup - for instance, an artist commits a UV texture from their sole commit folder, and a programmer pulls it down into a full asset structure - it matters not! The artist sees what they need to. The people who advance this argument are typically graphic artists, though some programmers have also advanced the fallacy. What Dropbox lacks is the ability to create branches, revert to previous changesets, log work, or document comments about a changeset - all useful things whether working solo or in a team. Reality: False! Dropbox provides a shared space for storage and collaboration, yes.
#Smartsvn how to revert archive
Misconception: "A control system will not help me archive my project.