Hi, we’re running into an issue where the new interchange fbx importer does not handle vector curve import. This worked with the legacy fbx importer and is needed in our pipeline.
Please compare the logic inside the legacy FbxAnimUtils::ExtractAttributeCurves(), which iterates over all channels and creates all curves accordingly, with the UE::Interchange::Private::CreateAttributeCurve(), which passes a single curve name and three curves to the internal function, resulting in an early bail out due to CurveNames.Num() != Curves.Num().
Is the inability to import vector curves intentional or is this an oversight?
Steps to Reproduce
I have attached a simple fbx scene created in MotionBuilder containing a cube with two animated custom properties: Number, and Vector (3d).
If you import the animation into UE, you unexpectedly only get the Number curve in the animation asset.
Disable interchange via console comand “Interchange.FeatureFlags.Import.FBX false” and retry the import.
This time there will be four anim curves: “Number”, “Vector_X”, “Vector_Y”, and “Vector_Z”.