UV map: Difference between revisions
Jump to navigation
Jump to search
Note:Models tend to have a more complex mesh than brushes, which makes UV mapping much more fiddly. Model VTFs therefore tend to be created specially to map easily and efficiently onto one specific model only. Models may use multiple (alternative) skins, so long as the layout of each VTF corresponds to the model's UV map.
m (Robot: fixing template case.) |
(Gramatical Cleanup & Rewording) |
||
| Line 3: | Line 3: | ||
A [[UV map]] is a part of an object's geometry. It defines which areas (using UV coordinates) of a 2D pixelmap should be rendered on which polygonal surfaces (using XYZ coordinates) of a particular 3D mesh. A UV map does not contain any pixel data (eg color, etc). It is only a matrix relating 2D to 3D coordinates. | A [[UV map]] is a part of an object's geometry. It defines which areas (using UV coordinates) of a 2D pixelmap should be rendered on which polygonal surfaces (using XYZ coordinates) of a particular 3D mesh. A UV map does not contain any pixel data (eg color, etc). It is only a matrix relating 2D to 3D coordinates. | ||
In Source, the object's UV map | In Source, the object's UV map is stored in a [[VMT]] file and reads the pixel data from the same UV area of each VTF in the texture stack. Therefore one UV map imports data from the colormap, bumpmap, opacitymap, specularmap, etc as though they were one image (with enormous bitdepth). Thus the object's Material can easily be changed without having to rebuild the UV map. | ||
{{note|Models tend to have a more complex mesh than brushes, which makes UV mapping much more fiddly. Model VTFs therefore tend to be created specially to map easily and efficiently onto one specific model only. Models may use multiple (alternative) skins, so long as the layout of each VTF corresponds to the model's [[UV map]].}} | {{note|Models tend to have a more complex mesh than brushes, which makes UV mapping much more fiddly. Model VTFs therefore tend to be created specially to map easily and efficiently onto one specific model only. Models may use multiple (alternative) skins, so long as the layout of each VTF corresponds to the model's [[UV map]].}} | ||
Revision as of 14:21, 5 November 2010
A UV map is a part of an object's geometry. It defines which areas (using UV coordinates) of a 2D pixelmap should be rendered on which polygonal surfaces (using XYZ coordinates) of a particular 3D mesh. A UV map does not contain any pixel data (eg color, etc). It is only a matrix relating 2D to 3D coordinates.
In Source, the object's UV map is stored in a VMT file and reads the pixel data from the same UV area of each VTF in the texture stack. Therefore one UV map imports data from the colormap, bumpmap, opacitymap, specularmap, etc as though they were one image (with enormous bitdepth). Thus the object's Material can easily be changed without having to rebuild the UV map.
Note:Models tend to have a more complex mesh than brushes, which makes UV mapping much more fiddly. Model VTFs therefore tend to be created specially to map easily and efficiently onto one specific model only. Models may use multiple (alternative) skins, so long as the layout of each VTF corresponds to the model's UV map.
UV Mapping, or Texture Mapping, is the process of aligning Polygons to Pixels.
- To UV map Models use XSI Texture Editor (or equivalent).
- To UV map Brushes use Hammer Face Edit Dialog (and the Paint Alpha Dialog for blending Materials on Displacements).
- To UV map Decals use Hammer Decal Tool.
- To UV map Overlays use Hammer Overlay Tool.
- Valve Material Type files can also specify UV mapping adjustments for each VTF seperately, via the $basetexturetransform, $bumptransform, etc VMT parameters. (Todo: confirm: this only works for VMTs applied to Brushes, not to Models?)
See Also
- wikipedia:UV mapping and wikipedia:Texture mapping for the theory.
- The layout of a complex Model Skin is comparable to a wikipedia:Texture atlas.
- wikipedia:UVW mapping (used in 3DS Max only?)