Home > Supported File Formats > CADMATIC to COLLADA

How to convert CADMATIC (3DP) to COLLADA (.dae)?

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.

CADMATIC

Okino and Cadmatic have collaborated for many years to create a fluid 3D conversion pipeline from Okino's CAD importers into Cadmatic 3D Plant software. This is achieved through a custom 3D export converter module for Okino software which creates "3DP" files. Such files can then be loaded into Cadmatic's 3D plant design software.

This custom solution allows Cadmatic users to source from all primary MCAD and CAD programs, resulting in highly optimized, clean and robust 3DP files. Commonly requested source MCAD programs include SolidWorks, ProE/Creo, IGES solids, STEP solids, PARASOLID solids, DWF-3D, (for the technically best AutoCAD, NavisWorks, Revit, Inventor conversions) DXF/DWG, JT and basically all other top named MCAD programs.

The 3DP Exporter plug-in for Okino software is developed and maintained by Cadmatic. Please contact them directly to obtain the 3DP installer.

If you wish to convert from the Cadmatic 3D Plant software into other BREP solids modelling programs (such as SolidWorks, Unigraphics NX, Siemens Team Center, ProE/Creo CATIA, etc.) then please contact Cadmatic directly for their speciality methods and processes. Such processes are not provided by Okino software as its requires special processing of data from the 3D Plant software. As examples, Cadmatic 3D Plant can export JT "solids-based" files for Unigraphics NX and Siemens Team Center, while the use of a local copy of AutoCAD allows Cadmatic 3D Plant datasets to be converted into "solids" for Autodesk Inventor and other programs.

COLLADA

COLLADA (DAE) is a XML-based readable file format of the 2007/2008 era which had an original goal of allowing efficient cross conversion of 3D asset data between all of the major 3D DCC/Animation systems of that era. Many 3D software programs came to implement COLLADA but with varying levels of comformity and data reliability. COLLADA is more generally known as a polygonal mesh file format and not a MCAD/CAD/AEC/GIS format. Today people would usually use FBX over COLLADA, depending on the quality of the associated (and dated?) import/export converters.

Okino created one of the key implementations of the COLLADA file format in its import and export converters. However, it saw little need for them except for exporting into Cinema-4D from 2008 to 2012, as the primary gateway into Google Earth, and as our still-preferred method to move 3D assets into Blender (rather than FBX). COLLADA does have its place in these current and prior times.

Okino has a unique take on the COLLADA file format as Okino was at the very center of the DCC/Animation conversion world. In 2007 Rémi Arnaud and Mark Barnes argued that yet-another 3D file format was required and hence Sony funded their efforts to define COLLADA for the cross conversion of assets between (initially) 3ds Max and Maya. However, what they conveniently ignored was that Okino already had the defacto cross conversion system in place, for the prior decade, based on its BDF (binary data translation file format) for 3ds Max, Maya, Cinema-4D, Softimage, LightWave and others. In the mid 2000's there was a "not invented here" mindset and hence everyone wanted to stamp/force their own 3D file format on the industry: FBX (Autodesk), COLLADA (Sony), 3dxml (Dassault Systems), XAML-3D (Microsoft), U3D (Adobe and Intel), etc. There was little need or reason to have "yet-another" set of new 3D file formats. All, except FBX, would basically come and go as of 2007/2008. The implosion of the DCC/Animation industry of 2005-2007 and the 2008/2009 recession further hampered the long term adoption or need for COLLADA over Autodesk's FBX.

COLLADA is/was a very fine file format but it was really not needed at the time of its introduction in 2007. It only introduced yet-more confusion to the 3D graphics market as to which 3D file format to use to transfer 3D assets between packages. Developers generally implemented v1.4 of the COLLADA file specification then lost interest thereafter.

However, as a saving grace for COLLADA, all of the 3D software packages which had implemented a good COLLADA exporter became instant gateways to move their 3D assets into the then-new glTF file format of the mid 2010s, until such time that these same packages could add in their own glTF exporters.

PolyTrans|CAD for CADMATIC

CADMATIC import converter's overview

COLLADA export converter's overview