I’ve recently picked up FObjectFinder to dynamically load materials in the game code. I’ve created a TextRenderer initializer class, that setups basic TextRenderer info and attaches it to specified component, rendering debug info in game.
Consider the following code:
.h
//Small utility class that encapsulates initializing TextRenderer attached to specified component.
class DebugTextRenderer
{
public:
DebugTextRenderer();
~DebugTextRenderer();
private:
UMaterial* TextMaterial;
};
.cpp
DebugTextRenderer::DebugTextRenderer()
TextMaterial(nullptr),
{
#if WITH_EDITOR
static ConstructorHelpers::FObjectFinderOptional<UMaterial> materialObjectFinder(TEXT("path_to_the_material"));
TextMaterial = materialObjectFinder.Get();
#endif
}
These code pieces worked fine for me in a long term. However, recently, upon trying to add new C++ class in UE editor it crashed during code recompilation. What’s really weird is that it crashed in the Get method of object finder, in the “CheckIfInConstructor” check:
T* Get()
{
if (!Object && ObjectToFind)
{
CheckIfIsInConstructor(ObjectToFind);
FString PathName(ObjectToFind);
StripObjectClass(PathName,true);
Object = ConstructorHelpersInternal::FindOrLoadObject<T>(PathName);
ValidateObject( Object, PathName, ObjectToFind );
ObjectToFind = nullptr; // don't try to look again
}
return Object;
}
Upon investigating the callstack, the method Get() is called from the DebugTextRenderer constructor. What’s really weird is that:
-
It crashes because the method thinks it’s called outside of a constructor, but it isn’t.
-
It doesn’t crash in any other scenario (the TextRenderer component I initialize with this class works fine until the .dll’s are recompiled by UE).
Any suggestions on what I’m missing? I’ve tried to make the TextMaterial variable static to ensure it only gets initialized once, but this code is being called from a thread different than the original component constructors.