Home > Supported File Formats > DirectX to FBX

How to convert DirectX (.x) to FBX (FilmBox v5/v6/v7,.fbx)?

PolyTrans|CAD+DCC performs mathematically precise CAD, DCC/Animation, GIS and BIM 3D file conversions into all key downstream 3D packages and file formats. Okino software is used and trusted throughout the world by many tens of thousands of 3D professionals in mission & production critical environments, backed by respectable personal support directly from our core development team.

DirectX

.x files are the native 3D file format of the legacy Microsoft DirectX v2/v3 API and 3D toolkit. They were generally associated with 3D gaming whereby low polygon meshes with skinning (deformation) and "animation sets/clips" were the required norm. At the time of its introduction in 1995 there really wasn't any other similar 3D file formats which supported these capabilities in one, well defined and easily accessible format. Direct3D shipped for the first time in the DirectX 2.0 SDK in June 1996

Historically, the DirectX technology was developed a company called Rendermorphics of the UK which Microsoft purchased in February 1995. As little known history, 3 companies in the UK developed advanced realtime rendering toolkits prior to 1995: Argonaut Software (BRender), Criterion Software (RenderWare) and Rendermorphics (Reality Lab). Microsoft was to license the Argonaut 3D toolkit but opted to purchase the entire Rendermorphics company instead, at the last moment. As these various toolkits often sold for $50k at that time, the other two competitors eventually went out of business once Microsoft started giving DirectX away for free.

Okino knows of the .x file format well as it was the first company to properly and fully implement a DirectX importer and exporter, including full support for skinning and animation at a time when no other software provided such conversion support.

The DirectX file format had a long life until some people inside and outside of Microsoft started to push the FBX file format instead.

FBX

FBX is a 3D 'digital asset interchange' file format that had been pushed on the 3D industry by Autodesk after they acquired it from the bankruptcy assets of its prior owners, Alias Research and Kaydara of Canada. FBX has its placed in the DCC/Animation world but it does have its limitations, given that it is a closed and proprietary file format of Autodesk.

Note: if you are one of the many people who use FBX to convert data out of Navisworks, Revit, AutoCAD or Inventor then please use DWF-3D file format and Okino's DWF-3D import converter instead. It is a night and day difference but little known except to our core Okino users. Likewise, use our native program support for 3ds Max, Maya and Cinema-4D rather than use FBX.

FBX supports all the common attributes of a DCC/Animation file format such as mesh geometry with vertex normals and vertex colors, non-solids NURBS ('old school NURBS'), lights, cameras, hierarchy, bones and mesh skinning (deformations), materials and textures. In basic terms, it is similar to the capabilities of the COLLADA and VRML2/X3D file formats, and to Okino's long standard BDF data translation file format.

Okino has a very long history associated with FBX as it created the very first and fully implemented set of FBX import and export converters in 2002, with full animation, skinning and trimmed NURBS support. This was long before anyone had much heard of FBX. And to this very day we are still the only company that actively ships and supports FBX v5 (Kaydara), v6 (Alias) and v7 (Autodesk). However, FBX was just one of many 'not invented here' file formats which came to glut the 3D market in the 2005-2007 era, many of which petered away over time.

A key reason for its early adoption, throughout the 3D industry, was the availability of a free and officially supported (but closed) FBX SDK from Autodesk.

The downsides of the FBX file format is that (1) it has stagnated in recent years, (2) it is based on a legacy material model and not on modern PBR, (3) it is based on legacy lighting models and not on physically based lighting, and (4) it is a closed file format which only Autodesk can update or change. Otherwise, these restrictions have made it easier for software developers to implement FBX just once and then not have to worry about costly yearly revisions.

DirectX import converter's overview

FBX export converter's overview