Hair Rendering Problem When Using Reallusion Character via Live Link in Unreal Engine 5.6
I am contacting you again regarding a serious hair rendering problem that occurs when transferring a Reallusion character to Unreal Engine 5.6 through Live Link and rendering the character in Sequencer.
As shown in the attached screenshot, the character's hairstyle becomes severely distorted and corrupted during rendering. The hair does not maintain its intended shape and becomes unusable in the final cinematic output.
This is not the first time I have reported this issue.
I previously submitted this problem as an issue to Reallusion, but I did not receive a meaningful response, a clear explanation of the cause, or a working solution.
This is particularly frustrating because every time this problem occurs and cannot be resolved, I have been forced to create a completely new project and repeat the entire setup and production process from the beginning just to determine whether the problem disappears.
This means that the issue is not simply a minor inconvenience. It is causing a significant loss of development time and repeated production work.
I would like to formally raise the following concerns:
Why has this issue not been properly investigated or resolved despite being reported previously?
Why has no clear explanation been provided regarding the cause of the hair corruption?
Why have I not been given specific instructions or a reliable workaround to prevent this problem?
And most importantly, why has my previous issue report effectively received no meaningful follow-up?
When a production workflow depends on Reallusion characters being transferred to Unreal Engine, a rendering problem that can completely corrupt a character's hairstyle should not simply be ignored.
I am using the Live Link workflow specifically because it is an officially provided workflow for integrating Reallusion characters with Unreal Engine. Therefore, I expect Reallusion to provide a clear explanation when the workflow produces an invalid or corrupted rendering result.
Current environment Reallusion Character Creator / iClone Unreal Engine 5.6 Unreal Live Link Level Sequence / Sequencer Cinematic rendering The actual problem
The character can appear usable during the editing process, but when the sequence is rendered, the hair becomes severely distorted, stretched, and visually corrupted.
This makes the character unusable for cinematic production.
I need Reallusion to determine whether this is:
A Live Link problem A Character Creator/iClone hair export problem A Groom/Hair system compatibility problem An Unreal Engine 5.6 compatibility problem A material or shader issue A Sequencer/Movie Render Queue issue Or a known bug in the Reallusion Unreal integration
Please do not simply provide generic troubleshooting suggestions.
I need a specific explanation of the root cause and a reproducible solution.
Please provide:
The exact cause of this hair corruption. The correct Character Creator/iClone settings before sending the character to Unreal Engine. The correct Live Link settings for Unreal Engine 5.6. The required Groom, Hair, material, or rendering settings in Unreal Engine. The correct settings for Sequencer and Movie Render Queue. Whether this workflow is officially supported with Unreal Engine 5.6. Whether this is a known bug. If it is a known bug, the current status of the issue and the expected fix. A reliable workaround that allows me to continue working without having to recreate my entire Unreal project.
I also want to make it clear that repeatedly recreating an Unreal project is not an acceptable workaround.
I have already lost significant development time because of this issue. Every time the problem occurs, I am forced to question whether the problem is caused by the project itself, the Live Link transfer, the character, the hair system, or Unreal Engine.
Without a proper explanation from Reallusion, it is impossible to determine the actual cause, and this results in repeatedly wasted production time.
I am therefore asking Reallusion to take this issue seriously and provide an actual technical response rather than leaving the issue unresolved.
If this is a known compatibility problem, please acknowledge it clearly.
If it is a bug, please provide the bug status and workaround.
If it is caused by an incorrect setting, please provide the exact settings required to prevent it.
I would also appreciate an explanation as to why my previous report did not receive a meaningful response or solution.
This issue is directly affecting my ability to use Reallusion's characters for Unreal Engine cinematic production, and I need a reliable solution before I can continue using this workflow.
I have attached the rendering result showing the hair corruption for reference.
I look forward to receiving a specific technical explanation and a working solution.
So far, I have not encountered any major issues with AutoSetup 2.03.
There was a minor issue where the hair color appeared slightly different after the transfer, but after re-importing the character, the hair issue was also resolved.
However, I have one important concern regarding the characters I previously transferred using AutoSetup 2.01.
Do I need to delete all of the characters that were transferred with version 2.01 and transfer them again using version 2.03?
Some of these characters have already been placed in my levels, and I have already completed their dialogue and other related work. If I have to delete and re-import these characters, I would have to redo a significant amount of work from the beginning.
Therefore, I would like to know whether the existing characters transferred with AutoSetup 2.01 can remain in the project after I uninstall version 2.01 and install version 2.03.
More specifically, is it safe to update AutoSetup from 2.01 to 2.03 while keeping all of the characters that were previously transferred with version 2.01?
Will the existing characters, their materials, hair, animations, and other related settings remain fully functional after the update, or is re-importing the characters with version 2.03 recommended or required?
I would appreciate it if you could clarify the recommended update procedure, as I would like to avoid having to rebuild the existing character setups and dialogue work.
Thank you for your help.
Winner_RL
Hi ryuradop,
No worries. If you are using UE5.6, AutoSetup 2.03 works with this version. It supports 5.6, 5.7 and 5.8.
Hope this update can finally resolve your current issue. If not, please upload the iClone project to us.
Thank you!
ryuradop
Thank you for the detailed explanation.
I will update the software first and then proceed with the testing to see if the issue is resolved.
I am currently using Auto Setup version 2.01. Before I update to version 2.03, I would like to ask if there are any known issues or compatibility problems that I should be aware of when updating from 2.01 to 2.03.
Thank you for your guidance.
Winner_RL
Hi ryuradop,
We sincerely apologize that you have encountered this issue and that the troubleshooting process has taken so long. We truly appreciate your continued support of Reallusion and the trust you have placed in our tools as an important part of your project.
We completely understand how stressful this situation has been. We are continuously working to improve our users’ workflows, and we hope the following steps will help resolve the issue you are experiencing.
After reviewing your video and consulting with our R&D team, it appears that the issue may be related to collision physics data becoming corrupted when transferring your file to Unreal Engine and subsequently reopening the project. This was a known issue that our team fixed in June, and the fix is included in the latest UE Auto Setup 2.03 release (see attached image).
Could you please download and install UE Auto Setup 2.03, reopen iClone and your original iClone project, and transfer it to Unreal Engine again?
Because the collision physics data may have been corrupted during the previous transfer, we recommend starting again from the original iClone project. This will help ensure that the project is transferred from its original, unaffected state using the updated Auto Setup version.
If the issue persists, please upload your project file to our Google Drive folder so our team can investigate it further. You may need to request access first, and I will grant you permission to upload the file. This ensures that your file remains private and is accessible only to the Reallusion team.
Thank you again for your patience and continued support.
