quick/netradiant-custom
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

tweak docs

Browse Source
This commit is contained in:
Garux
2021-11-08 11:28:00 +03:00
parent 53382854f9
commit d4ba9c3bfc
6 changed files with 34 additions and 21 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/shaderManual/fur.html
View File

@@ -58,7 +58,7 @@
<img src="fur.jpg" tppabs="http://robotrenegade.com/q3map2/docs/shader_manual/_images/fur.jpg" width="400" height="300" alt="Tribble" class="center" />
<h2>q3map_cloneShader</h2>
<p><a href="file:///C:/Users/Emile/Desktop/Web%20Projects/docs/shader_manual_2.4_2010-04/q3map-global-directives.html#q3map_cloneShader">q3map_cloneShader</a> allows the base shader to inherit the target shader's properties and appearance. Beware not to reference another cloning shader or itself as this can lead to an infinite loop. For fur, the base shader is the texture applied to the polygon surface.</p>
<p><a href="q3map-global-directives.html#q3map_cloneShader">q3map_cloneShader</a> allows the base shader to inherit the target shader's properties and appearance. Beware not to reference another cloning shader or itself as this can lead to an infinite loop. For fur, the base shader is the texture applied to the polygon surface.</p>
<pre>
// base texture
@@ -77,7 +77,7 @@ textures/fur/pink_base
</pre>
<h2>q3map_fur</h2>
<p><a href="file:///C:/Users/Emile/Desktop/Web%20Projects/docs/shader_manual_2.4_2010-04/q3map-global-directives.html#q3map_fur">q3map_fur</a> generates additional surfaces above the base shader. The q3map_fur directive takes a few values: layers, offset and fade. Layers controls the number of surfaces generated (start with low values, high values will very quickly cause a reduction in performance). Offset controls the distance between layers. Fade controls how much each additional layer fades in addition to its previous layer. The fur shader shouldn't be applied to surface geometry as it is implicitly generated above the base shader.</p>
<p><a href="q3map-global-directives.html#q3map_fur">q3map_fur</a> generates additional surfaces above the base shader. The q3map_fur directive takes a few values: layers, offset and fade. Layers controls the number of surfaces generated (start with low values, high values will very quickly cause a reduction in performance). Offset controls the distance between layers. Fade controls how much each additional layer fades in addition to its previous layer. The fur shader shouldn't be applied to surface geometry as it is implicitly generated above the base shader.</p>
<pre>
// fur texture

13
docs/shaderManual/general-directives.html
View File

@@ -184,12 +184,17 @@ textures/skies/xtoxicsky_dm9
<p>The default behavior is to put all blended shaders in sort "additive" and all other shaders in sort "opaque", so you only need to specify this when you are trying to work around a sorting problem with multiple transparent surfaces in a scene.</p>
<p>The value here can be either a numerical value or one of the keywords in the following list (listed in order of ascending priority):</p>
<dl>
<dt>portal (1)</dt><dd>This surface is a portal, it draws over every other shader seen inside the portal, but before anything in the main view.</dd>
<dt>Sky (2)</dt><dd>Typically, the sky is the farthest surface in the game world. Drawing this after other opaque surfaces can be an optimization on some cards. This currently has the wrong value for this purpose, so it doesn't do much of anything.</dd>
<dt>Opaque (3)</dt><dd>This surface is opaque (rarely needed since this is the default with no blendfunc)</dd>
<dt>portal (1)</dt><dd>This surface is a portal, it draws over every other shader seen inside the portal, but before anything in the main view. Default for shaders marked as portal.</dd>
<dt>Sky (2)</dt><dd>Typically, the sky is the farthest surface in the game world. Drawing this after other opaque surfaces can be an optimization on some cards. This currently has the wrong value for this purpose, so it doesn't do much of anything. Default for skies.</dd>
<dt>Opaque (3)</dt><dd>This surface is opaque (rarely needed since this is the default with no blendfunc).</dd>
<dt>Decal (4)</dt><dd>Scorch marks etc, default with polygonOffset.</dd>
<dt>SeeThrough (5)</dt><dd>Ladders, grates, grills that may have small blended edges in addition to alpha test.</dd>
<dt>Banner (6)</dt><dd>Transparent, but very close to walls.</dd>
<dt>(7)</dt><dd>Default for fog.</dd>
<dt>Underwater (8)</dt><dd>Draw behind normal transparent surfaces.</dd>
<dt>Additive (9)</dt><dd>Normal transparent surface (default for shaders with blendfunc's)</dd>
<dt>(9)</dt><dd>Normal transparent surface (default for shaders with blendfunc's).</dd>
<dt>Additive (10)</dt><dd>Generally only used for additive type effects.</dd>
<dt>(14)</dt><dd>Used for stencil shadows.</dd>
<dt>Nearest (16)</dt><dd>This shader should always sort closest to the viewer, e.g. muzzle flashes and blend blobs.</dd>
</dl>

2
docs/shaderManual/q3map-global-directives.html
View File

@@ -208,7 +208,7 @@ textures/shaderlab_terrain/dirt_rock_grass
<dl>
<dt>layers</dt><dd>This specifies the number of desired replicated fur layers generated.</dd>
<dt>offset</dt><dd>The distance (in game units) between subsequent layers.</dd>
<dt>offset</dt><dd>The distance (in game units) between subsequent layers. It is additionally scaled by original vertex alpha color component.</dd>
<dt>fade</dt><dd>A normalized value indicating the fade falloff between subsequent layers.</dd>
</dl>

2
docs/shaderManual/quake-editor-radiant-directives.html
View File

@@ -88,7 +88,7 @@ textures/liquids/lavahell2 //path and name of new texture
-->
<h2 id="trans">qer_trans N.N</h2>
<p>This directive defines the percentage of transparency that a brush will have when seen in the editor (no effect on game rendering at all). It can have a positive value between 0 and 1. The higher the value, the less transparent the texture. Example: qer_trans 0.2 means the brush is 20% opaque and nearly invisible.</p>
<p>This directive makes brush transparent when seen in the editor (no effect on game rendering at all). It can have a positive value between 0 and 1. The higher the value, the less transparent the texture. Example: qer_trans 0.2 means the brush is 20% opaque and nearly invisible.</p>
<blockquote>
<h4>Design Notes:</h4>
<p>On GtkRadiant 1.4 and earlier, if the shader uses qer_trans and a qer_editorImage with an alpha channel, the transparent areas of the editorImage will be 100% transparent. To keep the solid areas of the editorImage opaque, use a near 1 value for qer_trans (eg. 0.9999). This is useful for grates, windows, fences, etc. If using GtkRadiant 1.5 or later, use qer_alphaFunc for editorImage masking instead.</p>

2
docs/shaderManual/stage-directives.html
View File

@@ -362,7 +362,7 @@ tcMod scroll 1 1
<p>This should be the LAST tcMod in a stage. Otherwise there may be a popping or snapping visual effect in some shaders.</p>
<h3>tcMod stretch <em>func base amplitude phase frequency</em></h3>
<p>Stretches the texture coordinates with the given function. Stretching is defined as stretching the texture coordinate away from the center of the polygon and then compressing it towards the center of the polygon. (see Chapter 1: Key Concepts for waveform parameter definitions).</p>
<p>Stretches the texture coordinates with the given function. Stretching is defined as stretching the texture coordinate away from the texture center closest to the polygon center and then compressing it towards the center. (see Chapter 1: Key Concepts for waveform parameter definitions).</p>
<h3>tcMod transform <em>m00 m01 m10 m11 t0 t1</em></h3>
<p>Transforms each texture coordinate as follows:</p>