Character Creator4 export and import breaks facial morph


https://forum.reallusion.com/Topic538797.aspx
Print Topic | Close Window

By rep.of.banana - 2 Years Ago
I've come across an issue involving the CC Pipeline Addon and Blender. Specifically, the expression morph gets broken when I import a CC4 character to Blender, and then import it back to CC4.
At first, I thought this was a problem related to the pipeline plugin. However, I've realized the issue can easily be reproduced using only CC4. This suggests the problem lies within CC4 itself.
It's worth noting that I've been using this workflow since the days of CC3. Interestingly, this problem never occurred with CC3.

The Environment Settings:
- CC4: Version 4.12 and 4.3
- Windows 10

Below, I've outlined the procedure to reproduce this issue. Could you please check if others are experiencing the same problem?

1. Load any CC4 default character


2. Export FBX (the setting is what I usually use)
https://forum.reallusion.com/uploads/images/d66f6f02-2dd8-457b-9909-412a.jpg

3. When load exported FBX again, this dialog appears


4. And the facial expression is btoken
By 4u2ges - 2 Years Ago
It looks like a bug in FBX import routine with an older base (CC1 CC3) utilizing Traditional expressions profile.
They probably neglected to test it during release. Feel free to report it to Feedback Tracker.
While it should be fixed, you may avoid it meantime by switching profile to Standard before the Export out of CC.

Or if you already imported character back as Traditional, then go to Expression Editor and do Batch Load from the same FBX.
That would fix the order of blend shapes for Traditional profile and expressions would be OK.

There is also another bug with CC1/CC3 bases while importing from FBX.
The body materials have diffuse map applied to Glow channel. :w00t:

https://forum.reallusion.com/uploads/images/430ebdf4-bc63-48d5-be6e-83c1.jpg
By rep.of.banana - 2 Years Ago
Hi, 4u2ges.
Your advice solved my issue. I didn't even know there is a facial profile...
I'll report this as a bug. Thank you so much for your reply.