UE 5.5.1 - IMPORT PROBLEMS:: New Interchange interface imports Maya single FBX animations into 2: skeletal and morphs, WHY?

Development Programming & Scripting
, , , , ,
1

Hello, the new Import “Interchange” menu creates 2 sepparated animations when importing single FBX files (animations) from Autodesk Maya, 2 sepparated files instead of 1:

  • 1 animation file with all the morph target animation data but no skeletal animation
  • 1 animation file with the skeleton data and no morph animation,

making a total of 2 animations instead of importing the original single FBX animation file from Autodesk Maya, it sepparates morph animation from skeletal.

My testings:
All Maya settings are as usual, no different option from previously used for UE5 to UE5.4, but… I have tested diferent FBX versions just in case (animation already baked as usual)

UE 5.5.1 New Interchange interface has a ton of new settings, I have tried many of them to try to avoid this issue, just as a test:

  • enable/ disable Remove redundant keys
  • enable/ disable Merge morph targets with same name
  • enable/ disable Animation Only
  • enable/ disable Bake Meshes
  • enable/ disable Do not import curves with only 0 values
  • enable/ disable Delete existing morph target curves

and many more… still no solution, it keeps importing sepparated animation files.

2

FIXED… but not solved, got no answers but kept trying and:

Just disable the new “Interchange” interface, go to plugins and disable everything called “Interchange”, this will bring back the normal import menu and by just choosing your skeletal mesh while importing the animation and 1 click, UE 5.5.1 will import the original FBX animation in 1 file without splitting curves and skeletal animation and making 2 useless files.

I tried every other check box option in the new Interchange menu and even created my own animation import profile wich is a feature of this interface, in order to make faster testings, but nothing fixed this problem, you will have to uninstall the new Interchange interface,

can’t mark it as a solution, since this might actually be a bug in UE 5.5

3

Hello

  1. that should be fixed in 5.5.2 that is released this week.
  2. If you must deactivate interchange I would recommend doing it through the CVar so you can deactivate it only for FBX
    Interchange.FeatureFlags.Import.FBX false