Hello, I’m on 2021.3.5f1 using the 1.3.2 version of the package and I notice a large lag spike the first time that GetLocalizedString() is called. Though it doesn’t show up directly in the profiler.
I was wondering if there was some sort of initialization that should be done before hand to prevent this?
Yes if you use the synchronous version then it needs to force initialization to complete.
Yielding on LocalizationSettings.InitializationOperation should reduce this spike. If the table is preloaded then it should help even more.
Ah, I was wondering if it was something like that. Thank you very much!
Using this in an awake method seems to do it. This is would be the correct way to initialize it at game start correct?
LocalizationSettings.Instance.GetInitializationOperation();
That will start the operation. You should wait for it to finish by yielding on it in a coroutine. There’s a simple example in the package samples to show a loading screen for this.