|
|
| Line 16: |
Line 16: |
| # Create a [[VMT|Valve Material (.vmt)]] file, where you refer to the Valve Texture File (.vtf) you've created. (See [[#Creating a Valve Material (.vmt) file|below]].) | | # Create a [[VMT|Valve Material (.vmt)]] file, where you refer to the Valve Texture File (.vtf) you've created. (See [[#Creating a Valve Material (.vmt) file|below]].) |
| # Launch the Hammer editor (or model viewer) and check that the new material works properly. | | # Launch the Hammer editor (or model viewer) and check that the new material works properly. |
|
| |
|
| |
|
| |
|
| |
|
| |
| == Creating a Valve Material (.vmt) file ==
| |
|
| |
| Once the Valve Texture File (.vtf) has been created, a [[VMT|Valve Material (.vmt)]] file must be created to actually use the texture inside of the engine. Materials are defined inside of a Valve Material (.vmt) file. This is a high-level script that details how a texture is to be rendered.
| |
|
| |
| There are many [[shader]]s that can be used to render a texture. To begin with, we'll use a simple shader: <code>LightmappedGeneric</code>. This shader is used for world surfaces that should receive [[lightmap]]s.
| |
|
| |
| The simplest definition of this shader is:
| |
|
| |
| <pre>
| |
| "LightmappedGeneric"
| |
| {
| |
| "$basetexture" "test/MyTexture"
| |
| }
| |
| </pre>
| |
|
| |
| This will render the <code>"test/MyTexture"</code> .vtf file opaquely and with lightmaps applied to it. This is most generally used for textures applied to brush surfaces (like walls). With a .vtf file and .vmt file created, we can use this texture inside of Hammer on surfaces.
| |
|
| |
| One of the easiest methods of creating new .vmt files is to open an existing .vmt that has similar properties to the material you are creating. Edit the contents of the file and save it with a different name to create a new material.
| |
|
| |
|
| |
|
| |
| ==More about .vmt files==
| |
|
| |
| Let’s start by looking at an example of a [[VMT|.vmt]] file:
| |
|
| |
| <pre>
| |
| "LightmappedGeneric"
| |
| {
| |
| // String values are quoted
| |
| "$basetexture" "shadertest/LightmappedTexture"
| |
| "$envmap" "shadertest/LightmappedTexture_envmap"
| |
|
| |
| // Vector values are quoted
| |
| "$color" "[1 0 0]"
| |
| // Float and integer values are *not* quoted
| |
|
| |
| "$alpha" 0.5
| |
| "$nocull" 1
| |
| }
| |
| </pre>
| |
|
| |
| The first line of the .vmt file is the name of the [[Shader Types and Parameters|shader to be used]]. The material variables for the shader are defined inside the curly braces. Note that you should not have '=' between the material variable name and its value. Also note that comment lines use '//'. Any text after the '//' on the same line will be ignored when the material is loaded.
| |
|
| |
| If the shader needs to <i>fallback</i> to a simpler shader because it's running on a lower-end system, you can optionally specify an additional block to override material variable values specified in the original block.
| |
|
| |
| Here's an example:
| |
|
| |
| <pre>
| |
| "LightmappedGeneric"
| |
| {
| |
| "$basetexture" "shadertest/LightmappedTexture"
| |
|
| |
| "$envmap" "shadertest/LightmappedTexture_envmap"
| |
|
| |
| // If the shader falls back to shader "LightmappedGeneric_DX7",
| |
| // then the environment map defined in this block will be used instead of the
| |
| // one defined above. Since $basetexture isn't defined in this block,
| |
| // the original one will be used.
| |
| "LightmappedGeneric_DX7"
| |
| {
| |
| "$envmap" "shadertest/OverrideEnvMap"
| |
| }
| |
|
| |
| // If the shader falls back to shader "LightmappedGeneric_DX6",
| |
| // then the base texture defined in this block will be used instead of the
| |
| // one defined above. Since $envmap isn't defined in this block, the original
| |
| // one will be used.
| |
| "LightmappedGeneric_DX6"
| |
| {
| |
| "$basetexture" "shadertest/OverrideTexture"
| |
| }
| |
| }
| |
| </pre>
| |
|
| |
| For information on shader fallbacks, see '''Material choices and rendering performance''' in [[Controlling Geometry Visibility and Compile Times]] and [[Half-Life 2 Shader Fallbacks]].
| |
|
| |
| One other thing you'll see in the .vmt file format is the occasional variable starting with a '%'.
| |
|
| |
| For example:
| |
|
| |
| <pre>
| |
| "UnlitGeneric"
| |
| {
| |
| $envmap" "shadertest/shadertest_envmap"
| |
| %tooltexture" "shadertest/shadertest_envmap"
| |
| }
| |
| </pre>
| |
|
| |
| This simply means that the variable is used by tools only and won't be loaded by the engine. The only variables that need '%' are <code>'%tooltexture"</code>, <code>"%keywords"</code>, <code>"%detailtype"</code>, and all of the compile variables like <code>"%compileWater"</code> or <code>"%compileHint"</code>.
| |
|
| |
|
| |
|
| |
| ==Using Vtex on the command-line==
| |
|
| |
| For advanced users, <code>vtex.exe</code> can also be executed and scripted from a Windows command prompt. See [[Vtex]] for more information.
| |
|
| |
|
|
| |
|
