I have a project that's recently been exhibiting some dismaying behavior: every public field that is assigned to in the inspector (both reference and value types), in all scripts and all scenes, is being set to its default value when the project is built. This could be build breaking to other team members who have only some of my changes and not others. This is super bad if I don't realize that I have not checked out a prefab and start editing it because even after restarting Unity to fix the perforce state, it results in local changes on my disk while Unity thinks there are no changes to the prefab I edited and does not try to check it out or otherwise warn me in anyway. When this happens, the version control settings indicate that I am indeed still connected to my Perforce server, and hitting the refresh button or connect button again does not fix the situation, only closing and re-opening Unity fixes it. checked out become editable and no version control operations can be done on the prefab as all version control right click menu items are gray. However, after between a few minutes and a few hours.some. I won't guarantee this resolves the issue for you, but hopefully this helps you out or at least gives you a path to start looking further along.Upon starting Unity, all prefabs are checked in and are not editable unless you do a check out on them as expected. At this point I submitted the default change list and synchronized the other machines and it loaded properly without the errors. This creates file type changes for all of the. P4 edit -t binary '//depot//Assets/./*.mat'

P4 edit -t binary '//depot//Assets/./*.meta' I then went through the project and used the command line: To fix current ones I first made sure my default change list was empty.

In any case, as a work around, I modified my P4 server to recognize both of these file types as binary using the 'p4 typedef' admin command and editing the displayed file with the following: The meta files being text should be fine, but it seems my P4 server is modifying the end of line (I believe it's a P4 admin setting you can change to support different OS files).

This might be tied to the versioning settings 'Asset Serialization' option as well (although I haven't had time to experiment with modifying that and submitting new files). After some experimenting I believe the issue is related to the file types being set to text for the meta files (and maybe for the material. I encountered the same error relating to the meta and mat files.

Invalid Serialized File Header Unity