Binary FBX export only exports one action #40040

New Issue

Mitchell Stokes · 2014-05-06T06:15:36+02:00

Mitchell Stokes commented

2014-05-06 06:15:36 +02:00

The ASCII exporter allows exporting "All Actions," but the binary version does not have this. This makes it difficult to export multiple actions. This could possibly be marked as ToDo, but it seems like a workflow bug/regression.

Here is a simple character with multiple actions.
simple_character.blend

The ASCII exporter allows exporting "All Actions," but the binary version does not have this. This makes it difficult to export multiple actions. This could possibly be marked as ToDo, but it seems like a workflow bug/regression. Here is a simple character with multiple actions. [simple_character.blend](https://archive.blender.org/developer/F87144/simple_character.blend)

Mitchell Stokes commented

2014-05-06 06:15:36 +02:00

Changed status to: 'Open'

Mitchell Stokes commented

2014-05-06 06:15:36 +02:00

Added subscriber: @Moguri

Bastien Montagne commented

2014-05-06 08:28:18 +02:00

Added subscriber: @mont29

Bastien Montagne commented

2014-05-06 08:28:18 +02:00

What do you mean by “all actions”? Get all actions as separated stacks (one stack per action, be it active or not in current scene)?

Right now, it can either export the whole scene as a single animation, or all strips in NLA as separated stacks…

What do you mean by “all actions”? Get all actions as separated stacks (one stack per action, be it active or not in current scene)? Right now, it can either export the whole scene as a single animation, or all strips in NLA as separated stacks…

Bastien Montagne self-assigned this 2014-05-06 08:29:09 +02:00

Mitchell Stokes commented

2014-05-06 09:40:50 +02:00

The ASCII exporter can export each action in the action editor as a separate track. The NLA is rarely used for game dev assets as far as I can tell.

Bastien Montagne commented

2014-05-06 09:49:33 +02:00

Well, added the NLA stuff from gamedev request… But adding another option to export everything from action editor should not be hard.

Bastien Montagne commented

2014-05-06 14:25:39 +02:00

Hrrm… In fact, I’m not quite sure how to export all actions here… 6.1 is rather limited (only handle 'all actions' case for armatures/bones).

Issue is, in Blender, actions are not linked to a specific object (you can assign the same action to any object you like, even incompatible ones like e.g. armature with posedbones to a mere mesh, invalid fields will just do nothing). However, in FBX, animation stacks always are linked to a specific object.

So what I can do is:

loop over all actions in .blend file (not in current scene, since actions are main data, not scene ones).
export one stack per action per compatible object.

Note this will make stack count explode with more than a few actions and/or objects in the scene.

Also, we have to define what 'compatible' means:

At least one channel of the action is valid with the object?
Or all channels of the action are valid with the object?

Moving from bug to design task, this is TODO anyway…

Hrrm… In fact, I’m not quite sure how to export all actions here… 6.1 is rather limited (only handle 'all actions' case for armatures/bones). Issue is, in Blender, actions are not linked to a specific object (you can assign the same action to any object you like, even incompatible ones like e.g. armature with posedbones to a mere mesh, invalid fields will just do nothing). However, in FBX, animation stacks always are linked to a specific object. So what I can do is: * loop over all actions in .blend file (**not** in current scene, since actions are main data, not scene ones). * export one stack per action per compatible object. Note this will make stack count explode with more than a few actions and/or objects in the scene. Also, we have to define what 'compatible' means: * At least one channel of the action is valid with the object? * Or all channels of the action are valid with the object? Moving from bug to design task, this is TODO anyway…

blender-admin commented

2014-05-06 20:22:17 +02:00

This issue was referenced by f125c03bdf

This issue was referenced by f125c03bdf5c2ed8c63b11b6fcec6ff4d33fb026

Bastien Montagne commented

2014-05-06 21:13:18 +02:00

Changed status from 'Open' to: 'Resolved'

Bastien Montagne closed this issue

2014-05-06 21:13:18 +02:00

Bastien Montagne commented

2014-05-06 21:13:18 +02:00

Closed by commit f125c03bdf.