We have asset serialization set to “Force Text”.
Our projectsettings.asset was in text format on 4.2.1
We upgraded to 4.3
The current projectsettings.asset is in binary. If we make a change and do File->Save Project we get the following error:
“Could not serialize text file projectsettings/projectsettings.asset because an error occured - we probably ran out of memory.”
Memory on the system is not an issue (tons of memory in Activity Monitor + the bug happens even after a reboot).
I haven’t yet seen the memory issue, but we are seeing that on upgrade to 4.3, our ProjectSettings/ProjectSettings.asset is now in binary even though “Force Text” is set. Would like to see this fixed.
That’s a good point bagelbaker. Looking back in my source control history for the file, it’s obvious now that the 4.2 → 4.3 upgrade converted it into a binary file for no good reason, even though our project is set to use text serialisation for assets. I suspect it’s that disparity that’s making Unity moan now - it’s found a binary asset when it was expecting a text one. I will maybe see if I can’t revert the file to the 4.2 version and then reapply all of our Player changes since then.
The binary was contained in scriptingDefineSymbols [0] and metroCertificatePassword in my case.
Therefore, I reset WindowsStore:Cerficate.
And the following editor scripts were run.