Question Using Localization inside AssetBundle Scene

Hello guys,
I am creating Content-Scenes as Asset Bundles in a separate Unity-Project (Project A) and we started using the Unity Localization for handling localization inside the AB.
The AB gets loaded into another project (Project B) as a Scene and gets "played" there. Unfortunately I've realized that the Localization does not work after loading the AB - The Tables are not available.



This is a screenshot of the inspector of the loaded AssetBundle. As you can see the Table Collection is empty.
I currently cannot wrap my head around how to approach this. From my understanding when im trying to access the Localization via LocalizationSettings it will get the LocalizationSettings of my Project-B which loads the AB but not the LocalizationSettings in the AB itself (from Project A).
So I need my Localization Tables (String, Asset) written into the AB itself and the AB should also only use the Localization from the AB.
If there is anyone who could point me to the right direction would be greatly appreciated.

Best regards,
Phil

 

Let's say I create addressables out of my secondary project and import the addressables (with the String / Asset Tables from the Localization) into my primary Project. To me it's still unclear how my AB will use the String / Asset Tables inside the Addressable Catalog while I try to call it via LocalizationSettings. Do I need to announce the Tables to the Localization in the Primary Project?

 

Hello Karl, thanks for your reply.
I've set up my Adressables inside the AB to be packed within the AB. Therefore from my understanding the addressable data (including the Localization tables) should be available. How would I load and assign the Tables to the Localization in the Viewer Project so that my AssetBundle can be localized? Since the LocalizeStringEvent-Component is empty, do I need to re-initialize them at runtime after loading the AssetBundle?

 

Hello Karl,
I don't need to author the localization data once the Asset Bundle is built. I also don't need to have information shown in the inspector, since in the end its a built Windows Application. I see that it is missing a Table Collection with a certain GUID. So what I think needs to be done is to assign the Table Collection to the Localization Settings at runtime? Do I have to Load the Addressables from the AssetBundle first and then get the Table Collection out of that? I've set the Play Mode in our Viewer Project (which loads the AssetBundle as a Scene) to use existing Build but still the TableCollection is missing.

 

Hello Karl,
I've managed to make it work by loading the Addressable Catalog before loading the Asset Bundle.

After a while I'm now encountering the following issue:



I'm not able to load the catalog anymore. Also every time I click into the addressable group window this error appears - I see no more addressable groups or any addressable at all until i restart the Editor. I'm using Addressables 1.20.5 in both projects aswell as Localization 1.4.3.

In my Viewing project the following error appears:



I've tried updating the Addressable package to no avail. It looks like the Localization Addressable package (which I believe is created within the Localization System) is buggy or somehow erroneous.

Best regards,
Phil

 

Hello Karl,
I've managed to get the localization package running again by reimporting the whole project.
After loading the localization via the addressable catalog everything seemed to look fine until I tried changing the language. For some reason my second locale (DE) is not detected.
In Project A I have a Localization Settings with Locale DE and EN. In Project B i also have DE and EN locales in my settings.
When I start Project A my Settings look like this:



When I'm loading my AB-Scene from Project B (via Content Catalog) for reasons unknown to me the German locale identifier (DE) changes to EN in the runtime. If I manually change the identifier back to DE (in the runtime) the missing locale is detected and language changing works fine.

This is my default group inside Project B where the localization stuff resides:



Should I have the locales and Localization Settings from Project B in my Catalog? If so, do I need to manually load in the localization settings in project A?

Best regards,
Phil