Votes
2
Product:
Character Creator 4
Version:
4.54
Status:
Not Reproducible
Issue 12078
Auto Setup for Unreal Engine crashes UE5.6 on import
UE5.6: Crashes (Version 1.39.7803.1 (for UE 5.6))
UE5.5: Untested
UE5.4: Works as expected (Version 1.38.7513.1 (for UE 5.3–5.5))

Tried both "Standard Shader" or "HQ Shader" when importing. Seems irrelevant.

FBX Import Options:
Skeletal Mesh: Checked
Import Mesh: Checked
Use T0 as Ref Pose: Checked
Import Morph Targets: Checked
Import Animations: Not Checked (Tried both. Seems to crash before this. So not relevant.)

I have followed this: https://courses.reallusion.com/home/character-creator/pipelines-and-render/unreal?v=iclone-8-and-cc4-tutorial-auto-character-setup-for-unreal-engine-5
and this: https://courses.reallusion.com/home/character-creator/pipelines-and-render/unreal?v=updated-workflow-for-unreal-engine-5-5-auto-setup-%7C-character-creator-4-tutorial

Disabling Interchange Plugins does not appear to make a difference.

Characters:
I have tested with a modified version of Alika (Stylized)
I have tested with stock CC4 Camila (Just to make sure it's not something I have done.)
Both result in the same crash and message.

UE5.6 crashes with the message:
Assertion failed: MipView.GammaSpace == LayerData.SourceGammaSpace [File:D:\build\++UE5\Sync\Engine\Source\Runtime\Engine\Private\TextureDerivedDataTask.cpp] [Line: 422]
in UnrealEditor_Core

Current workaround is to use UE5.4. Untenable long term.
OS: Windows 10
  •  4
  •  540
BugPipeline (Export/Import)Auto Setup for Unreal
Submitted byfeaturebugentertainment
1
COMMENTS (4)
Feedback Tracker Admin 
HI featurebugentertainment

Thank you for your reply. We're glad to hear that the issue has not occurred again.
Our team is continuing to investigate and attempt to reproduce the problem on our end.

However, if the crash happens again, please don’t hesitate to contact us.
When you do, we kindly ask that you include the file and project you were using at the time, so we can better trace and analyze the issue.

We appreciate your cooperation and understanding. Please let us know if you need any further assistance.

KaylaYang
Reallusion
featurebugentertainment 
It just stopped crashing...

I decided to capture some video, in order to see what the last thing it attempted to load was. (They were flying by pretty fast.) Windows' capture failed to capture anything other than the focused window, missing all of the pop-ups. It did not crash however.

I tried again, without the capture, figuring the capture may have slowed it down enough to avoid a race condition or something. Nope, still didn't crash. Character loaded just fine. Just like in UE5.4.

So I attempted a restart, to see if it would revert to crashing on import. Nope. Imports just fine.

I have tried with CC4 running in the background. With the Hub in the background. With both. Small UE5.6 window. Fullscreen UE5.6 window. Firefox running 10 youtube videos in the background. Anything I might have been doing differently.

I can no longer get it to crash on import. Don't get me wrong, I'm not complaining. But I'm at a loss as to what might have been causing the crashes. As I've been importing the same character.fbx the whole time.
featurebugentertainment 
Attached System Information file.
Attached Memory graph from starting UE5.6 and importing.

Total Memory: 32768MB

After a reboot:                     21% Memory
Epic Launcher Started:      22% Memory
5.6 Test Project Opened:   32% Memory
Max usage during import: 37% Memory
Drops back down to 22% upon crash.

Hmmm. I can't say I'm noticing anything unexpected. I could check VRAM as well, I guess.
Attachment:
  • UE56Crash.png
Feedback Tracker Admin 
HI featurebugentertainment

This issue has been received by us.
we would like to further confirm some details and kindly ask you to provide the system information to help us proceed with a more in-depth investigation.
Please follow the instructions provided at the following link to export the required information.

https://www.reallusion.com/FeedBackTracker/Home/HowToGet

Additionally, could you please try importing it into UE again, and check the memory usage on your system at the time of import?
We’ve recently identified that some users have experienced similar issues, which appear to be related to memory usage.
When system memory reaches a certain threshold, such issues are more prone to happen.

KaylaYang
Reallusion
1