Feedback Are there any convenient ways or API to get the reference count of a addressables asset?

Hey guys.

Are there any convenient ways or API to get the reference count of a addressables asset?
As in asset bundle, I may keep the reference count of prefab and other asset by myself. But in addressables, did it have a ready-made API for me to use in runtime?

I used Addressables.ResourceManager.RegisterDiagnosticCallback to do this. But it seems not working when call destroy on a gameObject, only Addressables.ReleaseInstance is usefull to Addressables.InstantiateAsync gameObjectes.​

Thanks.

 

I used Addressables.ResourceManager.RegisterDiagnosticCallback to do this. But it seems not working when call destroy on a gameObject, only Addressables.ReleaseInstance is usefull to Addressables.InstantiateAsync gameObjectes.

 

We could probably add this, but I think it might not be a super efficient API. What exactly do you need it for? Are you just wanting a catchall at the end of some section to say "if anything's still ref'd release it"?

 

In sometimes I just want to release those no reference assets include prefabs and textures etc.

 

My recommendation is that you keep up with things yourself. If you do need something like this, then the easiest thing is to probably just extend addressables. Keep in mind that it's a package you have full source code access to. Ideally you don't need it, but as of now, I don't think we provide that interface you want.

 

Yes, but i am not dying for modifing the soures code , as i want to keep it same with yours for updating etc.
I am managing it myself now, Could you please give me some suggestions to realize this?
Thanks.

 

Let me clarify what I meant. For what you need, you should be able to extend (not modify) the package. And I think for your needs, having the ability to read/browse our source code can help you with what you need, but you shouldn't need to edit.

Now, let me ask a clarifying question of your need.

I may have misunderstood what you are wanting. Which situation are you in:

1. You have loaded things through addressables, the addressables ref count is above 0, but at some point you want to tell addressables to release everything it has (maybe you are leaving a level or something).
2. You have loaded things through addressables, and released them, and the addressables ref count is 0. But, since sometimes things stay in memory, you want to force-unload them from memory.

I had been thinking you were in situation number 1. You wanted a "clean out all the things addressables is referencing". But now after a reread, I'm wondering if you are in situation number 2. Please clarify.

 

I load assets with addressables, but i destroy it using GameObject.Destroy , not using Release ,and the ref count in addressables will not be right.

 

well, I think we've identified the problem! Just don't do that.

If you really don't want to keep up with which things are addressable, just write a little helper method like this:

Code (CSharp):

1.     static void MyDestroyMethod(GameObject someGameObject)
2.     {
3.         if(!Addressables.ReleaseInstance(someGameObject))
4.             GameObject.Destroy(someGameObject);
5.     }

If you absolutely refuse to use Addressables.ReleaseInstance then I'm not sure how I can help you.

 

We don't want to change user's behavior and ask them not to use as this...

 

are you an asset store tool?

I'm somewhat confused by who the users are you don't want to change. It sounds like you're asking someone to change how they load/instantiate (from the normal Unity way, to calling into your system), but you don't want them to change how they unload.

As a tool creators ourselves, we have decided if you are using our system to load, you need to use our system to unload.

If you are a tool creator that wants to find a way around that, I'm don't really have any helpful ideas I can think of.

 

I am just a common game developer , not a asset store tool.
I can change other team members in out team's behavior to use our load method as it is normally encapsulated , we do not need to change it no matter we use what type of load system.
BUT, I do not want to ask those guys not to use unity's Instantiate/Destroy method.

 

In such case, you can try to avoid using AddressReference and Addressables.InstantiateAsync, which manage reference counting for you. Just LoadAssetAsync(addressName), cache it somewhere, and use normal GameObject.Instantiate and GameObject.Destroy.

 

yes, I can managa the references myself , that 's the last way for me . and I was hoping addressables can do it automaticly...

 

Well it's a technique difficult that Unity does not have a global event processing feature for object destroy. So if the AAS manages reference counting for you, you have to tell the system exclusively when object get destroyed. That probably one of the drawbacks to implement the system as a package, it's not part of the core engine, it can not do too magical things for you.