cloudwalker

This is extremely unfortunate, was looking forward to swapping to this system once this was complete. Guess I'll look elsewhere. This kind of thing is non negotiable, hopefully you re-prioritize in the future.

Is there any update on the possibility of such feature KristOfMorva suggested? Ease of repo management is critical. On the fence to convert to Plastic completely and this is the last thing preventing! If something easier is coming in the future, we can get by with archive for now. Could you share a archive script that would archive all .fbx,png (any extension list really) except the last N revisions? thanks!

Today I tested archiving a 1gb binary file on the cloud, I've yet to see the dashboard show the 1gb drop on my usage. How long should it take to reflect? Archiving files should reduce cloud usage correct?

Ah, if this works with just the Plastic client alone then that's fine. I'll give that a go. Thanks for the shout.

I tested two things that I wanted to be sure that worked in plastic like they do in git. 1. Updating a store asset package 2. Moving a folder or other files around (re-organizing) After checking in the changes post update or move, I test an Update on a 2nd machine to see how it behaves. After the update is finished, there are an equal amount of deletes / adds for every file that was updated where there should be absolutely zero. It could be due to the post checkin adds / removes screwing up the Update on the 2nd machine - not sure. Not experienced with plastic scm yet. Like you said disabling the Unity Plugin before updatingmight fix the issue? When I use git to pull down the updates that have many file updates or folder moves it always completes cleanly even if Unity is open at the time.

Any update on this one? I'm currently evaluating a switch from github due to repo size issues. These operations work fine in git but fail miserably in plastic. Folder moves and inplace file updates like Garrett mentioned are not handled correctly on another machine that pulls down the update. The machine that is updating their workspace will make a delete and copied (new) for every file that was deleted and moved, or updated by a package update. Almost seems like an order of operations issue, or perhaps Unity is trying to import the file changes while the workspace update is still happening in the background.