According to the [Animation Curves documentation][1], the preferred way to create morph target animation is using our 3d animation software; however, any tangent adjustments made to curves in the 3d software are discarded on import despite tweaked tangents being supported in the editor (though the tools for this behave in a different, undesirable way).
Unlike with morphs targets, modified curve tangents on other types of animation (translation, rotation) import as expected.
EDIT: I may as well clarify what I mean by “undesireable”.
In addition to the curve adjustment window being small and apparently non-resizeable, the way handles work inside this specific editor is really odd.
Unlike Bezier handles like in 3dsMax or anywhere else, it’s not possible to create a vertical, or even near-vertical tangent in the curve editor without the resulting curve shooting way off the chart like this:
The steepest Unreal’s tangents can go without going completely nuts is something like the “editor adjusted curve” above, which is comparable to Max’s “fast” tangents.
As a test I tried exporting with fast tangents, but Unreal’s importer discards those too, which really does make me think this is a bug and not some odd limitation of Unreal’s curve editor.
Thank you for your report. We were not able to investigate this on the engine version you reported, but there have been many version changes to UE4 since this question was first posted. With a new version of the Engine comes new fixes and it is possible that this issue has changed or may no longer occur. Due to timetable of when this issue was first posted, we are marking this post as resolved for tracking purposes.
If you are still experiencing the issue you reported in the current engine version, then please respond to this message with additional information and we will investigate as soon as possible. If you are experiencing a similar, but different issue at this time, please submit a new report for it.
I don’t have access to the current engine version, but I don’t remember seeing anything about this in the patch notes. Have the full patch notes for each version been written down in some place where I can look over them and see if this bug has been fixed any time in the last 3.5 months?
If not, do you have the ability to test this problem with the current version? I think my report was pretty comprehensive, but if there was anything unclear please let me know.
I can see that we’ve got some things planned around this functionality with animations, but I can’t test it on our internal build as it doesn’t appear to be implemented, at least not in the build I’m using.
