UV map: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
mNo edit summary |
||
| Line 10: | Line 10: | ||
*** UV divisors (eg <code>"scale" <[[float]] U> <[[float]] V></code> ?) | *** UV divisors (eg <code>"scale" <[[float]] U> <[[float]] V></code> ?) | ||
* 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]]. | * 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]]. | ||
* A model's [[UV map]] or '''Texturemap''' is an index specifying which area of the relevant [[VTF]]s to apply to each specific polygon of the mesh. The UV map itself does not contain any pixel values (colour, etc), it only indexes the mesh's XYZ vertices to corresponding texture UV coordinates. Each UV map is therefore specific to a mesh rather than a texture file, and so it is stored as ''part of the mesh'' file. A mesh may only have one UV map, but it can use multiple or alternate skins, so long as the layout (coordinates) of each VTF skin corresponds to the Mesh's UV Map. | * A model's [[UV map]] or '''Texturemap''' is an index specifying which area of the relevant [[VTF]]s to apply to each specific polygon of the mesh. The UV map itself does not contain any pixel values (colour, etc), it only indexes the mesh's XYZ vertices to corresponding texture UV coordinates. Each UV map is therefore specific to a mesh rather than a texture file, and so it is stored as ''part of the mesh'' file. A mesh may only have one UV map, but it can use multiple or alternate skins, so long as the layout (coordinates) of each VTF skin corresponds to the Mesh's UV Map. | ||
==See Also== | ==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?) | |||
Revision as of 07:26, 11 April 2008
- UV Mapping, or Texture Mapping, is the process of aligning and adjusting how a Texture (VTF) is applied to a specific Polygonal Mesh. (I'm using the term "mesh" for both brush and model geometry.)
- To UV map Models use XSI Texture Editor (or equivalent).
- To UV map Brushes use Hammer Face Edit Dialog.
- Valve Material Type files can also specify UV mapping adjustments for each VTF used by a particular material, via the $basetexturetransform, $bumptransform, etc VMT parameters.
- 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.
- A model's UV map or Texturemap is an index specifying which area of the relevant VTFs to apply to each specific polygon of the mesh. The UV map itself does not contain any pixel values (colour, etc), it only indexes the mesh's XYZ vertices to corresponding texture UV coordinates. Each UV map is therefore specific to a mesh rather than a texture file, and so it is stored as part of the mesh file. A mesh may only have one UV map, but it can use multiple or alternate skins, so long as the layout (coordinates) of each VTF skin corresponds to the Mesh's UV Map.
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?)