Git issues with 4.3

Questions & Answers
1

We’ve been using git for a while now, and it’s worked fine with Unity with Version Controlled Meta Files turned on. However, some time after upgrading to 4.3, a co-worker pulled a new version of the code, and some (but not all) of our scripts, prefabs, and NGUI atlas references were broken (e.g. “script not found”, instances of prefabs appear red in the hierarchy and no longer link back to the prefabs). They can be restored, but it’s quite a chore to do so.

I noticed that with 4.3 came the option for Visible Meta Files and Hidden Meta Files. It seems that Visible Meta Files was selected for my project by the migration to 4.3. Is this the correct setting for using git? And if so, what might cause this behavior?

Thank you.

2

I expect one of your co-workers accidentially set this option wrong. Did you also check you all use the (exact) same Unity Version?! Don’t know if it really bother, but you should avoid different versions in any collab software!

I noticed that with 4.3 came the option for Visible Meta Files and Hidden Meta Files. It seems that Visible Meta Files was selected for my project by the migration to 4.3. Is this the correct setting for using git? And if so, what might cause this behavior?

Yes, that’s correct. Please refer to the releasenotes: http://unity3d.com/unity/whats-new/unity-4.3

Asset Pipeline: .meta files are now always turned on. From Project Settings → Editor you can choose to hide them if you are not using version control.

3

The problem for us was that the *.meta files were not added to the repository.

Try this : git - Ignoring folder meta files on version control - Stack Overflow

(the default gitignore file in the repo had *.meta in it)