The Complete JT to OBJ Conversion Guide

Free-Form Surfaces Support:

JT: Full support | OBJ: No support

Impact:

Free-form surfaces allow a CAD user to design surfaces with advanced controls over curvature and continuitiy. While these surfaces are common for CAD models (in the form of so-called boundary representations or "B-reps"), they need to be converted to polygonal triangle or quad data to work with most 3D rendering engines - a process called tessellation. In this example, a surface patch is used to describe a part of a curved surface of a product. Without support for this feature, the free-form surface has to be tessellated into quads or triangles.

Geometry Compression Support:

JT: Full support | OBJ: No support

Impact:

Geometry compression describes the process of compressing the representations of a 3D model's geometry, usually a triangle mesh. 3D geometry compression does not change the topology of a 3D model, but just changes the way that a 3D model and its 3D positions and related vertex data is stored. Geometry compression can be lossy (just like JPEG compression in image processing can be lossy, for example), in which case one might notice slight artifacts like variations in 3D vertex positions (compared to the uncompressed 3D model). However, such differences are often not noticeable. There are only very few standards for geometry compression, like glTF's support of Draco compression and similar extensions.

Texture Transforms Support:

JT: Partial support | OBJ: No support

JT Notes:

Basic texture transformation support

Impact:

Texture transforms describe transformation operations that are applied to 2D texture images or UV coordinates when using 2D texture data on a 3D surface. They can be used, for example, to make sure that material patterns are using real-world scale when rendered on the 3D surface. In this example, such a pattern is used and scaled with the help of a texture transform. Without support for this feature, the texture pattern shows up at the wrong scale.

Texture Compression Support:

JT: Partial support | OBJ: No support

JT Notes:

Efficient compression for visualization

Impact:

Texture compression refers to a process of compressing 2D texture images for memory-efficient rendering (and sometimes for efficient transmission). The decompression of compressed texture data is therefore performed on-the-fly during rendering, so that it never has to be stored in unpacked form, but can be kept as-is in GPU memory. Formats supporting texture compression methods, such as the ones offered by glTF through KTX2 containers, therefore allow 3D models to use a smaller memory footprint on the client device during rendering. This can speed up rendering time, and also make it possible to store and use larger amounts of texture data than it would otherwise be possible.

Multiple UV Channels Support:

JT: Partial support | OBJ: No support

JT Notes:

Limited multi-texturing capabilities

Impact:

Multiple UV channels allow the optimized and sophisticated use of various 3D modeling features at once. For example, one can use one set of UVs and 2D texture data to model a tiling texture or procedural material, and another UV set to leverage a global lightmap or occlusion map of the 3D model. In this example, a combination of tiled texture (UV channel 1) and baked ambient occlusion map (UV channel 2) is used. Without support for this feature, one needs to either give up the tiling property (e.g., by using a tool like RapidPipline to bake a single texture atlas), or give up the ambient occlusion map, as only one UV channel will be usable.

Embedded Textures Support:

JT: Partial support | OBJ: No support

JT Notes:

Textures can be embedded for self-contained files

Impact:

Embedded textures allow the storage and exchange of an entire 3D model and its materials within a single file, by embedding the texture images directly into the 3D file (and not storing them as separate image files). Without support for this feature, textures have to be stored in separate image files, and referenced from the main 3D model file.

Vertex Colors Support:

JT: Full support | OBJ: No support

Impact:

Vertex colors allow the attachment of colors to each vertex of a 3D model. This can be useful in scenarios such as scientific visualization, or when converting/meshing data from a colored 3D point cloud, for example. On the polygonal surface connecting the vertices, the respective vertex colors are usually smoothly interpolated. In this example, different colors are attached to the different corners of a cube. Without support for this feature, the cube won't have any colors.

Animations Support:

JT: Partial support | OBJ: No support

JT Notes:

Simple animation support for assembly operations

Impact:

Animations are an important part of many interactive 3D assets, for example in real-time rendering (including games, XR training, assembly instructions, product demos, and other use cases). There are various kinds of animations that can be used on 3D models. In this example model, a rigid animation is used to make the gears spin. Without support for this feature, in this example, the gears won't move.

Rigid Animations Support:

JT: Partial support | OBJ: No support

JT Notes:

Basic rigid body animation for design review

Impact:

Rigid Animations are typically used to animate mechanical parts. In this example, the door of this 3D model of a microwave can be interactively opened or closed, using a rigid animation that gradually changes the 3D transformation of the door. Without support for this feature, in this example, the door will just stay in place and won't move.

Hierarchical Scene Graph Support:

JT: Full support | OBJ: No support

Impact:

Scene graphs are one of the most common concepts in 3D computer graphics. By structuring the scene in a hierarchical way, logical parts of it can be easily addressed and transformed. This is useful in many applications, like games or 3D configurators. Without support for this feature, a 3D scene cannot be structured hierarchically, for example objects cannot be logically composed of smaller objects.

Scene Composition Support:

JT: Full support | OBJ: No support

Impact:

Scene Composition describes the process of composing a scene through links from a main scene that pull in various other scenes/3D models. This can also happen in a nested fashion (through multiple levels of linkage). With a target format not supporting this feature, references to external models must be resolved and the content be baked into one 3D model, which is then saved in that target format.

Standardized Format Support:

JT: Full support | OBJ: Partial support

OBJ Notes:

Compatibility of all properties strongly depend on particular compatibility of the tools that export / import the DCC file, as there is no clear standard for this format.

Impact:

Standardization plays a huge role in 3D model formats. With a format being standardized, every application will have a clear way of how to load or store data using this format. This makes it easier to re-use the 3D model across different applications, but also to make sure it will still be accessible and usable after a couple of years.