Now, let's say I want to update content (from remote locations) at runtime, when I had already loaded a previous version of the content. But checking the documentation, it says ' Release the internal operation handle', which should be actually equivalent to Addressables.Release(operationHandle), is that so? If so, the name is pretty confusing, I think an AssetReference.ReleaseOperationHandle (or similar) method should be added, making ReleaseAsset obsolete. I have also tried AssetReference.ReleaseAsset, thinking it was equivalent to Addressables.Release(asset), but then both the operation and the asset disappear from the event viewer. What is going on, does the asset still have a ref count of 0, and if I try to use it at some point in the future it may fail? But the operation handle is still in the event viewer, and I can still do operationHandle.Result to get the asset, which doesn't appear in the event viewer. Now I see the asset disappearing from the event viewer, so I assume its ref count is 0, so it's ready to be unloaded by Unity at some point. Let's say I don't release the operation, but I release the asset, which I don't need anymore, using Addressables.Release(asset). I assume that now I have to unload the operation handle since I don't need it anymore, using Addressables.Release(operationHandle), right? I see what seems to be the operation disappearing from the event viewer (' ChainOperation - InitializationOperation'), but the entry for the loaded asset also disappears (' Resource(New Item 1.asset)'), does it mean that releasing the operation also releases the asset, or what is going on? If I'm interpreting the manual and the addressables event viewer correctly, the ref count for both the operation and the asset will be 1, is that correct? I'm loading an asset (a ScriptableObject) using AssetReference.LoadAssetAsync, and getting the instance with the Result property. I'm quite confused regarding the actions of releasing an asset and releasing an operation handle.

Unity assets viewer release