FBX exporter animation artefacts #50940

New Issue

Storm · 2017-03-14T11:00:23+01:00

Storm commented

2017-03-14 11:00:23 +01:00

System Information
Windows 10
GTX 970

Blender Version
Blender 2.78c

Short description of error
Exporting an animation to FBX produces artefacts when viewing the results either through FBX Review or when importing back into Blender

Exact steps for others to reproduce the error
Open the attached Blender file and hit play to observe the animation. Note how the feet are perfectly stationary while the character bends its knees.

Now export to FBX. In the FBX export panel, under animation, set Simplify to zero and uncheck the All Actions check box. Enter a filename and click on the Export FBX button.

Now either view with FBX Review or import back into Blender, set the end frame to 40 and play the animation. Observe how the feet are no longer stationary.

Below is the blender file for testing. FBX ExportTest.blend

**System Information** Windows 10 GTX 970 **Blender Version** Blender 2.78c **Short description of error** Exporting an animation to FBX produces artefacts when viewing the results either through FBX Review or when importing back into Blender **Exact steps for others to reproduce the error** Open the attached Blender file and hit play to observe the animation. Note how the feet are perfectly stationary while the character bends its knees. Now export to FBX. In the FBX export panel, under animation, set Simplify to zero and uncheck the All Actions check box. Enter a filename and click on the Export FBX button. Now either view with FBX Review or import back into Blender, set the end frame to 40 and play the animation. Observe how the feet are no longer stationary. Below is the blender file for testing. [FBX ExportTest.blend](https://archive.blender.org/developer/F508884/FBX_ExportTest.blend)

Storm commented

2017-03-14 11:00:24 +01:00

Changed status to: 'Open'

Storm commented

2017-03-14 11:00:24 +01:00

Added subscriber: @Eliminati0n

Bastien Montagne commented

2017-03-14 14:06:00 +01:00

Added subscriber: @mont29

Bastien Montagne commented

2017-03-14 14:06:00 +01:00

Changed status from 'Open' to: 'Archived'

Bastien Montagne closed this issue

2017-03-14 14:06:00 +01:00

Bastien Montagne self-assigned this 2017-03-14 14:06:00 +01:00

Bastien Montagne commented

2017-03-14 14:06:00 +01:00

FBX exporter bakes and applies some simplification to animations (to save some space). Setting Simplify parameter to zero in Animation settings of the exporter should fix that.

We do not handle user support on this tracker, only bug reports. User forums like blenderartists.org or blender.stackexchange.com should be used for that matter.

FBX exporter bakes and applies some simplification to animations (to save some space). Setting Simplify parameter to zero in Animation settings of the exporter should fix that. We do not handle user support on this tracker, only bug reports. User forums like [blenderartists.org](http:*blenderartists.org/) or [blender.stackexchange.com](http:*blender.stackexchange.com/) should be used for that matter.

Storm commented

2017-03-15 02:41:22 +01:00

Thanks for your reply Bastien,

I am setting Simplify to zero (please see my instructions for reproducing the problem) and this is still happening.

Hence why I think this is a bug.

Thanks for your reply Bastien, I am setting Simplify to zero (please see my instructions for reproducing the problem) and this is still happening. Hence why I think this is a bug.

Bastien Montagne commented

2017-03-15 08:16:43 +01:00

Changed status from 'Archived' to: 'Open'

Bastien Montagne reopened this issue

2017-03-15 08:16:43 +01:00

Bastien Montagne commented

2017-03-15 08:16:43 +01:00

Eeek, OK, sorry, missed that part of your description somehow :|

Can confirm the issue, not sure where it comes from… off hands would suspect some floating point precision issue, but will have to check further.

Eeek, OK, sorry, missed that part of your description somehow :| Can confirm the issue, not sure where it comes from… off hands would suspect some floating point precision issue, but will have to check further.

Brendon Murphy commented

2019-06-11 11:27:19 +02:00

Added subscriber: @BrendonMurphy