Nativized BP Struct dependency can lead to a fatal loader stall

Report of a chain of dependencies that can lead to a fatal loader stall in a nativized build:

1. Thing -> BPStruct2
2. BPStruct1 -> BPStruct2

The necessary order of operations is:

1. BPStruct1 loads
2. BPStruct2 loads
3. BPStruct1 calls static constructor which calls constructor for BPStruct1 (before BPStruct1 has chance to call its static constructor)
4. BPStruct2 calls static constructor and fails to register as fully loaded, even though it is.
5. Thing tries to load and puts a loader node dependency on BPStruct2, which never is satisfied because BPStruct2 is done already.

User-suggested fix (for review):

Change the nativized code gen for the static script constructor from checking whether the object already exists via

  if (!Singleton)
  {

to using a static bool check instead

  static bool bWasRegisteredEver = false;
   if (!bWasRegisteredEver)
   {
         bWasRegisteredEver = true;

i have this problem UE4CC-Windows-58DC12AF4B97F057BD108FBFF569B2E9_0000

I am not able to find world outliner how to enable it?

How can i modify the param name in EQS node

How does TextureRenderTarget2D get TArray<uint8> type data?

What method is used to fill polygonal regions when drawing spline mesh at run time?

Undefined sysmbol: typeinfo for AActor when cross-compile linux dedicated server on windows

Delay nodes occasionally don't fire the "Completed" output in a nativized build

What is the difference between Camera and CineCamera?

How to achieve HLSL Multiple Render Target in Material blueprints?

Why does the volume fog disappear from a distant view?