Read JT for glTF / GLB conversion
A JT-to-glTF / GLB workflow combines the JT reader with the glTF / GLB writer. Use it when the receiving application needs glTF / GLB data from an existing JT model.
JT can contain stored visualization meshes, embedded Parasolid BRep, or both. Select the representation needed for the destination before reading the assembly. The Parasolid interface imports precise geometry only when the JT file contains Parasolid BRep data.
Prepare a scene for glTF or GLB delivery
For a mesh route, select a suitable stored level of detail or tessellate the imported Parasolid BRep with the required deflection. For a precise-geometry route, use the embedded BRep; a mesh-only JT file cannot supply the original CAD surfaces.
Map supported model items into glTF scene nodes and configure the mesh, placements and appearance for browser or application delivery. Decide whether the receiving workflow expects a GLB package or glTF with companion resources. Keep names useful for selection and inspection.
Validate the glTF / GLB result
Check part placements and repeated instances as well as names, colors and transparency. A stored coarse level of detail cannot regain surface detail merely by changing file format.
Reopen the asset in the target viewer and compare orientation, bounds, assembly placement and visible surface quality. Check material mapping and resource paths. Measure loading cost together with geometric detail so that reducing mesh size does not silently remove required features.
For a production pipeline, keep a representative source file and its expected geometry and attributes with the conversion settings. Discuss conversion integration with the source and destination applications, or compare the supported format interfaces.