Transferring scenes seems to break connections.

Questions & Answers
1

Hello all!

I have been having trouble with importing scenes in Unity. My friends and I are all working out of one Unity project and we normally just send each other new or changed scene files when necessary. The problem we are having is that when one of us makes a change to the models/objects in a scene and sends it to the others, certain connections for meshes, scripts, textures, or all three are broken even though all of those things exist in the project’s folders somewhere. Essentially, all we want to do is be able to copy a scene file to another computer and continue working with it. For example an artist can set up a scene with all the meshes and textures and then pass it to a programmer to add scripts.

We have tried:

  • Pro vs Standard versions of Unity
  • Copying just the scene file into the scenes folder
  • Importing / exporting the scenes as packages
  • Turning Unity meta files on and off
  • Saving objects as prefabs before copying the scene

Has anyone else had this problem before? Is this method not something that should be done? Is version control the only way to get around this issue? Although from what I’ve read version control can have its own nightmares.

Thanks!

2

They need to be in the exact location in all project folders. Have you considered working from one set of files in a place you can all access simultaneously?

It seems the editor saves its own version of what is going on with public variables. I work between two computers and despite the scene being the same on each and everything being in the same location I always notice differences between the two, specific to each machine.