Search Unity

Project assets missing when downloading from Collaborate

Discussion in 'Unity Collaborate' started by pccross, Nov 10, 2018.

  1. pccross

    pccross

    Joined:
    Jun 20, 2015
    Posts:
    93
    Been using Collaborate for about a year now. I've become accustomed to whenever I upgrade to a new minor revision of Unity (i.e. 2018.2.1 to 2018.2.2), I always start fresh, and download my project from Collaborate into Unity.
    For some reason, recently, I see sporadic behavior of the download looking normal (takes about 3 hours for a 25GB project), and I get no errors. When done, the Unity editor is open with my project name in title bar, but no Assets or Scenes exist. I looked at the Windows directory, and the Assets folder is completely empty, as well as almost every other project directory. The directory size shows as ~350MB though, instead of 25Gb.
    When I go to delete the directory, the 'recycle' action takes a number of minutes and appears to being deleting many gigabytes of files.
    Are my files getting hidden somehow?
     
  2. pccross

    pccross

    Joined:
    Jun 20, 2015
    Posts:
    93
    Some more info.
    I noticed there is a folder called "Projectname"\Library\Collab\Download\Assets" where I'm seeing all my intact assets.
    So I guess the real question is when I 'open project from cloud', and pick my project, why is everything downloaded to there, but nothing goes into real Assets folder, even though project opens successfully?
     
  3. ryanc-unity

    ryanc-unity

    Unity Technologies

    Joined:
    Mar 23, 2016
    Posts:
    1,317
    Hi @pccross! That is strange that Collab is succeeding in downloading your assets (since they're in your Library/Collab/Download folder) but not putting them in your actual directory. The quick fix would be to just copy-paste your assets from Collab/Download into your project directory, but I would check first after you attempted to download your project from the Cloud if there were any errors in the Editor log (or Hub log, if you were using Unity Hub to download from the Cloud). Were you downloading your project into 2018.2.2?
     
  4. KodiakJack

    KodiakJack

    Joined:
    Nov 22, 2018
    Posts:
    3
    I'm on 2018.2.10f1 and having the same issue, the collab is downloading too \Library\Collab\Download\ but not moving to the main directory. Manually moving them makes unity see it as all new files, and then wants you to push all of them, it seems there might be an issue with whatever is actually moving them over.
     
    Wintermute- likes this.
  5. KodiakJack

    KodiakJack

    Joined:
    Nov 22, 2018
    Posts:
    3
    I also can go deeper C:\project\Library\Collab\Download\Library\Collab\Merge
     
  6. KodiakJack

    KodiakJack

    Joined:
    Nov 22, 2018
    Posts:
    3
    since I have the time I'll go through what all I did to try and remedy it. I re-downloaded through the collab button, relinked, reimported(many times), cut and pasted the files from download, cut and pasted only the meta files, cut and pasted only the asset folders, tried opening the file folder level with the assets directly, removing the main assets folder in hope when it recreated it would pull them in. re-downloaded into a new folder completely, copied all files over while it was closed(wouldn't open), copied all files over while open
     
  7. Wintermute-

    Wintermute-

    Joined:
    Sep 5, 2017
    Posts:
    24
    We have the same problem today after downloading our project to a new computer using Collab. The project is eight months in development so I hope there is a way to solve this soon. I can't risk too many tests I am afraid we will break what is already in Collab.
     
    Last edited: Nov 30, 2018
  8. ryanc-unity

    ryanc-unity

    Unity Technologies

    Joined:
    Mar 23, 2016
    Posts:
    1,317
    Wintermute- likes this.
  9. GorkaChampion

    GorkaChampion

    Joined:
    Feb 6, 2018
    Posts:
    102
    I'm getting this issue all the time now (before was randomly). Basically we can't load and start working on our project right now. We have tried several times on a Mac and Windows. We are using 2018.3.b.12
    I see the assets in Library\Collab\Download but if I move them to assets, do I have the issue of having to publish all of them as new as referred above? Whats the solution?
     
  10. ryanc-unity

    ryanc-unity

    Unity Technologies

    Joined:
    Mar 23, 2016
    Posts:
    1,317
    Hi @GorkaChampion! You mentioned that you're using 2018.3b12. In the Package Manager when you have your project opened where it's all downloaded correctly, are you using v1.2.11 of Collab? If you are on 1.2.11, have you tried updating to 1.2.15 then publishing your changed manifest.json to see if that resolves your issue of downloading your changes to a new machine? If they don't then please submit a Support Ticket with a link to this thread and all the details that you have around the size of your project, the types of assets that you have and the Editor logs of your project that are generated while trying to download your project.
     
  11. GorkaChampion

    GorkaChampion

    Joined:
    Feb 6, 2018
    Posts:
    102
    OK, I upgraded to 1.2.15, published changes and downloaded again a new project and now it worked fine and I can see all the assets. Great.
    Can be the issue caused for having more than one unity editors opened at the same time (different projects). I read somewhere that it was better to have only opened one project. Is this limitation actually true? Anyway some of the tries I made I was running only one editor.
     
    ryanc-unity likes this.
  12. ryanc-unity

    ryanc-unity

    Unity Technologies

    Joined:
    Mar 23, 2016
    Posts:
    1,317
    I'm glad to hear that it's working for you now! This limitation actually isn't relevant anymore as of 2017.4, especially if you use the Unity Hub to install and open different projects in different versions. I'm in the middle of updating our Collaborate - Keep the User Safe guide to remove all outdated information. Thanks again for pointing this out! And let us know if you run into anymore issues.
     
  13. IsntCo

    IsntCo

    Joined:
    Apr 12, 2014
    Posts:
    141
    Did you guys never actually fix this?

    I am on Unity 2017.4.12f1 - pulling an existing project onto a new computer results in the download being placed in /Collab/Download/ and leaves an empty open project after the import. If you try opening /Collab/Download it imports all of the files, but then Collab wants to push (in my case, thousands) of new 'changes' to sync back up with Collab.
     
  14. StaceyH

    StaceyH

    Unity Technologies

    Joined:
    Apr 11, 2018
    Posts:
    44
    @Appminis This should have been fixed. We have someone on the team taking a look to see if they can reproduce the issue.
     
  15. dtakahas

    dtakahas

    Unity Technologies

    Joined:
    Oct 22, 2015
    Posts:
    83
    @Appminis I tried this with your exact version today and got a reproduction I believe.

    If I opened a cloud project using Unity Hub and choosing 2017.4.12f1, everything was fine.

    If I used the regular 2017.4.12f1 launcher, I saw something similar to what you saw. It was definitely messed up.

    So something in the launcher is not right. We'll investigate that. Can you confirm that you weren't using the Hub? If you weren't, using it would be a possible solution for now.
     
  16. IsntCo

    IsntCo

    Joined:
    Apr 12, 2014
    Posts:
    141
    @dtakahas Correct, was not using the Hub.
    I can try using the Hub on the new computer, but in an attempt to sync everything up, I pushed a commit with those few thousand of changes from Computer #2. I have not pulled them in on Computer #1 yet. Is there a way to delete the most recent commit? Because of the weirdness with the initial pull on Computer 2, no amount of going back to older versions/Restoring/Reverting to older commits on Computer 2 results in the files being synced. So I really need to just delete the most recent commit from Computer 2 (the only commit with these issues). I'm fine deleting the full project on that computer and trying again using Hub, but I don't want to mess anything up on the original Computer 1. The project is 30gb, so its heavy.
     
    Last edited: Feb 14, 2019
  17. dtakahas

    dtakahas

    Unity Technologies

    Joined:
    Oct 22, 2015
    Posts:
    83
    @Appminis The safest way to get back to the right state without touching Computer 1 would be this:

    1. Start with a new, clean checkout (using the Hub) on Computer 2.
    2. On Computer 2, use the instructions here https://docs.unity3d.com/Manual/UnityCollaborateRollback.html making sure to do the step that says "To publish the restored version as the current revision in the cloud, click the Publish now! button."
    3. Verify that everything looks right on Computer 2.
    4. Now when you update on Computer 1, there should be no actual file changes pulled. You will jump past the Computer 2 commit you didn't want to pull.

    I know you won't be able to see what you are pulling onto Computer 1 as far as files (it should be none), so if you are worried about that part, please send a Support Ticket and ask us to check the diff to make sure it's clean. We can also follow up with alternate solutions if you'd like.
     
  18. Trys10Studios

    Trys10Studios

    Joined:
    Jun 24, 2013
    Posts:
    45
    I'm not sure if this is going to solve anyone else's issues, but I want to give my experience as I was running into the same issue. My associate saved the project to the cloud, gave me permission to view (through Unity ID), and finally got all that working. Then, I ran into another issue - the one mentioned here - so in my search for a resolution I found the original talks about collab in Unite 2016 and in passing it was mentioned by 'publishing' your project, it is instantly backed up in the cloud. Out of curiosity, I tried downloading from the cloud a project on my own account, and the assets did not show up, so I wrote some text in the collab toolbar (as the speaker did in Unite) and hit publish. I then tried accessing that same project from the cloud and voila, it worked. The assets downloaded and everything was fine. Now I have to wait until the morning to see if that will work for my associate
     
    josi1301 likes this.
  19. NatalieW15

    NatalieW15

    Joined:
    Jul 30, 2019
    Posts:
    11