FBX branch animation import bugs #40729

New Issue

levon hudson · 2014-06-20T15:19:45+02:00

levon hudson commented

2014-06-20 15:19:45 +02:00

2 small bugs with the newish animation importing.

data isnt linked to the object
the animation data is imported, and named correctly, but the animation datablock isnt linked to the object
animation data doesnt take into account the world up and forward axis.
animation keyframes are imported based on their names in the fbx file, and does not take into account any world space transformations the FBX script applies to object locations and etc.

2 small bugs with the newish animation importing. 1. data isnt linked to the object the animation data is imported, and named correctly, but the animation datablock isnt linked to the object 2. animation data doesnt take into account the world up and forward axis. animation keyframes are imported based on their names in the fbx file, and does not take into account any world space transformations the FBX script applies to object locations and etc.

levon hudson commented

2014-06-20 15:19:45 +02:00

Changed status to: 'Open'

Bastien Montagne was assigned by levon hudson

2014-06-20 15:19:45 +02:00

levon hudson commented

2014-06-20 15:19:45 +02:00

Added subscriber: @LevonHudson

Bastien Montagne commented

2014-06-20 16:29:17 +02:00

Point 1 is not a bug. Issue is, we can't decide which animation to 'assign' to which object (in Blender, there is only one action per object, while in FBX you can link as much animationstacks/layers/curvenodes as you want to a same object). We could e.g. just pick the first one available for an object, but this is rather arbitrary. And I won’t dive in the Hell of trying to rebuild a full NLA equivalent of the FBX animation system, things are enough complicated with this basic support! :)

Point 2 sounds rather odd to me… Will have to check again, but iirc I did especially take care to apply same transformations to animated loc/rot/scale as the ones applied to static Lcl transform values (which complicated quite a bit the code, btw, since e.g. animated Y value could become X value in Blender…). :/

Point 1 is not a bug. Issue is, we can't decide which animation to 'assign' to which object (in Blender, there is only one action per object, while in FBX you can link as much animationstacks/layers/curvenodes as you want to a same object). We could e.g. just pick the first one available for an object, but this is rather arbitrary. And I won’t dive in the Hell of trying to rebuild a full NLA equivalent of the FBX animation system, things are enough complicated with this basic support! :) Point 2 sounds rather odd to me… Will have to check again, but iirc I did especially take care to apply same transformations to animated loc/rot/scale as the ones applied to static Lcl transform values (which complicated quite a bit the code, btw, since e.g. animated Y value could become X value in Blender…). :/

levon hudson commented

2014-06-21 07:38:42 +02:00

i did an export out of maya, camera moving in x, y, z, and then rotating 90d x,y,z. reimport into maya works fine. see the screen shots.

note that i have Z up, Y forward when exporting out of maya, And Maya exports the curves a bit dodgy due to gimbal lock.

new_export_zup.fbx

i did an export out of maya, camera moving in x, y, z, and then rotating 90d x,y,z. reimport into maya works fine. see the screen shots. note that i have Z up, Y forward when exporting out of maya, And Maya exports the curves a bit dodgy due to gimbal lock. ![maya.png](https://archive.blender.org/developer/F95098/maya.png) ![blender.png](https://archive.blender.org/developer/F95100/blender.png) [new_export_zup.fbx](https://archive.blender.org/developer/F95102/new_export_zup.fbx)

Bastien Montagne commented

2014-07-21 17:49:06 +02:00

Changed status from 'Open' to: 'Resolved'

Bastien Montagne closed this issue

2014-07-21 17:49:06 +02:00

Bastien Montagne commented

2014-07-21 17:49:06 +02:00

Camera orientation correction was wrong it seems, fixed in 944016ab78.

As already said, point 1 is not considered a bug, so will close now, thanks for the report.

Camera orientation correction was wrong it seems, fixed in 944016ab78. As already said, point 1 is not considered a bug, so will close now, thanks for the report.

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

FBX branch animation import bugs #40729