Using Unity 2019.3.0f4 and Localization package Preview 0.5.1. The raw image with the attached Localize Texture component as shown here in the quick start guide is different for me.
Not sure this is how the Localization Texture is supposed to be? Anyone else using Localize Texture component that can help?
When I play the scene this is the result.
Error Console
ArgumentException: Empty Table Reference. Must contain a Guid or Table Name
UnityEngine.Localization.Tables.TableReference.Validate () (at Library/PackageCache/com.unity.localization@0.5.1-preview/Runtime/Tables/TableReference.cs:101)
UnityEngine.Localization.Settings.LocalizedAssetDatabase.GetLocalizedAssetAsync[TObject] (UnityEngine.Localization.Tables.TableReference tableReference, UnityEngine.Localization.Tables.TableEntryReference tableEntryReference) (at Library/PackageCache/com.unity.localization@0.5.1-preview/Runtime/Settings/Database/LocalizedAssetDatabase.cs:41)
UnityEngine.Localization.LocalizedAsset1[TObject].LoadAssetAsync () (at Library/PackageCache/com.unity.localization@0.5.1-preview/Runtime/Localized Reference/LocalizedAssetReference.cs:61) UnityEngine.Localization.LocalizedAsset1[TObject].HandleLocaleChange (UnityEngine.Localization.Locale _) (at Library/PackageCache/com.unity.localization@0.5.1-preview/Runtime/Localized Reference/LocalizedAssetReference.cs:74)
UnityEngine.Localization.LocalizedAsset1[TObject].ForceUpdate () (at Library/PackageCache/com.unity.localization@0.5.1-preview/Runtime/Localized Reference/LocalizedAssetReference.cs:66) UnityEngine.Localization.LocalizedAsset1[TObject].RegisterChangeHandler (UnityEngine.Localization.LocalizedAsset1+ChangeHandler[TObject] handler) (at Library/PackageCache/com.unity.localization@0.5.1-preview/Runtime/Localized Reference/LocalizedAssetReference.cs:40) UnityEngine.Localization.Components.LocalizedAssetBehaviour1[TObject].OnEnable () (at Library/PackageCache/com.unity.localization@0.5.1-preview/Runtime/Component Localizers/LocalizedAssetBehaviour.cs:34)
Oh, this is due to changes in serialization between 2019.3 and 2020.1.
Ill take a look on Monday, I suspect we are a bit too liberal with our use of generics.
Hi, Sorry it looks like I totally forgot to look into this. Would you be able to file a bug report? That way it wont get forgotten about
Post the number here so I can track it.
I am trying to use the package and I run in the same issue: I follow the quickstart, and when I create a table and add some entries, once I quit and reopen the project it saves my entries but I does not serialize the reference to each localized objects. I tried it on empty projects across different version of the 2019.3 releases with the same issue. Any idea where this bug could come from?
Thanks.
This is an issue we have in our use of generics. It works now in 2020.1 and will be fixed in 2019.3 in the next release of the localization package.
Thanks Karl and satchell! Do you have an ETA on the date of the next release? We have some use for it in one of our project and I’m still pondering whether I should wait for the fix or go for an in-house solution we would cook.
Awesome! Looks like the component is working in the inspector now and am able to set the fields as shown in the Quick Start.
There is another issue I’ll look into regarding the Asset Tables not retaining the textures for some reason. I think I’d seen another thread on the topic so I’ll keep messing around…
Hmm. Well if you can reproduce it then please file a bug report and post the number here so I can track it.
Less chance of me forgetting about it this way
I still have the same issue, is there something I’m missing to save the asset tables? It retains the link to the textures as long as my project is open. Whenever I close/reopen the project it loses the references to the textures (but not the entries, they are serialized). Sometime when I fiddle with the metadata/comments part of the textures get serialized (but not all of them?). It’s a bit hard to open a ticket since it’s hard to reproduce the rare cases where it succeeds. Any idea where that might come from?
No they are not, they are reference to texture assets located the project’s asset folder. You mean that it won’t serialize unless said asset is already referenced in the scene?
What I understood: I create a table, I link my different localized textures to an entry in the table. I then use the localize feature to a RawImage component, link to the right table and then entry. It just works as long as I don’t close/reopen the project, that’s when I loose my references to the textures :/.
No it should work as you describe. Im just trying to pinpoint what the problem could be.
When you lose the reference, could you change the inspector mode to debug(right-click the header) and check the values that the LocalizeTexture has?
It could be that it is serializing correctly but failing to find the texture in Addressables.
When it fails could you also open the Addresssables window (Window/Asset Management/Addressables/Groups) and check the texture is in a Localization group
2019.3.2f1 & 0.6.1
The values from the Addressables Groups window filled and stayed filled on my most recent attempt, not always the case. Hard to say there’s an issue for the inconsistent results or my use and gaining experience in Localization with Addressables. The Asset Tables still lose reference when Unity is closed and reopened.
The Debug Inspector fields don’t change from their initial settings from inserting to the Asset Tables to Unity restart.
Hope this helps. I want to make sure I’m not pointing in the wrong direction so bare with me…
