"sharing" unity scenes with co-workers

Greetings all,

So hopefully this is an easy question to answer. I need a way to share my entire Unity Scene with a co-worker. So if I make some changes, I can send him the scene (and associate files), and he can just open it up and look at everything in the same way I was.

We both have the same folder structure, but for example, if I make a new scene with assets from “C:\Unity\Simple Tests\Assets\Standard Assets\TEST1” and I send him the “TEST1” folder, and the *.unity file, and he places them in the exact same folders that I had them (other than Drive Letter, he has D:\Unity… but that really shouldn’t matter), the scene doesn’t open fully. Some assets will be there, but others won’t.

As such, I have to send him the entire project files "C:\Unity\Simple Tests" which is nearing 600mb atm - and this is a ridiculous waste of time, especially to just show small changes.

What am I doing wrong? is there a way to export a full scene with all files linked properly?

Thanks for your help.

the only way to do that is to export a package for the scene including all referenced things that he then can import overwritting his current, at least if you work with the free unity.

With Unity Pro you could enable VCS that would solve part of it, you could use VCS then for example.

With Asset Server licenses it becomes a more or less none topic.

A lot of data is stored in the Library for the project, particularly for scripts on prefabs.
Exporting a package or using the asset server is the best method.

Thanks for the replies, but unfortunately this still isn’t working.

Exporting a package works better than just zipping the files that you would think are necessary, but it still isn’t 100% perfect. Some links are still broken, mostly between scripts and objects.

I can’t believe how poorly designed and tested this system is. How are 2 (or more) people supposed to work on the same project (on different comps) without having to dish out $500 for some ridiculous Asset Server? All this ‘meta data’ that gets saved about files and links between them is so silly and unnecessary. Uhg.

This must be some kind of bug. I have done this multiple times and have yet to encounter any problems; for me packages have been 100% perfect.

I always just zip up my project’s folder to switch between my home and work computer and it has always worked perfectly.

Hopefully this is the case. I will attempt it a few more times.

Yes, I know this works, but my project folder is nearing 600mb, and I’m not just transfering the files on a portable drive, I have to send it online. And to show just a small change, uploading/downloading 600mb+ is alot of wasted time.

This has been my biggest problem too. As soon as thanksgiving is over I’m going to give the 2.6 trial a run for its money and see if version control and media sharing has inproved.

It says it has support for systems like SVN in the new features list :).

From what I can tell 2.6 Indie has no version control.
You need the pro version I’d guess.

Exporting packages works fine for me as well.