Root motion is not exported to .fbx and so is incompatible with Unreal Engine 4
I am trying to use iClone to bring characters and animations in to Unreal Engine . Specifically, I am using CC2 to create characters, Perception Neuron Solo to record animations, and 3DXchange to convert existing animations to the iClone standard.
I have been successful in importing characters as when you export from iClone 7 there is an option to match the UE4 skeleton and this includes the root bone. I can then use existing animations which have root motion - this is great!
The problem is with exporting animations from iClone. They match the skeleton, but exclude the root bone animation track. If there was root motion in the animation file then the root bone would be directly under the hips and a red line would trace the avatar's path.
I have also tried exporting using 3DXchange. This also does not include root motion and, in addition, does not match the UE4 standard skeleton. If it were able to export root motion I would consider batch converting all of my existing animations and using the 3DXchange skeleton, but at the moment there is no benefit to that.
I've tested to see if it is my animations by importing an animation which I know to have root motion to 3DXchange and exporting it for UE4. I find that the root motion has been removed.
This seems to be a bug with the FBX export in both iClone and 3DXchange, because the functionality in iClone strongly suggests root animation. For example, the ability to "align > root". Further, the export license and ability to export for "Unreal" strongly suggests compatibility with UE4. No root motion means no compatibility.
Software details: iClone 7 iClone 3DXchange 7 Pipeline Character Creator 2 for iClone CrazyTalk 8 Pipeline.
Was about to commit to the same pipeline as described here. Would also like to know this works before proceeding with purchase.
AstonALIVE
Have you had a chance to look at the video yet?
AstonALIVE
Here is a link to the video: https://youtu.be/qzmOYIxajdI It just shows what has been described in the original post.
I have had an open support ticket for one month now which has not been addressed by any developers. Will someone be able to look at it now?
If it helps, my understanding is that this bug was not present in version 6.2 of iClone and has only been introduced recently. I have not tested this myself as I have not got a copy of iClone 6. Forum posts seem to suggest this was the case.
Feedback Tracker Admin
Thank you for your feedback.
Please capture a screen video about this issue, put it on the YouTube, and add the link in your next comment.
Your help is highly appreciated.
Reallusion
