The Complete Rhino 3DM to VRML Conversion Guide

Free-Form Surfaces Support:

Rhino 3DM: Full support | VRML: Partial support

VRML Notes:

Limited NURBS support in VRML 2.0

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.

Quad Meshes Support:

Rhino 3DM: Full support | VRML: Partial support

VRML Notes:

Primarily triangle-based with some quad 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.

Multiple UV Channels Support:

Rhino 3DM: Full support | VRML: Partial support

VRML Notes:

Basic 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:

Rhino 3DM: Partial support | VRML: No support

Rhino 3DM Notes:

Textures can be embedded in the 3DM file

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:

Rhino 3DM: Full support | VRML: No support

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.

PBR Materials Support:

Rhino 3DM: Full support | VRML: No support

Impact:

PBR materials enable Physically-Based-Rendering (PBR) for a standardized, photorealistic look of rendered images. PBR uses concepts like metallic-roughness or specular-glossiness properties and a microfacet-based modeling of the surface, using a concept called BRDF (Bi-Directional Reflectance Distribution Function). In this example, PBR materials are used to achieve realistic looking plastic and metal materials. Without support for PBR materials, only basic colors and shading can be used (for example, based on more simple shading models, such as the Blinn/Phong model).