Addressable asset has a null reference when instantiated via LoadAssetAsync

Unity Engine
1

I’m wondering if anyone has seen this behavior. I have fairly simple prefab, which has a component on it that references a Scriptable Object asset (“the config”). If I drag this prefab into my scene, it works fine, and I see that “the config” is on the object. However, when I instantiate the object dynamically, then the component has a null reference to the config.

I’m loading the object via Addressables.LoadAssetAsync, following by calling Instantiate on the result.

My understanding was that Addressibles was smart enough to include dependencies, and that I won’t need to mark every possible dependency as Addressable and put it in a category. That said, “the config” shows up in the “Duplicate Asset Isolation” section of the addressables window:

4550074--422320--upload_2019-5-16_19-7-46.png
4550074--422320--upload_2019-5-16_19-7-46.png777×211 27 KB

Has anyone seen this behavior before?

I tried manually adding “the config” to the same group as the object I’m spawning, and that “fixes” the issue. Now the reference isn’t null. But again, I thought that Addressables should automatically find dependencies, and I don’t need to manually add every possible dependency to Addressables for it to work.

2

I think we have to do the same thing you did. our build is crashing due to adding Addressable assets - to lighten load on memory. It has Null Ref right away when we try to Addressables.InstantiateAsync.

I’ll see if I can follow your workaround here and find that config.

3

Thanks for your post - it led me to understand why I had a problem. I was loading a large addressable asset to avoid memory problem and didn’t include its dependencies like you mentioned. I had to remove it because it’s clearly not a good candidate for addressables compare to other simple objects.

4