Apex Skeletal Mesh Clothing Crashes on SetSkeletalMesh();

[MPalacios]

Hello!
When setting an Apex Skeletal Mesh to my SkeletalMeshComponent everything works fine.
I want the player to be able to switch clothing and unequip clothing.
Previously - without apex - all I did was SkeletalMeshComponent->SetSkeletalMesh(nullptr) to remove the clothing and it worked fine.
With Apex, however, the engine crashes. Seems like there’s some tick going on in the Apex which crashes when the reference becomes null.
I’d really prefer not to use SetVisibility.

Anybody know of any way to deactivate physics/ticking on the Apex prior to removing the reference?

Thanks!

[MPalacios]

I got the solution from UDN. Here’s the answer in case anybody runs into the same issue;

Ok I’ve reproduced this and found the cause. We require a skeletal mesh when building the context for clothing simulation even when no clothing actors exist. Moving the recreate call above the null check is probably still correct but if you also go into USkeletalMeshComponent::TickClothing and change the first section to this:

if (CVarEnableClothPhysics.GetValueOnGameThread() == 0 || SkeletalMesh == nullptr)
{
return;
}

Your crash should go away. There’s no sense in ticking clothing without a mesh and it looks like we weren’t checking that case. I’m not sure that this is 100% the correct fix here (probably should unregister the clothing tick entirely) so I’ll log an issue to investigate that - but the check above should get you up and running again. Sorry it’s take a while to get this issue sorted - hopefully everything will work now!

Benn.