Crash Creating Metahuman Character

Development Character & Animation
, ,
1

Hi there,

When attempted to create a MetaHuman Character, I’m encountering an Editor crash. I’ll attach the traceback. To reproduce the steps,

Plugins enabled:

  • MetahumanCoreTech
  • MetahumanCharacter

The steps:

  1. In the Content Browser, I right-click and select Metahuman > Metahuman Character
  2. Wait for creation or to save
  3. Crash…

Project is UE 5.7.1 built from source via Perforce (not GitLab). Details from the build.version file:

{

“MajorVersion”: 5,

“MinorVersion”: 7,

“PatchVersion”: 1,

“Changelist”: 0,

“CompatibleChangelist”: 47537391,

“IsLicenseeVersion”: 0,

“IsPromotedBuild”: 0,

“BranchName”: “UE5”

}

I can’t say for sure if this is related to the Metahuman Creator Core Data. Is that available somewhere in Perforce to grab?

Do you have any advice on how to proceed? I want to rule out issues with our build process, as opposed to something else!

Thanks so much,

Eoghan

[Attachment Removed]

2

Confirming that this is happening with UE5.7.2 build as well.

[Attachment Removed]

3

Hi Eoghan,

Yes, the MetaHuman Creator Core Data was my first thought as well, however Unreal Engine should not (/does not normally) crash when this is missing.

Can you check if you have a Setup.bat folder in the root of the source folder? If you run this is will download binary content for the engine which includes the MetaHuman content.

Mark.

[Attachment Removed]

4

Good morning and thanks for the response!

Confirming that we do not have a setup.bat file in the mirror from your, to our, Perforce. Depot image attached.

Thanks again, Mark.

Eoghan

[Image Removed]

[Attachment Removed]

5

Confirming that we don’t see a Setup.bat file in our proxy.

[Image Removed]Do you have advice on how we might dig into this further?

Thank you!

[Attachment Removed]

6

OK - let me investigate this further with the team.

Mark.

[Attachment Removed]

7

Are there any non-ascii characters in the folder path for the source code/project/etc?

[Attachment Removed]

8

Thanks Mark.

No, no non-ASCII characters in the folder paths for any of the engineers building UE here.

[Attachment Removed]

9

Checking with the team the MetaHuman Creator Core Data should be part of the Perforce stream by default, assuming you have synced the whole stream. Apologies for the confusion with the Setup.bat file - this is only necessary if cloning from GitHub.

To double check, the MetaHuman Creator Core Data should be visible under /Engine/Plugins/MetaHuman/MetaHumanCharacter/Content/Optional if you want to double check it is there.

However, the callstack shows the editor is failing to load a DNA file which is not part of the optional content. We have seen crashes on paths with non-ascii characters, however you have ruled that out.

Are you able to provide the editor log so we can investigate further? Have you made any changes to the editor, or are you just building from a clean sync?

Thanks,

Mark.

[Attachment Removed]

10

For sure!

Attached here. I’ve removed lines that reference the other found urprojects on my machine and highlighted inline.

Thanks for confirming the MetaHuman data is in the Perforce stream already.

Running with Nvidia drivers: 582.16

Thanks Mark!

[Attachment Removed]

11

Thank you for sharing the log - unfortunately it doesn’t point to anything obvious.

One thought is the DNA file being read has become corrupt some how. Are you able to debug or print the DNA file that is being loaded? This should be in the FMetaHumanCharacterSkelMeshUtils::GetArchetypeDNAAseet() function, the first argument DNAPath passed to the GetDNAAssetFromFile().

Thanks,

Mark.

[Attachment Removed]

12

Also, are you able to try this from a fresh sync of at least the entire Engine/Plugins/MetaHuman folder from our Perforce?

Our working assumption at the moment is one of the files is corrupt (rather than missing) as we’ve not seen this error before and are unable to replicate it so far.

[Attachment Removed]

13

Copy. Testing, and I’ll report back!

[Attachment Removed]

14

I’ll be OOO tomorrow, but I’ll build tonight and report back on Monday.

Thanks, Mark!

[Attachment Removed]

15

Hi Mark and Team,

We’ve found a smoking gun on our end regarding the .dna files and we’re looking into it. There’s some disparity in metadata on those files between our servers.

I think it’s safe to close this ticket on your end. I really appreciate the help!

[Attachment Removed]

16

Ah, thank you for letting us know, Eoghan.

Mark.

[Attachment Removed]