JT Writer
| JT | |
| File Extension | JT |
| Supported Versions | 8.1, 9.5, 10.0 |
| Platforms | |
| Tessellation | Supported |
| B-rep | Supported |
| PMI | Supported |
The JT file format, also known as Jupiter Tessellation, was originally developed by Engineering Animation, Inc. and Hewlett-Packard as part of the Direct Model toolkit. It was later acquired by UGS Corp. and became part of Siemens Digital Industries Software in 2007. The format was officially published as an ISO standard in 2012, making it a widely used and recognized format for 3D data exchange and visualization.
The HOOPS Exchange JT writer allows developers to export the Assembly, B-rep, View data from Exchange to JT. The file extensions that you can create when you export the data are:
- .JT
Tessellation
The tessellation is exported in a lossless, compressed format.
B-rep
When we export the B-rep it will always be in Parasolid B-rep. If the format was not a Parasolid-based format then all surfaces get mapped to one of the following:
- B-spline surface
- Cone
- Cylinder
- Plane
- Sphere
- Revolution surface
- Swept surface
- Torus
…and curves to one of the following:
- 3D curve
- Circle
- Ellipse
- Line
- UV curve
If the source data was originally XT then HOOPS Exchange will take that data and use it for the B-rep definition.
PMI
All supported PMI is exported to one of the following types.
- Datum feature symbol
- Dimension
- GD&T
- Generic PMI
- MeasurementLocator
- MeasurementPoint
- Note
- Surface finish (roughness)
- Weld
How to Export to JT
To export a model to JT, use A3DAsmModelFileExportToJTFile().
Customize the export using A3DRWParamsExportJTData.
A3DRWParamsExportJtData sParamsExportData = A3D_MAKE_DATA(A3DRWParamsExportJtData);
// ... set export parameter options
A3DAsmModelFileExportToJtFile(pModelFile, &sParamsExportData, "path/to/file.JT");
Assembly
To understand and manipulate the model tree before export, see assembly traversal or the Tree Traversal API.
Export to Buffer
Our JT writer provides additional paramters to export data, which can be found in the refernce manual
Before exporting, ensure that the model contains the geometry and tessellation you expect. See our pages on tessellation for tips on generating visualization data for export.
Assembly
The assembly structure including coloring and transformations will be exported to the JT file. Instances are currently replaced by object copy. The export is currently to a single monolithic file.
Views
HOOPS Exchange JT Writer does not currently support views in the export of this format.
Export Options Specific to JT
Export options specific to JT can be found on the A3DRWParamsExportJTData reference page.
The option m_bWriteWireframe from A3DRWParamsExportJTData allows to export wireframe tessellation (this option is set to false by default).
JT Specification Conformance
A JT file stores its data in segments, and records the size of each segment in a table of contents within the file. Readers rely on these sizes to read each segment directly. JT readers that check these sizes strictly make file reading safer and more reliable, and refuse files where the recorded sizes are not exact.
Conformance by HOOPS Exchange Version
| Exported JT file | Before HOOPS Exchange 2026.8.0 | Starting with HOOPS Exchange 2026.8.0 |
|---|---|---|
| Recorded segment sizes | Slightly smaller than actual | Exact |
| Readers that do not check sizes | Load the file | Load the file |
| Readers that check sizes strictly | Refuse the file | Load the file |
| HOOPS Exchange 2026.8.0 and later | Load the file, with a warning | Load the file |
Readers that check segment sizes strictly include Siemens products starting with the 2612 releases, and applications built on JT Open Toolkit 12.2 and later. In readers that do not check these sizes, such as earlier Siemens products, files exported before HOOPS Exchange 2026.8.0 load normally, and no data is misread. For the warning logged by HOOPS Exchange, see Detection at Import.
Detection at Import
When it loads a JT file, the JT reader checks the recorded segment sizes, and logs these warnings when they do not match the file content:
Unexpected segment offset or length in the TOC of this JT file.At least one unexpected segment length detected in this JT file.
When such file was exported by HOOPS Exchange, the first warning is followed by:
This file contains one or more segments with wrong offset or length in TOC.
In order to make this file fully compatible with JT standards, it should be converted to latest version using one of the utilities provided.
Refer to documentation for more details.
These warnings are informational: loading continues and the imported model is complete.
Updating Existing Files
The recommended way to update existing JT files is a dedicated conversion utility, planned for a future release of HOOPS Exchange. It is designed to correct only the recorded segment sizes, and to leave the rest of the file unchanged.
Until this utility is available, you can export the files again to JT with HOOPS Exchange 2026.8.0 or later. The ImportExport sample does this without writing any code:
ImportExport input.jt output.jt
The sample uses the default values of A3DRWParamsExportJTData.
To keep the settings of the original file, such as its JT version, adjust these values in the sample before you build it.
Exporting again does not only correct the segment sizes. The file goes through the HOOPS Exchange model and is written again by the JT writer of the version you use. The new file contains what this JT writer supports (see Limitations), and its content can differ from the original file, because the JT writer improves from one release to the next. Keep the original files, and check the import log for errors before you replace them.
Limitations
The current limitations include:
- No support for parametric wireframe representations (Wireframe tessellation from specific entities are supported though)
- PMI text is exported in tessellated form
- No support of texture, light, or shader data
- Instances are currently exported as a part copy