Product Descriptions

CentOS uses GCC 4.8.5 and we are compiling native libraries with a more recent GCC version. You will get the following error if you’re using Drawings for Java:

java.lang.UnsatisfiedLinkError: /lib64/libstdc++.so.6: version `CXXABI_1.3.8' not found (required by libTeighaJavaCore.so)

The error appeared due to the gcc 4.8.5 and gcc 5.3 are not ABI compatible. Since gcc 5.3 within glibc library use CXX11 ABI version, and gcc 4.8.5 doesn't (more information about gcc ABI compatibility can be found here and release notes for gcc 5 that tells that "A Dual ABI is provided by the library. A new ABI is enabled by default."

Since we use a defualt ABI version (means we use new version) - you have such errors. You need to upgrade your OS version to have more modern gcc compiler within enabled new ABI version by default.

We are supporting Solid Edge files only with additional Datakit libraries that are available as separate component and it is not included in common membership. With this extension will be available .par .asm formats.

We provide wrappers above the C++ code. They are generated for all of our SDKs. 
Supported platforms include Windows, macOS and Linux.

Start from the file formats you need.

2D/3D CAD drawings - Drawings SDK for .dwg and .dgn. If you need the vertical-application objects inside a .dwg, add the matching product: Architecture, Civil, Mechanical or Map.

BIM - BimRv for Autodesk® Revit® .rvt/.rfa/.rte, IFC SDK for .ifc, BimNv for Autodesk® Navisworks® .nwd/.nwc/.nwf.

Mechanical / MCAD exchange - STEP SDK for STEP (AP203/AP214/AP242) and other EXPRESS-schema formats, plus IGES, JT, Inventor, SolidWorks, Rhino, CATIA, Creo and QIF through the exchange components.

Visualization - Visualize SDK for desktop and mobile rendering of all of the above and inWEB™ when the target is a web or SaaS application.

Output - Publish SDK for 2D and 3D (PRC-based) .pdf; the PDF, SVG, raster, Collada, STL and OBJ exports come with the SDK that owns the source format.

Point clouds and reality capture - the point cloud component for .rcs/.rcp and Scan-to-Bim for deriving BIM geometry from scans.

Both products are wrappers above the C++ code.
Drawings.NET Classic is a set of wrappers designed manually using the managed C++.
Drawings.NET is a set of wrappers, generated by means of a swig tool - and is a set of C# wrappers, that use pInvoke to address C++ code.

Both of these products allow to use ODA SDK functionality with managed languages, like C#, C++/CLI, VB. These products are set of wrappers for C++ native code.

.NET Classic (or Drawings .NET Classic) is an API which is identical to AutoCAD .NET API. If you have .NET plugin for AutoCAD, you'll be able to build it for ODA apps almost without changes. You can consider using .NET Classic if you are familiar with AutoCAD .NET API, or if you have existing .NET plugin for AutoCAD which you want to port to ODA based applications.
The disadvantage is that .NET Classic covers less C++ functionality than Drawings.NET. You can request to implement a .NET class from AutoCAD API if it is not implemented yet, but it requires more time than in Drawings.NET (because in .NET Classic we have to implement each class manually, while in Drawings.NET we use automatic code generation).

Drawings.NET (or .NET Swig, or .NET) provides API identical to ODA C++ interface. It provides same classes with same functions and parameters as ODA C++ SDK. On this project we use automatic code generation, so almost all ODA C++ functionality is available.

At the moment, only imports from PDF to DWG are possible with our software. The imported drawing is obtained as a copy of its presentation in PDF. All drawn elements are transferred to DWG in the form of curve sets, texts, images, etc.. The naturally imported drawing is not an absolute copy of the original drawing (which was imported into PDF) as not all data is transferred to PDF from the original drawing.

Yes, ODA publishes SWIG-generated .NET wrappers for essentially the whole product line, not just a few SDKs. 

Each wrapper needs its C++ counterpart plus the Kernel archive. The C# samples live under Swig/SwigODAExamples/<Product>/CSharp; Java, Python and VB.NET wrappers are generated from the same definitions.

ODA Drawings SDK provides native support for .dwg, .dxf, .dgn files as well as a set of exports and imports. We provide support for old and the most recent versions of .dwg.

BimNv SDK creates .nwd (Model Data), .nwc files (Geometry Cache), .nwf (BIM Data Integration) files.

BimNv SDK allows to combine and review detailed 3D design models from multiple file formats:.dgn, .dwg, .rvt/.rfa.

Directly, .dwg, .dgn and BimRv (.rvt/.rfa) content can be exported to .prc and to 3D .pdf.

Beyond that, anything Visualize can import can be published as 3D .pdf by routing it through a Visualize database and exporting from there - which in practice covers IFC, STEP, IGES, JT, Navisworks, OBJ, STL, Collada and the rest of the Visualize import list. See the Visualize2Pdf example.

Note that 3D .pdf carries geometry, not the source model's property data.

BimRv reads and renders .rvt, .rfa and .rte files of Revit format versions 2011 through 2027. A file is saved in the latest format the release supports; the authoritative value is ODBM_LATEST_FV in BmFileVersion.h, and the full list of recognised versions is ODBM_LIST_VERSIONS in the same header.

Export is available to COLLADA, JSON, PDF, OBJ, STL, SVG and raster formats. Import is available for COLLADA.

These products are Drawings extensions for civil custom objects, architectural design and mechanical objects. Please use this link to find out more about file formats Drawings SDK works with.

* — these formats are not part of a standard ODA membership and require an additional annual licensing fee. Several of the MCAD and exchange importers are also separately licensed components — the pricing page lists what a given membership covers.

Each importer has its own parameters class in TvImport.h (OdTvDwgImportParams, OdTvIfcImportParams and so on) and a matching <Format>2Visualize example. Export to .dwg and .nwd is provided by the Visualize2Dwg and Visualize2Nwd extensions.

Drawings SDK works with different file formats including .dwg, .dgn, .dwf, .dxb, .pdf, .dae (Collada),.svg, raster formats, .stl, .hsf, Three.js, .pc3, .rcs, .rcp. Drawings SDK saves file in the latest file version.

Supported versions of .dwg, .dxf, .dxb (binary .dxf): starting from ACAD9 and ACAD10 (.dxf and .dxb only) to ACAD2018.

Supported versions of .dwf: XPS, B6, A6, C5.5, A5.5, B5.5, C4, A4, B4, 3D.

The supported point cloud formats are Autodesk® ReCap® .rcs and .rcp, which can be imported into a Visualize database and rendered, with automatic level-of-detail.

.ptx is not supported. If you need it, convert to .rcs first (ReCap and several third-party tools do this), or import the points as an unstructured point cloud — Visualize accepts point data directly, and an unstructured cloud can afterwards be converted to the .rcs-based form to get level-of-detail. See the PointCloud2Visualize and Rcs2Visualize examples.