MetaHuman Crowd Collection Generates White/Untextured Heads

Newly created MetaHuman Crowd Collections generate MetaHuman Instances with white/untextured heads. This reproduces in a clean project with a newly created MetaHuman Character, so it does not appear related to migration or custom assets.

The generated face material instances use placeholder baked textures such as T_Flat_Grey_C, T_Flat_Black_M, T_Flat_N, and T_Flat_White_C, instead of character-specific baked face textures.

[Image Removed]

Is there a required setup step missing for baking face textures in custom MetaHuman Crowd Collections?

[Attachment Removed]

Steps to Reproduce

  • Create a new UE 5.8 project with MetaHuman Character/Crowd plugins enabled.
  • Create a new MetaHuman Character.
  • Create a new MetaHuman Crowd Collection from that character.
  • Build/generate the Collection and create a MetaHuman Instance.
  • Open the Instance or spawn it through Mass Crowd.
  • The head renders white/untextured, and the generated face material uses placeholder baked inputs.
    [Attachment Removed]

Hi, sorry for the delay getting back to you on this. Our offices have been closed for the last couple of weeks so we’re just in the process of catching up.

Thanks for reporting this, I’ve been able to reproduce it. It appears to be a bug with the head item setup when using the crowd character pipeline when a pre-existing mesh asset isn’t specified for the head. It looks like when you don’t specify an existing asset, the materials that are generated for the mesh aren’t applied correctly.

You should be able to work around this by specifying your existing mesh for your character here:

[Image Removed]Let me know if that gets things working for you, and I’ll continue looking into what’s going wrong when the mesh isn’t specified.

Thanks,

Euan

[Attachment Removed]

Hi Matthias, I’ve spoken to the dev team and investigated this further, but it looks like any fix won’t be trivial to implement. The dev team has also recommended that specifying the mesh assets within the pipeline is actually the desired workflow because it’ll make building the collections significantly quicker, and it means that the generated materials will be simpler. So for now, you should continue to manually specify these assets. I’ve created a bug to track this issue so you can see when it eventually gets resolved.

Thanks,

Euan

[Attachment Removed]

Hello Euan,

this workflow works for now, thanks!

Best regards,

Matthias

[Attachment Removed]

Hello there,
sorry to bother both,

the attached images are not anymore accessible, unfortunately.

Could you please help me to fix this issue.
i’ve tried to do tons of check and changing assets on this, but seems that is not currently working and generates White/Untextured Heads, even if in the Collection still referencing the correct asset.

Could you even point me out maybe the C++ class of the engine?
maybe i could help to fix the issue…

Best,
Alessio Masola

Workaround for the White Face Issue in MetaHuman Crowd (UE 5.8.4)

I encountered the same white face issue when using custom MetaHumans with MetaHuman Crowd in UE 5.8.4.

I managed to resolve it by creating custom Crowd face materials and assigning them through a duplicated BP_CrowdPipeline.

This workaround worked with two different custom MetaHumans, including one with clothing and Groom assets.

What seems to cause the issue

The problem appears to involve two things:

  1. A texture parameter name mismatch: The original MetaHuman uses Basecolor, while the default Crowd baked material uses Basecolor Baked. The texture parameter may not be transferred correctly.

  2. The baked material path not being enabled: In my tests, the generated Material Instances had Use Baked Material = False, which prevented the intended baked material path from being used.

Here is how I worked around it.

Step 1: Duplicate the Material Function

  1. Find MF_skin_bakedInputs.

  2. Duplicate it into your project’s Content folder.

  3. Rename it to MF_MWC_skin_bakedInputs.

  4. Open the duplicated Material Function.

  5. Find the Texture Object Parameter named Basecolor Baked.

  6. Rename the parameter to Basecolor.

  7. Keep the existing connections unchanged.

  8. Save the Material Function.

This allows the Crowd material to use the original MetaHuman’s Basecolor parameter.

Step 2: Duplicate the Master Material

  1. Find M_skin_unified_baked_crowd.

  2. Duplicate it as M_MWC_CrowdFace.

  3. Open the duplicated Master Material.

  4. Replace the MF_skin_bakedInputs function call with MF_MWC_skin_bakedInputs.

  5. Rename these Static Switch Parameters:

    • Use Baked Material → Crowd Use Baked Material

    • Use Virtual Texture → Crowd Use Virtual Texture

  6. Keep the existing connections unchanged.

  7. Save the Master Material.

Renaming the switches helps distinguish the custom material’s settings from the original parameters.

Step 3: Create Actor and Instanced Material Instances

Create two Material Instances with M_MWC_CrowdFace as their parent.

MI_MWC_CrowdFace_Actor

  • Crowd Use Baked Material = True

  • Crowd Use Virtual Texture = False

  • Use PerInstanceCustomData = False

MI_MWC_CrowdFace_Instanced

  • Crowd Use Baked Material = True

  • Crowd Use Virtual Texture = False

  • Use PerInstanceCustomData = True

Make sure the necessary Material Usage settings are enabled for your Crowd representations.

Step 4: Important — Static Switch Parameters and Unreal Python

During my initial investigation, I found that the generated Material Instances had:

  • Use Baked Material = False

  • Use Virtual Texture = False

I couldn’t edit the required Static Switch Parameter directly through the Material Instance editor in that configuration.

I used Unreal Python through Codex to modify the Static Switch Parameter.

The key requirement was to enable the baked material path:

Use Baked Material = True

In my final custom material setup, I renamed this parameter to:

Crowd Use Baked Material

and configured it to True in both Material Instances.

If the parameter is editable in your Material Instance editor, you can simply enable it there. Python is not necessarily required.

If it isn’t editable, you may need to modify the parameter programmatically using Unreal’s editor scripting APIs.

Important: Changing Basecolor Baked to Basecolor alone is not the complete workaround. The baked material path must also be enabled.

I used Codex to generate and execute the Unreal Python script needed to modify the Static Switch Parameters.

Step 5: Duplicate and Configure BP_CrowdPipeline

  1. Duplicate BP_CrowdPipeline into your project.

  2. Open the duplicated Blueprint.

  3. Go to Class Defaults → Face Material Overrides.

  4. Configure all six face material slots:

Slot Name Actor Material Instanced Material
head_shader MI_MWC_CrowdFace_Actor MI_MWC_CrowdFace_Instanced
head_LOD1_shader_shader MI_MWC_CrowdFace_Actor MI_MWC_CrowdFace_Instanced
head_LOD2_shader_shader MI_MWC_CrowdFace_Actor MI_MWC_CrowdFace_Instanced
head_LOD3_shader_shader MI_MWC_CrowdFace_Actor MI_MWC_CrowdFace_Instanced
head_LOD4_shader_shader MI_MWC_CrowdFace_Actor MI_MWC_CrowdFace_Instanced
head_LOD57_shader_shader MI_MWC_CrowdFace_Actor MI_MWC_CrowdFace_Instanced
  1. Compile and save the Blueprint.

These two Material Instances are custom assets, not materials included with Unreal Engine.

Step 6: Apply the Modified Pipeline

  1. Open your MetaHuman Crowd Collection.

  2. Assign your duplicated BP_CrowdPipeline.

  3. Click Apply to rebuild the Collection.

  4. Check the face and neck in the preview.

  5. Save the Collection.

Results

After applying this workaround:

  • The white face issue was resolved.

  • The original MetaHuman face color was preserved.

  • Both High Actor and ISKM representations displayed correctly.

  • Switching between High Actor and ISKM worked at runtime.

  • The workaround worked with two different custom MetaHumans.

I tested this in Unreal Engine 5.8.4.

This is not an official Epic fix, and I haven’t verified it across every LOD or MetaHuman configuration. The underlying cause is based on my investigation and testing.

I hope this helps anyone experiencing the same issue!