The Complete VRML to Solid Edge Conversion Guide

Geometry Compression Support:

VRML: Partial support | Solid Edge: No support

VRML Notes:

VRML files can be compressed at the file level using gzip (.wrz extension). Geometry-level compression is not part of the VRML97 core standard, but prototype-based extensions exist — notably Taubin's GC node, a geometry compression scheme proposed specifically for VRML.

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.

Texturing Support:

VRML: Full support | Solid Edge: Partial support

Solid Edge Notes:

Limited texture support primarily through material properties and appearance definitions for visualization purposes, not extensively used in typical mechanical engineering workflows.

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:

VRML: Full support | Solid Edge: Partial support

Solid Edge Notes:

Basic texture mapping capabilities through material and appearance properties, but not as advanced as dedicated 3D graphics applications.

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.

Procedural Textures Support:

VRML: Partial support | Solid Edge: No support

VRML Notes:

Simple procedural texture generation

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.

Vertex Colors Support:

VRML: Full support | Solid Edge: Partial support

Solid Edge Notes:

Limited vertex color support, mainly through part coloring and display properties rather than per-vertex color data manipulation.

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.

Morph Targets Support:

VRML: Partial support | Solid Edge: No support

VRML Notes:

Basic shape interpolation through coordinate interpolation

Impact:

Morph Targets, or "Blend Shapes", are commonly used to animate facial expressions and soft surfaces, for example cloth under a cloth simulation. They model various states of the animations with different vertex positions. In contrast to skinned animations, morph targets do not use any virtual bones, but work solely on the vertex data. In this example, a facial animation is achieved through morph targets. Without suport for this feature, in this example, the face will not show the animation.

Standardized Format Support:

VRML: Full support | Solid Edge: Partial support

Solid Edge Notes:

Solid Edge uses proprietary file formats but provides extensive import/export support for industry-standard formats like STEP, IGES, and others for interoperability.

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.