I’ve got an existing game project that is organized in this manner:
1.) There is a main Unity Project A, which contains the code, and some assets that are always needed.
2.) There is a secondary Unity Project B, which creates asset bundles for various packs of art.
The asset bundles from Project B are normally delivered with my games, rather than being downloaded from a server. At runtime, I load only the art packs that are needed for a given play session. Works great.
Now, I’m interested in migrating to the addressables system, but the documentation on multi-project setups says:
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.
Wow. OK. Not cool. I really don’t want to change how I’m deploying these assets. So, are people with my setup just out-of-luck, or is there some way to finesse this? Can I just load “remote” assets from a local file: URL, or something?