Because this loading screen must be shown before remote Assets are streamed to disk, you might include the logo Asset in the build so that it can be used immediately. The logo may be displayed in the UI of a loading scene while the game starts up. If this class is using more than 10MB of RAM, you’re probably using the memory cache. To determine what effect the AssetBundle memory cache may have on your application’s memory usage, use a native profiler (our tool of choice is Xcode’s Allocations Instrument) to examine allocations from the ArchiveStorageConverter class. You must weigh the tradeoff in memory cost versus added disk space requirements and Asset instantiation time for your application. Internal testing shows that there is at least an order of magnitude difference in RAM between using the disk cache and using the memory cache.

If it is not feasible to use the UnityWebRequestAssetBundle API, you may use AssetBundle.RecompressAssetBundleAsync() to rewrite an LZMA AssetBundle on disk. We therefore recommend using the UnityWebRequestAssetBundle API instead. This behavior can be controlled via the UseAssetBundleCache field.ĪssetBundle.LoadFromFile() and AssetBundle.LoadFromFileAsync() always use the memory cache for LZMA AssetBundles. Note that Addressables uses the disk cache by default. If you do not provide these arguments, Unity uses the memory cache.

If you provide a version or a hash argument to the UnityWebRequestAssetBundle API, Unity stores your AssetBundle data into the disk cache. When Unity downloads an LZMA AssetBundle using the Unless you specifically want to frequently and rapidly access the contents of an AssetBundle, the memory cache is probably not worth the memory cost. If you are working on a project with an already established AssetBundles approach, the information here about how AssetBundles affect runtime memory will help you get the best possible results. For an overview of the Addressables system, please refer to this blog post and this session from Unite Copenhagen 2019.ĭevelopers working on new projects should consider using Addressables rather than working with AssetBundles directly. While Addressables minimizes the direct interactions developers have with AssetBundles, it is helpful to understand how the usage of AssetBundles can affect memory usage. It is an abstraction on top of AssetBundles. The Addressables system is a package that provides a more accessible and supported way to manage Assets within your projects. An AssetBundle is a file that contains one or more serialized assets (Textures, Meshes, AudioClips, Shaders, etc.) and is loadable at runtime.ĪssetBundles can be used directly or through systems like the Unity Addressable Asset System (aka Addressables). Whether your application streams assets from a content delivery network (CDN) or packs them all into one big binary, you’ve probably heard of AssetBundles.

Asset bundler asset bundle viewer unity