The Complete JT to STL Conversion Guide

Free-Form Surfaces Support:

JT: Full support | STL: 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 | STL: 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.

Quad Meshes Support:

JT: Full support | STL: No support

Impact:

Quad meshes are a common way to hand-model and edit 3D models. 3D artists get intuitive control and such meshes are also easy to refine, as well as well-suited for creation of skinned animations. However, real-time rendering pipelines and hardware are usually all based on triangles, so if a 3D model should not be edited any more, it is safe to convert quads to triangles (and engines will do this automatically before sending data to the rendering hardware). In this example, a part of a mesh is modeled with quads. Without support for this feature, quads will have to be triangulated, producing a pure triangle mesh.

Texturing Support:

JT: Full support | STL: No support

Impact:

Texturing describes the process or refining the visual appearance of a 3D model's surface through additional 2D or 3D data, defined in a different reference system. The by far most common use of texturing are 2D texture images, applied to model visual material properties the 3D surface. Other cases include the use of procedural 2D or 3D funtions that produce intensity or color signals, which are then mapped to the 3D surface. For the vast majority of these cases (all of them except for 3D procedural functions), a parameterization or "Texture Mapping" is needed, which maps the 2D content to the 3D surface. Coming from a 2D coordinate space with coordinate axes often entitled U and V (in contrast to XYZ, which are the 3D surface positions), this process of mapping is also called UV Mapping, and it can be done with a dedicated UV map, or through a live mapping (e.g., box mapping). In this example, a texture image is applied to the 3D model to give the control panel a realistic look. Without support for texturing, the panel would have to use a single material instead, or all controls (including text) would need to be modeled through 3D geometry, instead of a 2D texture image.

Texture Transforms Support:

JT: Full support | STL: No support

JT Notes:

The JT specification defines a full texture transform matrix, supporting translation, rotation, and scaling of texture coordinates.

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 | STL: No support

JT Notes:

JT stores texture images (typically as JPEG data) within binary segments, enabling compressed image storage. No GPU-level texture compression (e.g. BCn/DXT) is defined by the JT specification.

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 | STL: No support

JT Notes:

JT's material model supports multi-texture layers, but multiple independent UV coordinate sets per vertex are not fully defined across all geometry representations.

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.

Procedural Textures Support:

JT: Partial support | STL: No support

JT Notes:

JT includes a generic shader/material node system that enables procedural-style texture effects. Full arbitrary procedural texture programs (e.g. GLSL) are not defined.

Impact:

Procedural texture allow the modeling of surface details through mathematical functions, along with artistic control over various parameters. Typically, they are used for patterns like wood grain or other semi-regular structures. Since they are not using any pixels as source data, procedural textures have, in principle, infinite resolution and are very lightweight to describe. In this example, a procedural texture is used to model the look of a wooden material. Without support for this feature, in this case, the wooden parts won't show any visible details.

Embedded Textures Support:

JT: Full support | STL: No support

JT Notes:

JT fully supports embedding texture image data directly within the file as binary segments, making JT files self-contained.

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.

Normal Mapping Support:

JT: Full support | STL: No support

JT Notes:

Normal maps are fully supported in the JT material specification with no stated limitations.

Impact:

Normal maps are used to model shading differences that are arising from small geometric details on a surface, such as fabric structures, visible gaps between bricks forming a wall, or rough rock surfaces. In this example, a normal map is used to model a fabric structure. Without support for this feature, the rendered fabric will look smoother than it actually is in the real world, as the fabric structure won't be visible.

Materials Support:

JT: Full support | STL: No support

Impact:

Materials are a fundamental concept in 3D modeling, enabling colored and - in many cases - photorealistic rendering of the 3D model that they are applied to. There are also some formats that don't make use of 3D materials, for example because they need to solely describe a shape (e.g., for many cases in additive manufacturing). In this example, photorealistic PBR materials are used to equip the 3D model with a realistic look. Without support for materials, the model will have to be rendered with a default material (often a default shade of gray).

Transparent Materials Support:

JT: Full support | STL: No support

Impact:

Transparency is commonly used for see-through objects, containing (usually partially) transparent surfaces. In this example, a transparent material is used to model the glass window of the microwave, so that one can see inside. Without support for this feature, the inside of the microwave cannot be seen, as the window will be rendered as an opaque surface.

Vertex Colors Support:

JT: Full support | STL: 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 | STL: 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 | STL: 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.

Scene Nodes Support:

JT: Full support | STL: No support

Impact:

Scene nodes make it possible to address parts of a 3D model separately. For example, a part could be dynamically hidden or shown as part of a 3D configurator. Without support for this feature, a 3D scene will only consist of a flat model, without parts being individually configurable.

Hierarchical Scene Graph Support:

JT: Full support | STL: 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 | STL: 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.