Hello,
Forgive me if this issue has already been addressed but I have had a quick look and couldn’t find anything specificly.
We have a 3-man team of 3D modellers/ visualisers and we’re looking at Unity as a new platform for our work. The problem is that we can’t work on the same project at the same time, and I’m talking about different scenes in the same project. Unity tells us that multiple instances are not allowed. How then should we work in order to avoid duplication of folder structures? I’m sure I read somewhere that Unity was geared towards working collaboratively, and I can’t beleive that only one person can work on a project at a time. We really want to adopt Unity as a working platform but this could eb a stumbling block.
Thanks
So your project exists on the network drive?
Unity creates a “lock” file in the project directory structure and that prevents others from opening the same project.
Usually sharepoint is not the best way to share a project in a team.
What happens if someone deletes or modifies the file?
What happens if Unity messes up the cache files and things will just be broken?
Working with backups is not going to scale well.
You should consider using some revision control systems (GIT or SVN) or the Asset Server (never tried it).
Yes the project is on a network drive. We work on all of our current projects that way and have done for years and we don’t have aproblem. Maybe Unity will mess up it’s cache, I’m not that familiar with the way it works.
I could understand if it won’t let you open the same scene on a different computer but any scene in the project folder is restricted. I’m sure there are work arounds but this would mean having multiple folder structures for one project. I would think keeping track of your assets would be much more difficult this way.
I’ve not heard of GIT or SVN could you elaborate?
I’m not familiar with GIT, but SVN is a revision control system. As I understand it, your project resides on a master server, and everybody with SVN will download a version of that project. If you wish to work on a few specific files in that project, you change them in your local machine, and then commit your changes to the master server.
You have to remember to update your local folder fairly frequently, as you might end up working on a file someone else is already working on. However, you can also choose to lock files that you are currently using to make sure that no one else updates them by mistake.
There’s more to it than I’ve described here, but it’s a fairly solid system. I’m curious if Unity’s Asset Server handles things better… if so, that would be well worth looking into.