So, I read the Unity5 AssetBundle changes and understand them perfectly. My problem is that many functions were "deprecated", but the functions seem to still work, and the Unity5 documentation actually uses deprecated functions.
My main concern is how I now, in Unity5, take the catalog of collections and turn them all into my own separate AssetBundles separately? Not only one AssetBundle containing everything, but each built-in own separate AssetBundle?
Ideally, I would use the BuildPipeline.BuildAssetBundle function. But unity5 says that it is out of date. But if you look here: http://docs.unity3d.com/500/Documentation/Manual/managingassetdependencies.html
They use this feature in a manual.
He also says that the CollectDependencies option is deprecated and no longer needed. But I removed it from my code, and then Unity spat out an error:
Please specify BuildAssetBundleOptions.CollectDependencies or collect GameObject components and pass as 'assets' parameter.
source share