Mesh

In Source, each Mesh (sometimes referred to as the envelope or skin of the model) defines a part of the model's Rendering Geometry (or Render model). The Rendered Skin is projected over the Mesh which envelopes the Skeleton.

Each renderable model requires at least one mesh (the body mesh) but may also have additional sub-meshes. Each mesh may also have a number of versions optimised for LOD-substitution.

All Mesh data is exported from a model editor as an SMD file, and then compiled to the model's VVD and VTX binary files. Mesh data includes (for each triangular polygon) :

• 3D Geometry data : Vertex Coordinates (relative to a specific Parentbone),
• Smoothing group data : Vertex Normal vector (relative to a specific Parentbone),
• Skinning data : Vertex UV map coordinates and Default Skinname(s),
• Envelope data : Vertex Weight map values and Parentbone.

Tip:See SMD file format for exactly how this data is stored in the triangles block of a "Studio Model Data" file.

Body mesh

The "default" body mesh is rendered unless substituted by a specific LOD mesh. Sometimes it is called the Reference mesh because it is defined in the model's Reference.smd and compiled via the $body or $model QC command.

Sub-mesh

Optional Sub-meshes can be switched on and off at runtime. Like the body mesh, they are enveloped to this model's Skeleton, and will deform (stretch and flex) as if part of the Default mesh. Specific pieces of clothing are good candidates for switchable sub-meshes; eg different types of body armor or headgear. By contrast Sub-models (eg weapons) can be attached to specific $attachment points on this skeleton, but they remain enveloped to their own skeleton; their geometry will be moved by this skeleton but will not be deformed by it.

• The $bodygroup configuration allows any number of sub-meshes (SMDs) to be added to the Default mesh. By setting up multiple $bodygroups sub-mesh switching can be triggered by (code-level) events.
• Whereas "Alternative Skins" replace the Default Skin, Optional Meshes do not replace the Default Mesh.
• Sub-meshes do not affect the model's collision model.
• (
  Todo: $model's face mesh for facial animation ?
  )
• Sub-meshes must be exported in separate .smd files to the body mesh, but they must be enveloped to the same skeleton so they align correctly with the model (see $bonemerge).

LOD mesh

Source's LOD system allows a "cheaper" (simplified) version of the Default mesh(es) to be rendered at a distance where the loss of "expensive" detail is not noticeable to the Viewer. Any number of replacement LOD_meshes can be made from pared-down Default meshes, and compiling the lod.SMDs via the $lod configuration. A Default mesh is used when no LOD mesh is active; we could say it amounts to an "lod0" Mesh. See Creating LOD Models.

Disambiguation

• A Model is a functional set of components, including whatever Skin, Mesh, Skeleton, Collision geometry, associated Animations, Sounds, Physics properties, etc. data it needs to fulfil a given role. Often a particular SMD or MDL file is referred to as a model, for example a "reference model" usually refers to the reference.smd, and a "collision model" (PHY) is a fully rigged version of the visual model (VVD) which is simply "rendered" in the Physics Engine as opposed to the Rendering Engine.
• A Collision Mesh in Source is a misnomer, because all pieces of 3D collision geometry are rigid Collision Hulls rather than deformable Meshes. A Ragdoll's Collision Model consists of a system of small Rigid Hulls which are moved (but not deformed) by skeletal articulation. The "Rendering Mesh" or "Skin Mesh" is the only type of Mesh used currently for Source Models.