(Case 1082552) Collaborate takes forever.

Hi.

I'm using collaborate on a big project on 2018.3b and collaborate don't work properly. When updating anything, even a minor change, unity re-import the whole project which can take a lot of time. I haven't tried the beta on an other project yet and am wondering if I'm the only one with that issue.

Thanks

 

I just imported a package and got the same issue so it might not be collaborate's fault but the editor re importing the whole project every time we import assets.

 

Issue still present on 2018.3b02. While I didn't have a full reimport, Unity seemingly had to recompile a lot of things after a collaborate update.

 

Issue still present in 2018.3b3. Collab worked but was followed by some kind of recompiling from Unity. If that can help, Unity is using around 17% of the processor and this takes few minutes before it responds again.

 

I just noticed I have a regular conflict with collaborate, a file from a third party asset that wasn't an issue before.

I added it to my .collabignore file. After saving it, unity went back to compiling but this was shorter this time. Though the lack of interface and documentation for the "collabignore" doesn't help and I have no idea if I did things properly.

So far collab still ask me to solve the conflict. Since I don't have a choice, I clicked "choose theirs" on the merge conflict and now have to wait again for Unity to do it's thing.

I join my .collabignore file so you can check it if needed.

I'll keep you updated about what's following.

Code (CSharp):

1. Assets\PlayMaker\Editor\Resources\EditorStartupPrefs.asset
2. # ===========================
3. # Default Collab Ignore Rules
4. # ===========================
5.  
6. # OS Generated
7. # ============
8. .DS_Store
9. ._*
10. .Spotlight-V100
11. .Trashes
12. Icon?
13. ehthumbs.db
14. [Tt]humbs.db
15. [Dd]esktop.ini
16.  
17. # Visual Studio / MonoDevelop generated
18. # =====================================
19. [Ee]xported[Oo]bj/
20. *.userprefs
21. *.csproj
22. *.pidb
23. *.suo
24. *.sln
25. *.user
26. *.unityproj
27. *.booproj
28.  
29. # Unity generated
30. # ===============
31. [Oo]bj/
32. [Bb]uild
33. sysinfo.txt
34. *.stackdump
35.  

 

It didn't work.

 

Update:

I tried importing a simple FBX update from collaborate. I still get the same issue even though the fbx file has nothing to do with scripting.

I also tried to import an update on the same fbx with a unitypackage and it worked fine. So the issue might be from collaborate.

I'd like to know if anybody has the same issue so we can compare notes. Right now, this bug makes the beta barely usable.

Thanks

 

That's great news. I hope we'll get that fix in b4.

Thanks

 

Hi.

Anything new about this? The issue is still present on b5 and nothing have been posted on issuetracker. Considering everything else works fine for us on the beta, I'm concerned 2018.3 will be shipped with that bug.

Thanks

 

Tanks @LeonhardP . I can invite one of you on collaborate but I'll need an extra seat. Mine are all taken.

 

Hi @LeonhardP
I haven't heard back from you. Can you contact me so i can invite you on the project and solve that issue?
Thanks

 

I have to bump that thread back up since the issue is still present on 2018.3b11.