In our project we have config classes based on UDeveloperSettings.
Some of these classes are defined in a module that is not the main project module (not sure if this has an impact).
We define these settings with ini files linked to these classes.
It seems that if in these ini files we use LOCTABLE with a Stringtable asset reference to define some text, the Stringtable asset will be loaded with the flag EInternalObjectFlags::LoaderImport and as such will result in triggering an ensure in VerifyObjectLoadFlagsWhenFinishedLoading() (line 10698 of file Engine\Source\Runtime\CoreUObject\Private\Serialization\AsyncLoading2.cpp), for instance :
Ensure condition failed: !bHasLoaderImportFlag || GUObjectArray.IsDisregardForGC(Obj) [File:xxx\Engine\Source\Runtime\CoreUObject\Private\Serialization\AsyncLoading2.cpp] [Line: 10698]
Object 'StringTable /Game/UI/Commons/Data/StringTables/ST_UI_Settings.ST_UI_Settings' (ObjectFlags=28000B, InternalObjectFlags=108000) should not have the LoaderImport flag now, or this check is incorrectly reached during active loading.
It is to note that these string tables objects, in the GUObjectArray have the first indexes that are not disregardForGC
I don’t really get what we’re doing wrong and what is the expected use of LOCTABLE in ini files when the settings class is in a separate module
Can these ensures be considered harmless or can it lead to some unexpected behaviour ?
Thanks
[Attachment Removed]