Question Very first LocalizeStringEvent invocation is very slow

Hey! I was inspecting the cause of a framedrop caused especially on low-end devices, and upon inspections with the profiler, I noticed that the reason is the LocalizeStringEvent component doing a localization for the very first time.



Is it possible to do something to prepare the localization system in the loading screen in order to avoid this framedrop?

 

I'm not using WaitForCompletion, only the LocalizeStringEvent component - I don't know if that does that internally.

The preloading is already activated, doesn't seem to help

 

I just tried putting

yield return LocalizationEditorSettings.InitalizationSettings;

before loading the first scene in the application's very first loading screen, but that first freeze-up still persists...

 

Seems like it boils down to Mono.JIT at the end, after which the load spreads out among internal Mono functions like GC.Alloc.

 

Sure thing, here is the screenshot;

and here is the profiler capture file:
https://drive.google.com/file/d/1k_TtBlXXrkaEAPEMZ3HiEp7KX85sIXWC/view?usp=sharing

The lag spike occurs on frame 204/300 (should be obvious on the graph)

 

No, I forgot about the deep capture feature

I'm using many smart strings in this project indeed. The one that caused the lag in this instance looks like this:

{interactKeyName} - Open Chest - <color=#26ABFF>{normalGoldCost}</color><sprite name=coin> 

interactKeyName - StringVariable
normalGoldCost - IntVariable

Though this happens with other Smart Strings if they are created for the first time as well. Is there a way to have the Smart Strings create their pools during the loading screen?

 

I couldn't figure out how to use Smart.Format (it kept throwing exceptions), so I decided to add a LocalizeStringEvent with Local Variables in my loading scene for an off-screen text to achieve the same effect and voila - the lag caused by smart formatting is gone!




Upon further inspection I found out that most of the lag was actually caused by -this- very first TextMeshPro call... However, thank you for your help, shaving off a 20ms is a good achievement too!