Search Unity

Bug Localization and addressables compatibility is nightmare

Discussion in 'Localization Tools' started by DevsSTG, Jan 12, 2021.

  1. DevsSTG

    DevsSTG

    Joined:
    Aug 21, 2020
    Posts:
    3
    That makes a bunch of times that I have to recreate all the locales and string tables to be able to have them working in addressable.
    It sometimes loses references, corrupts addressable groups and then you have to start all over again...
    Would it be possible to make some script to replug tables in the right addressable groups? (actually this is possible with locales, deleting the group in Addressable groups, then re-adding all locales in localizationSettings, but this already seems to be a hacky way to fix that)
    As locale addressable groups are made not editable you can't configure it from editor to fix that, which should have been the easiest way I think. Seems like a buggy behaviour (I hope it is ^^' )
     
    DevsSTG, Jan 12, 2021
    #1

  2. DevsSTG

    DevsSTG

    Joined:
    Aug 21, 2020
    Posts:
    3
    By the way I tried resetting them in addressable groups by switching the group inspector to debug, remove read only, add entries, and re-enabling readonly, but it seems to not work. It ends up with no Key Id found (while I clearly see the key ids are the good ones) and console spamming about either tables not found or other stuff addressable related
     
    DevsSTG, Jan 12, 2021
    #2

  3. karl_jones

    karl_jones

    Unity Technologies

    Joined:
    May 5, 2015
    Posts:
    8,291
    Hi,
    Could you file a bug report with any issues you may have?
    In 0.10.0 we have made some improvements, if you re-import a StringTableCollection or AssetTableCollection then it should fix any Addressables issues.

    We made the group readonly because allowing for making changes is more likely to create bugs/errors. Our Addressables require very specific names and labels.
    If you click the remove option in the collection and then add it should fix the addressables issues for you now except for the shared table data which is fine to add as a normal addressable(name and labels are not important for that)
     
    karl_jones, Jan 12, 2021
    #3

  4. Skjalg

    Skjalg

    Joined:
    May 25, 2009
    Posts:
    211
    I'm on the latest preview (0.9) and I have been struggling with this for days.

    Why does this happen?

    Excerpt from catalong.json
    "m_InternalIds":["{UnityEngine.AddressableAssets.Addressables.RuntimePath}/StandaloneWindows/defaultlocalgroup_assets_all_6741363fbaef67acb63a98c54691a127.bundle","
    {UnityEngine.AddressableAssets.Addressables.RuntimePath}/StandaloneWindows/localization-assets-shared_assets_all_1cd5ef8fb81df9fe80b8418c4518a253.bundle",
    "Library/com.unity.addressables/aa/Windows/StandaloneWindows\\localization-locales_assets_all.bundle","
    {UnityEngine.AddressableAssets.Addressables.RuntimePath}/StandaloneWindows/localization-stringtables_assets_all_8f2e326ebc491f3f0d5cb944d918406d.bundle","
    {UnityEngine.AddressableAssets.Addressables.RuntimePath}/StandaloneWindows/ftue_assets_all_1bac7f26fb354a159c253b0b1a817e54.bundle","
    {UnityEngine.AddressableAssets.Addressables.RuntimePath}/StandaloneWindows/ftue_scenes_all_679fe7946ef5791d97c4b571b2e4e7af.bundle","
    {UnityEngine.AddressableAssets.Addressables.RuntimePath}/StandaloneWindows/mainmenu_assets_all_61f62b03b972cb833cef1e2485912dda.bundle",

    It's not set to custom path, its set to LocalLoadPath

    How can I fix this?
     
    Skjalg, Jan 25, 2021
    #4

  5. karl_jones

    karl_jones

    Unity Technologies

    Joined:
    May 5, 2015
    Posts:
    8,291
    You should be able to edit it in the addressable editor. Select the locales group and edit the path.
     
    karl_jones, Jan 25, 2021
    #5

  6. Skjalg

    Skjalg

    Joined:
    May 25, 2009
    Posts:
    211
    You mean this one?
    upload_2021-1-25_15-39-35.png

    Shouldn't load path be LocalLoadPath?

    Seems to me like BuildPath is the one being used, which is a bug
     
    Skjalg, Jan 25, 2021
    #6

  7. karl_jones

    karl_jones

    Unity Technologies

    Joined:
    May 5, 2015
    Posts:
    8,291
    Im not sure. We just create a default group for the Locales, we dont do anything with the build or load paths. So if its a bug then it will be on the Addressables side. Could you file a bug report so we can look into it?
     
    karl_jones, Jan 25, 2021
    #7

  8. Skjalg

    Skjalg

    Joined:
    May 25, 2009
    Posts:
    211
    Sure, case 1309120
     
    Skjalg, Jan 25, 2021
    #8
    karl_jones likes this.

  9. Skjalg

    Skjalg

    Joined:
    May 25, 2009
    Posts:
    211
    Did you have a chance to look at it? Is it a bug with my setup or in the build process itself?
     
    Skjalg, Jan 26, 2021
    #9

  10. karl_jones

    karl_jones

    Unity Technologies

    Joined:
    May 5, 2015
    Posts:
    8,291
    Its still with QA. It takes a couple of days to work through them.
    Ill ask the Addressables team if its a known issue
     
    karl_jones, Jan 26, 2021
    #10

  11. karl_jones

    karl_jones

    Unity Technologies

    Joined:
    May 5, 2015
    Posts:
    8,291
    Addressables have managed to reproduce the issue. It is indeed an Addressables bug so once its fixed it should just be a case of updating to the latest Addressables package in the package manager for it to start working in Localization.

    One thing we do change is the Bundle Naming. If you change it back to the default "Append hash to filename" then it should work until we can get a fix.

    upload_2021-1-26_14-45-25.png
     
    Last edited: Jan 26, 2021
    karl_jones, Jan 26, 2021
    #11
    Skjalg likes this.

  12. Skjalg

    Skjalg

    Joined:
    May 25, 2009
    Posts:
    211
    Thanks for the quick response!
     
    Skjalg, Jan 28, 2021
    #12
    karl_jones likes this.