I am currently working on a game project with about 15 other persons. We have a major problem that is really frustrating us and stops us from working on the important things.
Since we are so many we need to be able to send packets between each other. The problem is that when we export a package and then import it in another project all links are broken. For example if we export a player prefab all scripts are missing, the model is gone and the texture as well. However if we go the the assets folder the files are there and we can assign them again manually. We are also using the Include dependencies option.
This isn’t a huge problem when exporting just a single prefab, but when we export an entire scene it gets messy. Every single object in the scene are missing their meshes, textures and materials. They are still imported to the assets folder but still all the links in the inspector are broken which means someone has to sit and relink all that manually. We only have 10 weeks to work on this project and at the moment we have to waste so much time on this it’s hard getting any real work done.
I have searched these forums for quite a while but cannot seem to find an answer. I’ve seen the question being asked before but the only answer it seems to get is to ‘Include dependencies’ which, as I stated, doesn’t work. A solution to this would be highly appreciated.
Unity3d has some hidden information that probably are not been exported.
Try to enable metadata files, go to Edit->Project Settings->Editor and enable “Enable Meta files”.
I didn’t understand if you are sharing the a project or some packages.
If you have a project, you must use a version control system. Like git, it is a really powerful.
If you are sharing some packages, I belive that it will work first time when you send all files in the same package, but will start to lose reference when you send again smaller packages with only some files.
The best solution is don’t do it, you must always share all files from same package. A workaround is to copy file by file (after enable meta files) directly to the other guy.
I’ve been struggling with this for weeks and I finally solved my problem. I believe that Unity does not always differentiate between different folders of the same name on package export.
For example, I had folders for each of the assets, which contained a subfolder called “mats and textures” in each of the parent folders. It was a nice way of organizing things local to each asset. When I dumped all textures into a single “mats and textures” folder my problem went away.
Solution (In my case)
In the Project window select the assets you want to export. Right-click and then select Export Package. This will export the meshes, materials, etc. In other words, it will export the dependencies (if checked).
Just going to the Assets-Export Package menu option and then selecting the portion of the overall project you want to export does not seem to work. You have manually deselected the dependencies, so the check box at the bottom is meaningless. Actually unchecking it and checking again will select all.
