After upgrading to UE 5.7, I’ve encountered persistent validation errors when using MetaHuman clothing and groom assets sourced directly from the MetaHuman store. These assets work perfectly in editor and runtime, but the MetaHuman validator throws intrusive errors and warnings that disrupt workflow and cause anxiety. I’m still new to Unreal, so I asked an AI assistant (Microsoft Copilot) to help me understand what’s going on. It confirmed that these are false positives caused by stricter validation logic introduced in 5.7.
Steps to Reproduce:
- Add MetaHuman clothing or groom asset (e.g., , ) as a wardrobe item.
- Run MetaHuman validation.
- Observe repeated errors:
• “WardrobeItem should use a pipeline derived from UMetaHumanGroomPipeline or UMetaHumanSkeletalMeshPipeline.”
• “Groom Binding does not have an associated source mesh.”
• “Skeletal mesh does not have at least 4 levels of detail.”
Expected Behavior:
Assets from the MetaHuman store should validate cleanly without requiring manual pipeline overrides or dummy LODs.
Actual Behavior:
Validation throws errors and warnings, despite assets rendering and animating correctly. The system allows asset use but floods the user with error spam. This includes:
• Hair disappearing when “Always Use Hair Cards” is enabled (due to missing card LODs or broken bindings).
• Clothing assets working fine but still triggering pipeline and LOD errors.
• Validator allowing asset use but repeatedly screaming at the user.
Impact:
This behavior causes unnecessary anxiety and workflow disruption. The validation system undermines confidence in compliant assets and forces manual overrides for store-approved content. As someone new to Unreal, this has made me feel sick and anxious while trying to build — especially when the assets clearly work and the system still screams failure.
Additional Notes:
• I asked Microsoft Copilot to help explain the issue. It confirmed that UE 5.7 introduced stricter validation logic and that these errors are not caused by user mistakes.
• The validator does not block asset use but throws repeated warnings that feel intrusive and emotionally exhausting.
• This is not a user error — it’s a regression in validation logic that needs to be addressed.