Search Unity

Proper way of moving project to other machine/system

Discussion in 'Editor & General Support' started by sqallpl, Mar 18, 2019.

  1. sqallpl

    sqallpl

    Joined:
    Oct 22, 2013
    Posts:
    384
    I know that it was discussed many times before but things are changing from time to time and it would be great to get some up to date info.

    Is this a proper way of moving/opening a project on a new machine/system?

    1. Copy the whole project directory without Library and Temp directories to the new machine/system.
    2. On the new machine/system open the project in the same version of Unity.
    3. Wait until the re-import and database building process is finished.

    Is that right or maybe I'm missing something?

    Thanks.
     
  2. MadeFromPolygons

    MadeFromPolygons

    Joined:
    Oct 5, 2013
    Posts:
    3,978
    if your using source control then just clone onto the new machine.

    If your not using source control, then good god that is the first thing to do before worrying about transfering.
     
    sqallpl likes this.
  3. Baste

    Baste

    Joined:
    Jan 24, 2013
    Posts:
    6,332
    It's correct.

    Using source control is a nice way to avoid making a "my power went out and now my game data is gone" post in three months.
     
    sqallpl likes this.
  4. sqallpl

    sqallpl

    Joined:
    Oct 22, 2013
    Posts:
    384
    Thanks for the advice.

    We are using source control (Library and Temp are ignored) and additionally regular, independent 'oldschool' project backups.

    Generally I was looking for a confirmation that launching the project without a copy of the Library folder is a proper way.
     
  5. Baste

    Baste

    Joined:
    Jan 24, 2013
    Posts:
    6,332
    Yup.

    The files you need are:
    - The Assets folder
    - The Packages folder
    - The ProjectSettings folder

    Everything else will be regenerated by Unity. In particular, you don't need any of the standalone files that are generated outside of those folders (like the .csproj files or the .sln files).
     
    sqallpl likes this.