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. As I can see 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. Wrappers are generated for a large set of SDKs: Drawings SDK, Visualize SDK, Publish SDK. But for now our wrappers are Windows-only.

Unfortunately, currently we haven’t .NET Standard wrappers for ODA SDK. Wrappers for Kernel, Drawings, Dgn will be available approximately in the middle of this year.

If you mostly use .dwg and .dgn, use Drawings SDK. For working with Architecture , Civil and Mechanical .dwg file formats, please use corresponding ODA product.

For visualization you can use Visualize and Open Cloud (this product specially designed for creating web/Saas application). These products work not only with different CAD file formats, but with BIM as well.

For developing BIM solutions you can use a wide range of file formats:

• Autodesk® Revit® files (rfa/rvt) – BimRv
• IFC files – IFC SDK
• Autodesk® Navisworks® files (nwd, nwc, nwf) – BimNv

You can get 2D and 3D .pdf with Publish SDK.

Yes, we have wrappers for Python2 for the vc15 platform. Wrappers generated using SWIG, that uses CPython technology.

We have several examples of using the ODA SDK in Python: Drawing \ Swig \ Python \ Examples \ OdDemoViewerExSwigPythonTK and Drawing \ Swig \ Python \ Examples \ OdReadExSwigPython.

You will need the following archives: Kernel SDK, Drawings SDK, Python SDK (Kernel.PY & Drawings.PY). You can download the archives on this page.

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.

You can use ODA archives with SWIG wrappers, which are implemented for some products: Drawings.NET, Publish.NET, Visualize.NET, Architecture.NET and Civil.NET.

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.

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

BimRv reads and renders .rvt, .rfa, and .rte files of format versions 2011-2020. File will be saved in the latest version (depending on which release do you use).

Exporting to a Collada, .pdf, .svg, .obj, raster file.

Importing Collada files.

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.

* — BIM and NwInterop are not part of a standard ODA membership and require an additional annual licensing fee.

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.

Yes, we already support .rcp and .rcs files, we can import this data in our visualize database and visualize it.