Hi JoePan,

Thank you for your previous responses.
To help clarify the situation further, I’ve prepared three demonstration videos in a zp file showing the issue:

- One video using the legacy import (working correctly)

- One using the new Interchange import with "Embed Motion" enabled

- One using the new Interchange import with "Embed Motion" disabled

Summary of the current situation:

- Disabling the Interchange Plugin is not an option, as it also disables the Mesh Paint Plugin, which is required by other teams in our production pipeline.

- Installing the Auto Setup Plugin from Reallusion is also not viable, as it includes precompiled binaries and prevents us from building our custom Unreal Engine. Since source access is not available, we’re unable to fix the resulting build issues.

As a temporary workaround, we're currently importing the meshes in a separate clean project where the legacy system is still active, and then migrating the assets into our main project. However, this process is extremely tedious and inefficient. Any attempt to reimport the meshes in the main project causes them to break again — which means we must go back to the separate project for each new import or change, clean everything manually, and migrate again. This is not sustainable in a production environment.

I’m sharing the videos in case I’m missing a step or configuration in the new import process — if there’s something I’m doing wrong, I’d be grateful to hear it. But if this is a limitation or bug in the current Interchange system, I hope it can be addressed soon. The current state is a serious blocker for us, and I imagine other teams working with CC characters and facial animations will face the same issue as they adopt UE5.5 and Interchange.

Thanks again for your time and support — looking forward to your feedback.

Best regards,
Orisen

Thanks for your reply. You suggested using the Auto Setup Plugin for Character Creator, which we’re familiar with. It works as expected in standard Unreal builds, but unfortunately, it's not a viable solution for us.

We're using a custom engine build in our production pipeline, and the plugin includes precompiled binaries that interfere with our engine build process. As it stands, this blocks our developers from building the engine entirely, making the plugin unusable in our setup.

Is there any possibility of getting a source version of the plugin instead of the final binaries? If not, we’d appreciate clarity on that so we can explore alternative solutions on our end.

This is a critical issue for us, as the new Interchange system is the default going forward, and this break in compatibility is currently affecting our workflow.

Looking forward to your response.