I updated to 5.6.0b3 and the compiler started to output several warnings regarding obsolete API calls.
I wonder whether the API Updater is designed to update these automatically and thus it’s a bug that it don’t? In case it’s a bug, do you want me to submit a separate bug-report for each warning or one report containing all warnings?
'UnityEngine.AI.NavMeshAgent.Stop()' is obsolete: 'Set isStopped to true instead'
'UnityEngine.AI.NavMeshAgent.Resume()' is obsolete: 'Set isStopped to false instead'
'UnityEditor.SerializedObject.UpdateIfDirtyOrScript()' is obsolete: 'UpdateIfDirtyOrScript has been deprecated. Use UpdateIfRequiredOrScript instead.'
'UnityEditor.TextureImporterFormat.AutomaticTruecolor' is obsolete: 'Use textureCompression property instead'
'UnityEngine.Camera.hdr' is obsolete: 'use Camera.allowHDR instead.'
'UnityEditor.TextureImporter.linearTexture' is obsolete: 'linearTexture Property deprecated. Use sRGBTexture instead.'
Afaik, the script updater will only update those methods which are flagged with [UnityUpgradable] (or something like that). Those will be updated automatically when you open your project and let the updater do its work.
If you have a custom DLL which links Unity.dlls and which uses methods which should be upgraded, you have to do it manually. The editor will give you warnings about it and you have to check yourself in your solution for the warning.
Obsolete and deprecated methods aren’t updated automatically. Most times you have to decide whether or not you want to still use the old methods or not. And most times it’s pretty straight forward to use the new methos (e.g. there was a typo in the method name, has now a different parameter type or something like that), but sometimes (e.g. like the changes made to the particle system) you have to do a bit more, as the script updater can’t exactly know in all cases what you actually want to do.