Actually it does relate to blueprints just a tiny bit. I have a VR pawn that is very much empty at this point. It is a C++ class, that I derive from my other class APCPawn, which in turn is derived from APawn. I can create a blueprint from APCPawn without a problem, and the only thing AVRPawn currently has is the following constructor:
AVRPawn::AVRPawn()
: Super()
{
UMotionControllerComponent* leftController = CreateDefaultSubobject<UMotionControllerComponent>(TEXT("LeftController"));
leftController->SetupAttachment(RootComponent);
leftController->bDisplayDeviceModel = true;
UMotionControllerComponent* rightController = CreateDefaultSubobject<UMotionControllerComponent>(TEXT("RightController"));
rightController->SetupAttachment(RootComponent);
rightController->MotionSource = FXRMotionControllerBase::RightHandSourceId;
rightController->bDisplayDeviceModel = true;
}
Nevertheless, any attempt to create a blueprint out of AVRPawn crashes the editor with the subject message.
But… Commenting out
xxxController->bDisplayDeviceModel = true;
lines eliminates the crash.
Since having these lines uncommented and using AVRPawn directly from the game also has an issue: all materials are rendered unlit, I suspect that the bug is in SteamVR plugin…
Does your project by any chance also rely on VR?