4 <meta http-equiv="Content-Type" content="text/html; charset=windows-1252">
\r
5 <meta name="GENERATOR" content="Microsoft FrontPage 4.0">
\r
6 <meta name="ProgId" content="FrontPage.Editor.Document">
\r
7 <title>Glossary</title>
\r
10 <body background="../pics/background.jpg" text="#FFFFFF" link="#FFFFFF" vlink="#FFFFFF" alink="#FFFFFF">
\r
13 <p align="center">Glossary</p>
\r
15 <table border="1" cellspacing="1" width="100%" bordercolor="#808080" bgcolor="#000000" cellpadding="10">
\r
19 <b><font FACE="Times New Roman">
\r
20 <p>Root Shader</font></b><font FACE="Times New Roman">: a shader that is part of
\r
21 a family of related shaders used to texture a terrain entity. It represents a
\r
22 terrain texture in its unblended state. The naming convention for a root shader
\r
23 is <metashadername>_#.</p>
\r
25 <p>Blend Shader</b>: a shader that is part of a family of related shaders used
\r
26 to texture a terrain entity. It represents a terrain texture in its blended
\r
27 state, two textures that crossfade across each other. The naming convention for
\r
28 a blend shader is <metashadername>_#to#.</p>
\r
30 <p>Metashader:</b> the identifying name of a group of related shaders used to
\r
31 texture a terrain entity. By way of example, the metashader name used to texture
\r
32 mpterra2 was
\85 mpterra2. Its root shaders had names like mpterra2_0,
\r
33 mpterra2_1, and mpterra2_2. Its blend shaders were named mpterra2_0to1,
\r
34 mpterra2_1to2, and mpterra2_0to2.</p>
\r
37 <p align="center"><a href="adding_bots.html">Back</a> - <a href="table_of_contents.html">Table
\r
38 of Contents</a> - <a href="new_or_revised_q3map_shader_comm.html">Q3Map Shader
\r
48 <p align="center">-26-</p>
\r