Search Unity

  1. Welcome to the Unity Forums! Please take the time to read our Code of Conduct to familiarize yourself with the forum rules and how to post constructively.
  2. Dismiss Notice

Object references between addressable groups and patching

Discussion in 'Addressables' started by seraphki, Mar 10, 2020.

  1. seraphki

    seraphki

    Joined:
    Jul 20, 2016
    Posts:
    26
    I've started digging into addressables for our current project, and have a question about how hard referencing within addressables works.

    The current plan is to put our prefabs into a group and the assets that they reference (sprites, etc) in their own groups (separated by type). The reason for this is so that we can update data on the prefabs and without having to update the bundles containing images, resulting (hopefully) in smaller patches. Also so that if prefabs from separate groups use the same images, they will not be pulled into both groups and duplicated.

    First off, am I correct on those assumptions?

    Second, I was reading up on patching here: https://docs.unity3d.com/Packages/c...manual/AddressableAssetsDevelopmentCycle.html
    On this page it is mentioned that if you update an asset in a static bundle and use the update tools, that asset will be moved to a new bundle and the asset in the old bundle will be dead data. From what I've been able to discern, this is done via a catalog that gets updated so the provider now knows that the asset is in a different location. On the devices that download that patch will you only get the updated asset if you're using the addressables to reference that asset? Or will the hard references within prefabs (via sprite renderers, etc) know that they need to reference a new location?

    Thank you for your help!
     
  2. seraphki

    seraphki

    Joined:
    Jul 20, 2016
    Posts:
    26