7502018d20
There is an asset in the store I grabbed. the coding is WAY above my head, I got about half of it and integrated and adapted what I can to it. im going as far as I can with it and ill come back in a few month when I understand t better.
3.2 KiB
| uid |
|---|
| addressables-multiple-projects |
Loading from Multiple Projects
Should your situation require a multi-project workflow, such as a large project broken up across multiple Unity projects that have the Addressables package installed, we have Addressables.LoadContentCatalogAsync to link together code and content across the various projects. Studios with teams that works on many facets of an application simultaneously may find benefit with this workflow.
Setting up multiple projects
The main items to note for a multi-project setup is to make sure:
- Each project uses the same version of the Unity Editor
- Each project uses the same version of the Addressables package
From there projects can contain whatever you see fit for your given situation. One of your projects must be your "main project" or "source project". This is the project that you'll actually build and deploy your game binaries from. Typically, this source project is primarily comprised of code and very little to no content. The main piece of content that you would want in the primary project would be a bootstrap scene at minimum. It may also be desirable to include any scenes that need to be local for performance purposes before any AssetBundles have had a chance to be downloaded and cached.
Secondary projects are, in most cases, the exact opposite. Mostly content and little to no code. These projects need to have all remote Addressable Groups and Build Remote Catalog turned on. Any local data built into these projects cannot be loaded in your source project's application. Non-critical scenes can live in these projects and be downloaded by the primary project when requested.
The Typical Workflow
Once you have your projects setup, the workflow generally is as follows:
- Build remote content for all secondary projects
- Build Addressables content for source project
- Start source project Play Mode or build source project binaries
- In source project, use
Addressables.LoadContentCatalogAsyncto load the remote catalogs of your other various projects - Proceed with game runtime as normal. Now that the catalogs are loaded Addressables is able to load assets from any of these locations.
In regards to the source project, it should be noted that it may be worth having some minimal amount of content built locally with that project. Each project is unique, and so has unique needs, but having a small set of content needed to run your game in the event of internet connection issues or other various problems may be advisable.
Handling Shaders
Addressables builds a Unity built in shader bundle for each set of Addressables player data that gets built. This means that when multiple AssetBundles are loaded that were built in secondary projects, there could be multiple built in shader bundles loaded at the same time.
Depending on your specific situation, you may need to utilize the Shader Bundle Naming Prefix on the AddressableAssetSettings object. Each built in shader bundle needs to be named different from others built in your other projects. If they're not named differently you'll get The AssetBundle [bundle] can't be loaded because another AssetBundle with the same files is already loaded. errors.