I mostly work on my PC version of Unity 3 and then sync my project folder to my MAC so that I can compile and build to my iPhone. The reason I do this is because my PC is my desktop and my MAC is a laptop, so I’m much more comfortable working on my desktop.
My question is which files of my project folder should I NOT sync between computers? I assumed I should leave the “library” folder alone on both computer and only sync my assets folder and my project/scene files. Is this the right thing to do or can I safely sync everything in my project folder (including the library folder) without having to worry about messing something up?
Even if you aren’t going to use SVN to sync the two, follow the directions in that link. Set your project up for external version control and ignore the files it tells you to ignore (everything in the library folder except for a specific list of 9 files) when syncing.
thats a rather bad idea
without VCS, using the list from there will not work out as you are missing all guid and it will just not work on the other side anymore as it will lose any releationship
I mean no offense dreamora, but you may want to actually read the link. You do not need to actually use SVN to use the “external version control” system. You can use it with any form of external version control (including manually syncing files between two computers).
All of the required information about asset relationships is stored in the .meta files and the short list of library sub-files listed on that page.
In fact, as long as you have EVC enabled (and have the .meta files) you do not need to sync the library folder at all. You merely will lose any project and build settings (including inputmanager). I certainly don’t suggest ignoring the 9 files that Unity suggests syncing though; at the very least you’ll lose all of your input settings.
I know in 2.6 the .meta files contained the linkages. It was still somewhat messy, and prone to error, and would probably require a fair bit of trial and error, but you can retain the IDs and references without including the Library folder, so long as you copy the .meta files as well.
Right you don’t need to use SVN
but you need to own Pro and enable VCS support.
If you don’t have VCS enabled or are not on Pro (it was nowhere stated that he owns unity pro and iphone pro, which is a requirement) then you must sync the whole project folder
also, in this case it basically makes no difference: it will not work when you use different project types, you can’t sync a desktop / web player project into an iphone project and vice versa, as the assets require reimporting and changes upon importing into iphone / desktop from the other side
so he can basically copy the project over once and then switch the project type so he can work on it as an iphone project
but beyond that point he will have some problems syncing / realize it to be impossible
Yeah I figured it would be a pain, especially when working on 2 different platforms.
I do not own pro yet, I’m currently using the 30 days trial version. I think my best bet is to create packages which I would then import in my project on the MAC. Not as quick as syncing correctly with VCS support but at least I won’t run into weird problems that way!
Really, really bad experiences using External Version Support + SVN over Mac and PC… I’m just not 100% sure the problem is on the multi-platform or just unity messing up stuff with regular binary scenes. I just know “merging” on Unity’s VCS is bad: http://answers.unity3d.com/questions/1235/version-control-workflow
merging is impossible if we talk about scenes and prefabs.
thats why you add prefabs to scenes, 1+ per user and then these users only commit their prefabs … this will autoupdate the scene
And this isn’t about VCS. I own an asset server license since 2.1 or so and still do and the asset server stuff can’t do this either nor can the asset server even branch
