Search Unity

Best Practice: Never have more than one Unity Editor instance open?

Discussion in 'Unity Collaborate' started by AdamKane, Oct 31, 2018.

  1. AdamKane

    AdamKane

    Joined:
    Dec 3, 2012
    Posts:
    130
    Hello,

    From the Collaborate Expert's Guide:
    https://docs.unity3d.com/uploads/ExpertGuides/Collaborate_-_Keep_The_User_Safe.pdf



    Is this guidance still true? I almost always have at least 2 (and often 3) instances of the Unity editor open, working on things in parallel. (Part of this is driven by the need to wait for Collaborate operations to wrap up.)

    Also, can anyone expand on "Collaborate reads from one javascript package location" and the under-the-hood details of how that plays out poorly when multiple instances of the Unity editor are open? In general, Unity seems to work great with multiple editor instances open on the same machine at the same time.

    Thanks,
    Adam
     
    Last edited: Nov 2, 2018
  2. Prodev101

    Prodev101

    Joined:
    Aug 6, 2010
    Posts:
    49
    Best option is not to use collaborate right now.. Its not finished!
     
    Marc-Saubion likes this.
  3. ryanc-unity

    ryanc-unity

    Unity Technologies

    Joined:
    Mar 23, 2016
    Posts:
    1,416
    Hi @AdamKane! Sorry for the delayed response. It is on my plate to update this guide since a few things have changed under the hood from when Collab first launched.

    As of 1.3.0-preview.2 of the collab-proxy package, you should not have any issues opening two or more instances of Collab-enabled projects at the same time, as long as they are not the same project from the same file directory, since Unity doesn't support that. However, from personal experience testing using Unity Hub, I haven't run into any Collab-related issues when opening 2-3 projects in different or similar versions of Unity, going as far back as 2017.4.

    The initial concern for not suggesting that multiple instances of Collab-enabled projects be open at the same time was because each project was referencing the same javascript package location when loading the Collab Toolbar and History Window. This could result in unexpected behavior, especially if the projects were open in different versions of Unity, each one potentially trying to load a different version of the javascript package. Now, with Unity Hub (and even more so with Collab becoming a package), those folder locations are separated by version and should not be overwritten unexpectedly.
     
    AdamKane likes this.
unityunity