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>New or Revised Q3map Shader Commands</title>
\r
10 <body background="../pics/background.jpg" text="#FFFFFF" link="#FFFFFF" vlink="#FFFFFF" alink="#FFFFFF">
\r
12 <b><font FACE="Arial" SIZE="5">
\r
13 <p align="center">New or Revised Q3map Shader Commands</p>
\r
16 <table border="1" cellspacing="1" width="100%" bordercolor="#808080" bgcolor="#000000" cellpadding="10">
\r
19 <p><font size="3">q3map command line switches:</font></p>
\r
25 Number of threads used to compile the map. For the fastest compile
\r
26 times the number of threads is set to the number of system processors.
\r
28 Write a .gl file of the bsp tree for debugging.
\r
30 Output verbose information.
\r
32 Enable realtime debug drawing output.
\r
34 Water, slime and lava brushes are not compiled and won't show up when running the map in Quake.
\r
40 Detail brushes are not compiled and won't show up when running the map in Quake.
\r
42 Detail brushes will be treated as normal brushes.
\r
44 Only change the entities in a .bsp using a .ent file.
\r
46 Only change the textures in a .bsp file.
\r
50 Visible surfaces that cross fog boundaries will not be split along the bound.
\r
51 This can cause visually incorrect fog in the map.
\r
53 Visible surfaces are not subdivided as required by shader tesselation.
\r
54 The shader parameter "tesssize" sets the tesselation of a surface.
\r
56 Only test the map for leaks. If a leak is found the compilation is stopped.
\r
58 Output verbose information about entity sub-models.
\r
60 Curves are not compiled and won't show up when running the map in Quake.
\r
62 T-junctions are not fixed. This can cause tiny slits where a surface meets halfway another surface.
\r
64 Expands all the brush planes and saves a new map out to allow visual inspection of the clipping bevels
\r
66 Output files to a folder called "tmp".
\r
68 Write out a fakemap.map This map will contain a worldspawn entity with all the world brushes.
\r
70 Set the lightmap pixel size to NxN units. Default 16x16.
\r
72 Will enable custom surface flags (see below)
\r
78 Number of threads used to compile the map. For the fastest compile
\r
79 times the number of threads is set to the number of system processors.
\r
81 Only calculate a very loose visiblity list. It doesn't take much time to
\r
82 calculate but a lot more polygons will be drawn by the Q3 engine than necesary.
\r
84 Merge bsp leaves before calculating the visibility list. This will speed up
\r
85 the vis calculations but mostly more polygons will be drawn by the Q3 engine
\r
88 Disable the passage visibility algorithm. The passage vis is faster and a bit more
\r
89 tight than the old algorithm.
\r
93 Output verbose information.
\r
95 Don't sort the portals on complexity. Sorting mostly speeds up visibility calculations
\r
96 because more complex portals can use information from less complex portals.
\r
98 Don't delete the .prt file after creating the visibility list.
\r
100 Input files will be read from a folder called "tmp".
\r
102 Output files will be written to a folder called "tmp".
\r
109 Number of threads used to compile the map. For the fastest compile
\r
110 times the number of threads is set to the number of system processors.
\r
112 This scales the light intensity of area lights.
\r
114 This scales the light intensity of point lights.
\r
116 No light tracing is performed. As a result no shadows will be casted.
\r
118 Enable patches casting shadows.
\r
120 Don't calculate vertex lighting.
\r
122 Don't calculate light grid for dynamic model lighting.
\r
124 Take four samples per lightmap pixel and store the average light value of these
\r
125 four samples for the actual lightmap pixel.
\r
126 This super sampling is used for anti-aliasing.
\r
128 Just like -extra four samples per lightmap pixel are calculated. However the
\r
129 average of 12 samples is stored per lightmap pixel.
\r
131 Set the lightmap pixel size to NxN units. Default 16x16.
\r
133 Create a debugging border around the lightmap.
\r
135 Output verbose information.
\r
146 Number of threads used to compile the map. For the fastest compile
\r
147 times the number of threads is set to the number of system processors.
\r
149 This scales the light intensity of area lights.
\r
151 This scales the light intensity of point lights.
\r
153 Don't calculate vertex lighting.
\r
155 Don't calculate light grid for dynamic model lighting.
\r
157 No polygon stitching before lighting.
\r
159 Don't use alpha shading at all.
\r
161 Don't use colored alpha shading. The alpha channel will be used as if it were binary.
\r
162 The light goes through or not and does not change color.
\r
164 Use the "-light" light algorithm for all surface unless a surface
\r
165 uses a shader with the shader option "q3map_vlight".
\r
167 Set the lightmap pixel size to NxN units. Default 16x16.
\r
169 Output verbose information.
\r
171 <p><font size="3">The q3map options are a subset of the shader instructions that require
\r
172 recompiling of the map.</font></p>
\r
173 <p><font size="3">q3map_tracelight</font></p>
\r
174 <p><font size="3"> [<font color="#FFFF00">NEW</font>] Surfaces using a shader with this option will always be lit with the
\r
175 original "-light" light algorithm. Patches will not cast shadows on
\r
176 this surface unless the shader option q3map_patchshadows is used.</font></p>
\r
177 <p><font size="3">q3map_patchshadows</font></p>
\r
178 <p><font size="3"> [<font color="#FFFF00">NEW</font>] When this option is used in conjunction with the original (-light)
\r
179 lighting algorithm, surfaces with textures modified by this option will will
\r
180 show shadows cast by curve patches (under normal circumstances, curve patches do
\r
181 not cast shadows).</font></p>
\r
182 <p><font size="3">q3map_vertexshadows</font></p>
\r
183 <p><font size="3"> [<font color="#FFFF00">NEW</font>] By default, no shadows are cast on vertex-only lit surfaces (see
\r
184 surfaceparm pointlight). Also when running Quake III Arena in vertex lighting
\r
185 mode, no shadows are cast upon any surfaces (shadows are part of the light map).
\r
186 When using this shader option shadows *will* be cast on the surface when vertex
\r
187 lit. However sharp shadow edges won't be seen on the surface because light
\r
188 values are only calculated at the vertexes.</font></p>
\r
189 <p><font size="3">q3map_novertexshadows</font></p>
\r
190 <p><font size="3"> [<font color="#FFFF00">NEW</font>] Shaders used for misc_models and terrain can now use
\r
191 q3map_novertexshadows to disable shadows to be cast at the vertex lit surfaces.
\r
192 Shadows being cast at small misc_model objects often makes sense. However
\r
193 shadows on large vertex lit terrain surfaces often look bad. By default no
\r
194 shadows are cast at forced vertex list surfaces ( shaders with "pointlight"
\r
196 <p><font color="#FFFFFF" size="3">q3map_forcesunlight</font></p>
\r
197 <p><font color="#FFFFFF" size="3"> [</font><font color="#FFFF00" size="3">NEW</font><font color="#FFFFFF" size="3">] No sunlight is cast at vertex lit md3 models and terrain by default.
\r
198 Using this option sunlight (overbright bits created by q3map_sun option) will be
\r
199 cast on these surfaces.</font></p>
\r
200 <p><font size="3">q3map_vertexscale <scale></font></p>
\r
201 <p><font size="3"> [<font color="#FFFF00">NEW</font>] The light value at the vertexes of a surface using a shader with this
\r
202 option is multiplied by the scale value. This is a way to lighten or darken a
\r
203 vertex light only surface in comparison to other, light-map lit surfaces around
\r
205 <p><font size="3">q3map_notjunc</font></p>
\r
206 <p><font size="3"> [<font color="#FFFF00">NEW</font>] Surfaces modified by a shader with this option are not used for
\r
207 tjunction fixing.</font></p>
\r
208 <p><font size="3">q3map_vlight</font></p>
\r
209 <p><font size="3"> [<font color="#FFFF00">NEW</font>] Surfaces modified by a shader with this option will always be lit with
\r
210 the "-vlight" algorithm when q3map is used with the options "-vlight
\r
211 -tracelight".</font></p>
\r
212 <p><font size="3">q3map_lightmapsamplesize <S></font></p>
\r
213 <p><font size="3"> [<font color="#FFFF00">NEW</font>] Surfaces using a shader with this shader option will use lightmaps with
\r
214 pixel size SxS. This option can be used to produce high resolution shadows on
\r
215 certain surfaces or can be used to reduce the size of lightmap data where high
\r
216 resolution shadows are not required.</font></p>
\r
217 <p><font size="3">q3map_lightimage <image></font></p>
\r
218 <p><font size="3"> Image to use for the light color of a surface light instead of the image(s)
\r
219 used by the shader. Color is averaged from the texture. Texture must be the same
\r
220 size as the base image map.</font></p>
\r
221 <p><font size="3">q3map_surfacelight <value></font></p>
\r
222 <p><font size="3">Sets the amount of light this surface emits.</font></p>
\r
223 <p><font size="3">q3map_lightsubdivide <value></font></p>
\r
224 <p><font size="3"> A surface light is subdivided into a bunch of point lights for the actual
\r
225 lighting of the world. This parameter controls the space between those point
\r
226 lights. Default value is 120.</font></p>
\r
227 <p><font size="3">q3map_backsplash <percent> <distance></font></p>
\r
228 <p><font size="3"> A surface light is also lit by itself using back splash point lights with a
\r
229 lower intensity. The <percent> parameter specifies the intensity
\r
230 percentage they use from the q3map_surfacelight <value> parameter. The
\r
231 <distance> parameter controls the distance of these back splash lights
\r
232 from the surface. You can set the <percent> to zero or a negative value to
\r
233 disable the back splash lights.</font></p>
\r
234 <p><font size="3"> q3map_globaltexture</font></p>
\r
235 <p><font size="3">When this option is set the texture is not aligned to the world.</font></p>
\r
236 <p><font size="3"> q3map_backshader <shader></font></p>
\r
237 <p><font size="3"><shader> is the path/name of the shader or texture to be used at the
\r
238 back side of the surface.</font></p>
\r
239 <p><font size="3"> q3map_flare <shader></font></p>
\r
240 <p><font size="3">Creates a flare using the specified <shader> at the center of the
\r
241 surface using a shader with this option.</font></p>
\r
242 <p><font size="3"> light <value></font></p>
\r
243 <p><font size="3">Old style flare specification always using the shader "flareshader".
\r
244 The <value> parameter is unused.</font></p>
\r
245 <p><font size="3"> q3map_sun <red> <green> <blue> <intensity>
\r
246 <degrees> <elevation></font></p>
\r
247 <p><font size="3">Color will be normalized, so it doesn't matter what range you use. The
\r
248 intensity falls off with angle but not distance. A value of 100 is a fairly
\r
249 bright sun.</font></p>
\r
250 <p><font size="3"> degree of 0 = from the east, 90 = north, etc.</font></p>
\r
251 <p><font size="3"> elevation of 0 = sunrise/set, 90 = noon</font></p>
\r
252 <p><font size="3"> surfaceparm pointlight</font></p>
\r
253 <p><font size="3">Surfaces using a shader with this parameter will always be vertex lit</font></p>
\r
254 <p><font size="3">This option can be used to reduce the lightmap data. Often used on surfaces</font></p>
\r
255 <p><font size="3">that don't need any shadows.</font></p>
\r
256 <p><font size="3">Surfaceparm dust</font></p>
\r
257 <p><font size="3">If a player lands (jumps onto) on a surfaces using a shader with this
\r
258 parameter, a put of dust will appear at the player
\92s feet. Note that the
\r
259 worldspawn entity of that map must have an enableDust key set to a value of 1.</font></p>
\r
261 <font FACE="Arial" SIZE="5"><b><font SIZE="4">
\r
262 <p>Custom surfaceparms</p>
\r
263 </font></b><font SIZE="2">
\r
264 <p>With the new q3map tool you can add custom surface parameters for mods
\r
265 without the need to recompile the q3map tool. These custom surfaceparms are
\r
266 stored in a file called
\91custinfoparms.txt
\92 in the folder scripts/. An
\r
267 example of this file with the new surfaceparm treacle and surfaceparm grass is
\r
269 <p>// Custom Infoparms File<br>
\r
270 // Custom Contentsflags<br>
\r
274 // Custom Surfaceflags<br>
\r
280 <p>NOTE:</b> For linux users, when using the -custinfoparms parameter q3map
\r
281 first looks in your homedir, and only if it doesn't find a custinfoparms.txt
\r
282 there, it uses the one stored in the</p>
\r
283 <p>quake3 install dir (usually /usr/local/games).</p>
\r
286 <p>Content Flags</p>
\r
287 </b><font SIZE="2">
\r
288 <p>Contents flags are flags similar to CONTENTS_FOG in the original Q3A. These
\r
289 flags define the contents of volumes inside the game (for instance lava, fog,
\r
291 <p>If you look in the source file game/surfaceflags.h, it has defines for all
\r
292 contents flags. The define is split into a name and a hexadecimal value, for
\r
293 instance CONTENTS_PLAYERCLIP 0x10000. These hexadecimal values are powers of 2
\r
294 and can be ored together (binary) to form a bit mask. Up to 32 contents flags
\r
295 can be ored together this way.</p>
\r
297 <p>Example</b>: creating a volume with treacle.</p>
\r
298 <p>The following outlines how a custom contents flag can be added and used in a
\r
299 mod. First open the
\91custinfoparms.txt
\92 file and add
\91treacle 0x4000
\92\r
300 to the Custom Contentsflags section as shown in the example file above (0x4000
\r
301 is one of the unused values available for custom use). Next write a shader
\r
302 script which uses
\91surfaceparm treacle
\92. Apply this new shader to all sides
\r
303 of a brush in a test map. When you compile the map, add the -custinfoparms
\r
304 parameter to the command line following q3map.</p>
\r
305 <p>Next, add CONTENTS_TREACLE 0x4000 to the source file game/surfaceflags.h in
\r
306 your mod. Now you can call the point contents function. If the point is inside
\r
307 the brush with the shader using the
\91surfaceparm treacle
\92 then the point
\r
308 contents call will return a bit mask with CONTENTS_TREACLE set. This can for
\r
309 instance be used to slow down player movement when a player is inside such a
\r
313 <p>Surface Flags</p>
\r
314 </b><font SIZE="2">
\r
315 <p>The surface flags are texture properties that often affect entities in
\r
316 contact with surfaces using such flags. The
\91surfaceparm metalsteps
\92\r
317 parameter from Q3A is a good example.</p>
\r
318 <p>If you look in the source file game/surfaceflags.h, it has defines for all
\r
319 surface flags. The define is split into a name and a hexadecimal value, for
\r
320 instance SURF_NODAMAGE 0x1. These hexadecimal values are powers of 2 and can be
\r
321 ored together (binary) to form a bit mask. Up to 32 surface flags can be ored
\r
322 together this way.</p>
\r
324 <p>Example</b>: Making
\91footsteps on grass
\92 sounds</p>
\r
325 <p>The following outlines how a custom surface flag can be added and used in a
\r
326 mod. First open up the
\91custinfoparms.txt
\92 file and add 'grass 0x80000' to
\r
327 the Custom Surfaceflags section as shown in the example file above (0x80000 is
\r
328 the first available unused value in surfaceflags.h for surface flags). Next
\r
329 write a shader script which uses a grass image and has 'surfaceparm grass
\92.
\r
330 Create a test map with the grass shader covering the ground surface. When you
\r
331 compile the map, add the -custinfoparms parameter to the command line following
\r
333 <p>Next, add SURF_GRASS 0x80000 to the source file game/surfaceflags.h in your
\r
334 mod. Now you'll be able to execute a trace and the trace information will be
\r
335 returned in the trace_t structure. If the trace hits a surface with the grass
\r
336 surfaceparm then the SURF_GRASS flag will be set in trace_t->surfaceFlags.
\r
337 Such a trace can be used to trigger playing a sound of a person stepping on
\r
338 grass. For a reference example, see the existing metal steps in the game code.</p>
\r
345 <p align="center"><font face="Arial" size="3"><a href="glossary.html">Back</a> - <a href="table_of_contents.html">Table
\r
346 of Contents</a> - <a href="related_links.html"> Links</a></font></p>
\r
348 <font FACE="Arial" SIZE="5">
\r
350 <p> </font></td>
\r
357 <p align="center">-27-</p>
\r
projects / xonotic / netradiant.git / blob