Hello everyone!

In the next major release of FBX (2013), we are planning a major change to the whole API. We are putting a lot of efforts to bring the API to a consistent level. Since the modifications are major, we wanted to let you know that your code calling FBX SDK API will most likely be broken upon upgrading to FBX SDK 2013.

What are we doing exactly?
- Renaming almost every class/structure of the FBX SDK to a consistent way.
- Moving enumerations inside classes.
- Grouping logical classes/functions together.
- Renaming file names and path names.
- Removing a lot of deprecated code.
- Exposing previously private classes.
- Unifying usage of internal classes.
- ...and many more small clean-up changes all over the place!

In this release, we will not have any deprecated calls, since this would mean the whole SDK would be deprecated. This also means a lot of functions or classes will not be available anymore, and sometimes without replacements. At some point we needed to look back and make some decisions about what the FBX SDK should offer. Decisions were mostly motivated by the fact that the FBX SDK has grown pretty large over time, and inconsistent in a way. This is ok, we’ve been working on it for almost two decades now. ;)

FBX 2013 will not be ready for a while still, we just wanted you to be aware of the upcoming major changes, and we hope to upload a build on the Beta boards eventually, thought I cannot provide any precise schedule. We are very excited with the API face-lift, and we hope you will all like the FBX SDK API rejuvenation we are working on for some time now!

If you have any questions or comments about this topic, please do not hesitate to ask below! Thank you!

-Robert Goulet

Robert Goulet, FBX Dev Lead

Aside from the the API, will there be changes in the FBX file format?

I assume that FBX SDK 2013.x will be compatible with python3.2, is that correct?

However, have you guys considered rebuilding the current release for python3.2?
There are some environments where this version of python is a natural choice
and being stuck to python3.1 due to the lack of support from FBX SDK is a little
uncomfortable, to say the least :)

Howdy,

Will it be rock solid and more stable (crash resistant) when using with other api’s, for example in a non Autodesk application plugin project?

Edit:
If you don’t understand exactly what I mean, take a look at my post in this thread over at the Cinema 4D plugin developer support forum:
http://www.plugincafe.com/forum/forum_posts.asp?TID=5845&PID=24471#24471

Adios,
Cactus Dan

Hi Robert,
I’m sorry, what I am going to talk about may be not directly related to this topic, but it is very important to me . I hope you can help me . Thank you forward!
My problem is I find that memory leak occurs when I Load a .3ds file using FBXSDK 2011.3.1or 2012.1.
I have done a simple project in vs2005 to test whether memory leak occurs when loading .3ds files or .fbxs file or .obj files using FBXSDK 2011.3.1 .
The result of the test is that when loading .3ds files, memory leaks. When loading .fbx files or .obj files memory is OK.
The attachment is the test project, I hope you can help to find whether the memory leak is due to my misapplying of the FBXSDK.

Thanks a lot.

ZOU

	Attachment
fbxsdk2011_test.zip

Will the new FBX enable us to read AutoDesk materials. for example Revit FBX includes internal binary material description that makes it unreadable by none AutoDesk application which forces us to request users to install a Revit plugin to export formats other than FBX.

If the new version will enable us to access those materials, this will be a great plus.

Hi simlab,

The materials that are in Revit can only be used in AutoCAD, Navisworks, Showcase and 3dsMax.

There is an option on the command-line FBX Converter, called /matconvert, that will convert the objects in the original file to be Materials. However, no color or texture information will be included. The converted file will be able to have materials applied in correctly with the names of the materials that were used in the Revit file.

Viviane Rochon
Maya Data Platform
Autodesk

Howdy,

Will the new version support spline IK? Since it already supports IK and constraints, it would be nice to also have spline IK support so that a fairly complete character rig could be exchanged between applications.

Adios,
Cactus Dan

Hello,

I’m working with the FBX sdk for couple of months and so far it is extremely helpful tool.
Our project is based on Direct3D rendering engine using Left Handed coordinate system.
The conversion methods of the KFbxAxisSystem class are not working well for us and we have to overcome some issues using our own conversion matrices.
It would be nice to know if a fix for that issues is planed for the upcoming version.

Cheers,

Nir

Do you have a timeframe for the alpha release and instructions to apply?

Thanks,
Kev

+1 for Python 3.2, I want to write an FBX importer for Blender,

the latest version comes bundled with 3.2,

checked out the latest SDK (2013.2), unfortunately still no Python 3.2 available.

It’d be much appreciated, thanks guys for the awesome SDK. :)