Question Get RemoteLoadPath at runtime?

I'll bounce this off the team for some guidance!

 

So, it's not exactly the most straightforward thing to do but it is possible. Basically you need to load the built in ResourceManagerRuntimeData and then check the property CatalogLocations. The [0] index should always be the remote location. Let me clarify, the location will point to a .hash file. What you probably want is the .json catalog location so just replace the .hash with .json to point to the actual catalog.

Code (CSharp):

1. string playerSettingsLocation = Addressables.ResolveInternalId(PlayerPrefs.GetString(Addressables.kAddressablesRuntimeDataPath, Addressables.RuntimePath + "/settings.json"));
2.  
3.         var text = File.ReadAllText(playerSettingsLocation);
4.         ResourceManagerRuntimeData rtdRuntime = JsonUtility.FromJson<ResourceManagerRuntimeData>(text);
5.  
6.         var remoteCatalogLocation = rtdRuntime.CatalogLocations[0].InternalId.Replace(".hash", ".json");
7.  
8.         //var remoteCatalogLocation = rtdRuntime.CatalogLocations.First(loc => loc.InternalId.StartsWith("http://"))
9.         //    .InternalId.Replace(".hash", ".json");

I've thrown in the commented out section in case you'd rather find the remote path that way instead of relying on the 0 index.

One other option is to use the Addressables.TransformInternalIdFunc. You can use this to see paths as Addressables requests assets (catalogs, AssetBundles, etc.). You could look for a remote catalog location to come through this func and then do whatever you need with it. Something akin to this:

Code (CSharp):

1. Addressables.InternalIdTransformFunc += location =>
2.         {
3.             if (location.InternalId.StartsWith("http://") && location.InternalId.EndsWith(".json"))
4.             {
5.                 //Do something with remote catalog location.
6.             }
7.  
8.             return location.InternalId;
9.         };

Full disclosure this code is untested so you may need to tweak it for your specific situation. I hope this helps.

 

Hopefully this is what you're looking for but if you feel that string "{UnityEngine.AddressableAssets.Addressables.RuntimePath}/catalog.json" into

Addressables.ResolveInternalId

it should give you what you're looking for. Let me know if it doesn't.

 

If you step through your code can you check rtdRuntime.CatalogLocations and see what that list looks like? The catalog location order should be deterministic but perhaps it isn't See if any of those CatalogLocations contain the remote location you're looking for. I just tested your code exactly as it is in my project and it got me the remote load path.

Also, if you see less than 3 entries in the CatalogLocations double check that Build Remote Catalogs has been turned on and you've rebuilt your Addressable data after turning it on (I figure it probably is but I wanted to mention it just in case).

As a potential workaround you might want to set the remote location to a PlayerPrefs as part of your build

Code (CSharp):

1. PlayerPrefs.SetString("myremotelocation", AddressableAssetSettings.RemoteCatalogLoadPath.GetValue(AddressableAssetSettings));

and then you should be able to retrieve that at runtime using

PlayerPrefs.GetString

which, of course, isn't ideal and I'll open a ticket because this shouldn't be this difficult. There's definitely some quality of life improvements we can make here. But this might help you in the meantime.

 

Hey, I'm glad you got it figured out!

I don't have the full context but regarding your "different apps/same bundles" situation I'd recommend looking into

Addressables.LoadContentCatalogAsync

. You may have already done so. In my mind the setup looks like this:
- Project A: Houses the actual assets and builds the remote AssetBundles
- Project B: Uses remote bundles from Project A
- Project C: Also uses remote bundles from Project A

Now, for Project A you'd build your remote catalogs and AssetBundles like normal, no issue there. You might want to take advantage of the Player Version Override in Project A. Normally a remote catalog is going to be named something like catalog_2021.9.3.2.4.json or whatever. If you put in a string in the Player Version Override, lets say "abc" the remote catalog will be named catalog_abc. It'll always be "catalog_abc" which is useful for your dependent projects.

For Projects B and C you can do this however makes sense for your project but you basically want to construct the url to the remote catalog created by Project A. The Player Version Override is useful because you don't have to try and save/reconstruct a time stamp to add to your URL. You have a static string that you already know.

Once you have the remote path constructed, pass that into

Addressables.LoadContentCatalogAsync

and those projects should now download and use those AssetBundles like any other project. Of note: make sure these apps are only downloading bundles built for their specific platform. This might mean that you need to divide up builds on your CDN into different folders based on the platform and use that in the construction of your URL.

Re: PlayerPrefs at Runtime - I'm pretty sure you can. I don't use it much but I'm almost positive that that's a thing. I might be mistaken though.

I hope some of this helps. If you have more questions/concerns about multi project set ups feel free to make a new thread. It helps me and our community team keep track of issues