Convert X_T to OBJ

A mesh application, game engine, 3D printer workflow, or viewer may require OBJ when the source system provides only Parasolid X_T. Converting also makes the model easier to share, but changes precise CAD geometry into a polygon mesh.

What the X_T format is

.x_t is the text-based Parasolid transmission format used to exchange solid and surface models between mechanical CAD systems. Parasolid-based products such as Siemens NX, Solid Edge, SolidWorks, and many CAM systems can create or import it; .x_b is the corresponding binary format. An X_T file can contain exact analytic faces, topology, assemblies, and attributes that polygon formats do not preserve.

What the OBJ format is

.obj is a text-based polygon-mesh format supported by Blender, Maya, 3ds Max, game engines, slicers, and many 3D viewers. It stores vertices, texture coordinates, normals, and polygon faces. An accompanying .mtl file can reference materials, while image textures normally remain separate. OBJ is suitable for rendering, mesh editing, and some fabrication workflows, but it does not retain Parasolid solids, parametric history, feature trees, constraints, or exact CAD tolerances.

Using CAD Exchanger Desktop

1. Install CAD Exchanger Desktop for Windows, macOS, or Linux, then open the file with File → Open.
2. Inspect the imported bodies and hide construction geometry or unwanted assembly components before export.
3. Open the tessellation or mesh settings. Reduce chordal deviation and use a finer angular tolerance for curved or detailed surfaces; use coarser values when file size matters.
4. Choose File → Export, select OBJ, and enable normals, texture coordinates, and material export when available.
5. Save the OBJ, retain the generated .mtl file and texture images, and open the result in Blender or another viewer to check scale, normals, gaps, and missing faces.

CAD Exchanger is a practical choice because it reads Parasolid X_T directly and exposes tessellation controls. TransMagic and Okino PolyTrans are commercial alternatives with broader CAD translation features. If the originating CAD application is available, import the X_T there and use its OBJ or mesh export; the menu and available settings depend on the product and license.

Using an online converter

CAD Exchanger Cloud can provide browser-based CAD conversion without installing desktop software. Confirm that its current format list accepts .x_t as input and .obj as output before uploading, because many conversion sites support STEP or IGES but not Parasolid. Do not upload confidential or export-controlled geometry unless the service terms and your organization’s policy permit cloud processing. Download the OBJ together with any .mtl and texture files, then verify the result locally.

Quality and compatibility limits

OBJ export tessellates each CAD face, turning curved surfaces into triangles or polygons. Coarse tessellation creates visible faceting and lowers geometric fidelity; very fine tessellation increases file size and can slow mesh software. Choose the smallest chordal deviation that meets the downstream rendering, editing, or fabrication requirement rather than relying on a generic high-quality preset.

Check units during both export and import. OBJ has no reliable standard unit declaration, so a model authored in millimetres can appear 25.4 times too large or too small when the receiving program assumes inches or metres. Compare the imported bounding-box dimensions with the original CAD model.

Assemblies may export as separate OBJ objects or as one combined mesh. Preserve separate parts when materials, selection, animation, or later editing depends on component boundaries. CAD colors and materials may translate imperfectly, and OBJ does not carry assembly constraints, metadata, feature history, or exact surface definitions. Unsupported or defective Parasolid entities can be omitted during import.

Parasolid files are version-sensitive: an older CAD or translation application may not read an X_T produced by a newer Parasolid release. If import fails, export the model again from the source system using an older compatible Parasolid version or an intermediate format such as STEP, then tessellate that imported model.