Convert Smart 3D to OBJ in your application
3D InterOp is a CAD interoperability SDK that lets your software read Smart 3D files and write OBJ, carrying the mesh data across without re-tessellating it.
Spatial does not offer an online converter or a desktop conversion app. 3D InterOp is a component that software vendors embed in their own products.
- Reads Smart 3D · Writes OBJ
- Triangle mesh → triangle mesh
- C++ / C# APIs
Smart 3D to OBJ at a glance
Both formats store triangles, so the facets carry over without re-tessellation. The differences are in structure, appearance and metadata.
| Smart 3D (source) | OBJ (target) | |
|---|---|---|
| Full name | Hexagon (Intergraph) Smart 3D review files | Wavefront OBJ |
| Standard / owner | Hexagon | Open format |
| File extensions | .xml with its .vue | .obj |
| Geometry | Tessellated geometry | Polygon mesh |
| Assemblies / structure | Yes: plant hierarchy (.xml) | No assembly hierarchy |
| 3D InterOp support | Read only | Read and write |
What's preserved, what changes
Here is what your application can expect to carry across from Smart 3D to OBJ.
-
Preserved
Mesh dataThe Smart 3D facets are read and written to OBJ without being re-tessellated.
-
Changes
Assembly structureOBJ has no native assembly hierarchy. Decide in your application how Smart 3D product structure is grouped or flattened before writing.
Why software vendors add Smart 3D to OBJ conversion
Lightweight review
OBJ carries tessellated geometry that opens much faster than the full CAD model, so design reviews and digital mockups stay responsive.
Sharing outside engineering
Marketing, training and sales teams rarely have CAD software. A OBJ file gives them the shape in a format their tools can open.
Easier handling of large assemblies
Without exact surfaces and feature data, OBJ files are easier to transfer and display, even for large assemblies.
Things to check before you ship
- The OBJ writer is available through the UConnect interface only.
- Supported Smart 3D input: the .xml file with its .vue file.
- Provide the .xml with its .vue file: a standalone .vue gives visualization data only.
- Test tessellation settings on your heaviest parts: finer meshes mean larger files.
- Validate a sample of translated files in the target system your users actually work with.
Working with Spatial was a real milestone for us: Thanks to the powerful 3DInterOp library, we were able to successfully bring our complex CAD-based solutions to the cloud while remaining flexible to meet individual customer requirements. For us, Spatial is not just a technology partner, but a true enabler of our product strategy.
Dr. Arno Michelis, Founder, Simus Systems
Read the Case StudyAbout the formats
-
Source format
What is a Smart 3D file?
Hexagon Smart 3D is a plant and marine design system. Its models are shared as review files: a .vue file with the geometry and an .xml file with the plant hierarchy and properties.
-
Target format
What is an OBJ (.obj) file?
OBJ is a simple, widely supported text format for polygon meshes, created by Wavefront. It describes vertices, faces and texture coordinates, with materials in a separate .mtl file.
Frequently asked questions
No re-tessellation is needed. 3D InterOp reads the Smart 3D facets as visualization data and writes them to OBJ.
OBJ has no assembly hierarchy, so your application decides how the Smart 3D structure is grouped or flattened before writing.
The OBJ writer is available through the 3D InterOp UConnect interface.
Provide the .xml file with its .vue file. A standalone .vue file gives visualization data only.
3D InterOp reads the .xml file with its .vue file, as visualization data.
No. 3D InterOp reads Smart 3D but doesn’t write it. To send data back to Smart 3D users, write a neutral format they can import.
-
Building software that needs to convert Smart 3D to OBJ?
3D InterOp is an SDK that lets your application read Smart 3D and write OBJ alongside 30+ CAD and BIM formats.