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