← CAD and mesh conversion guides

OCCT conversion workflows

ASE to JT

Convert ASE to JT. Prepare source geometry, select the target writer and verify placements and supported attributes.

Build this conversion into your application with OCCT readers, writers and the commercial components identified below.

Ask about this workflow
Input interface
OCCT3D Assimp reader
Processing route
Mesh to mesh
Output interface
OCCT3D JT writer

Read ASE for JT output

A ASE-to-JT workflow connects the ASE reader to the JT writer. Select the model items and output representation needed by the receiving application.

Read the ASE asset with the Assimp integration and inspect the supported mesh, material and scene-structure data. Select the objects intended for the output workflow.

Build a JT visualization model

The Assimp integration provides mesh geometry, colors, materials and scene structure for its supported inputs. Pass that data to a separate OCCT or commercial writer. For STEP, STEP XML or DXF output, use the mesh-capable representation; this does not reconstruct BRep surfaces from polygons.

Use the OCAF-to-JT converter for supported hierarchy, names, colors and mesh representations. Configure tessellation and any required levels of detail around the viewing task. This output route creates a visualization representation; it does not promise Parasolid BRep export inside JT.

Check the JT result

Validate object transforms and available material references. Keep the authoring source for scene details not represented by the imported mesh and material mapping.

Select a JT version accepted by the recipient and check part positions, geometry coverage and appearance there. Compare both the full assembly and selected parts. If later processing requires precise CAD surfaces, retain the source BRep alongside the visualization derivative.

Discuss this conversion with the producing and receiving applications, representative files and required geometry and attributes. Compare the reader/writer catalog when a different representation is needed.

Conversion integration

Build a ASE to JT workflow

Share the source and receiving applications, representative files, required attributes and throughput. We can scope SDK evaluation or an integrated conversion service.