OldSiteResourcesQuake3ShaderManual - Revision history

EricChadwick: newline space char

2015-11-17T12:42:21Z

newline space char

2015-11-17T12:40:50Z

code blocks fixed

2015-11-17T12:36:21Z

cleanup: template, headings, indents, category

2015-01-23T00:41:15Z

fixing image syntax

2014-07-29T08:44:32Z

6 revisions

2010-07-06T04:38:42Z

breaking WikiName automatic links to temporarily remove broken linking

2010-07-06T04:37:35Z

2010-07-06T04:33:16Z

2006-06-09T06:41:10Z

2006-06-09T06:39:20Z

@@ Line 808: / Line 808: @@
 '''<frequency>''': this is wave peaks per second.
- '''Wave Functions <func>'''
+'''Wave Functions <func>'''
 '''Sin wave''': the texture expands smoothly to its peak dimension and then shrinks smoothly to its valley dimension in a flowing manner.

@@ Line 1,144: / Line 1,144: @@
 The alpha channel can also be used to merge a texture (including one that contains black) into another image so that the merged art appears to be and opaque decal on a solid surface (unaffected by the surface it appears to sit on), without actually using an alpha function. The following is a very simple example:
-  [[Image:OldSiteResourcesQuake3ShaderManual$image003.jpg]]
+  [[File:image002.png|left|600px]]<br clear="all" />
- [[Image:OldSiteResourcesQuake3ShaderManual$image002.png]]
   Figure 1

@@ Line 1,030: / Line 1,030: @@
 F.) the detail stage MUST use "blendFunc GL_DST_COLOR GL_SRC_COLOR".  Any
-other [[BlendFunc]] will cause mismatches in brightness between detail and non-detail views.;
+other BlendFunc will cause mismatches in brightness between detail and non-detail views.;
 G.) the detail stage should scale its textures by some amount (usually between 3 and 12) using "tcMod" to control density. This roughly corresponds to coarseness. A very large number, such as 12, will give very fine detail, however that detail will disappear VERY quickly as the viewer moves away from the wall since it will be MIP mapped away. A very small number, e.g. 3, gives diminishing returns since not enough is brought in when the user gets very close. I'm currently using values between 6 and 9.5. You should use non-integral numbers as much as possible to avoid seeing repeating patterns.

@@ Line 739: / Line 739: @@
 Getting a handle on this concept is absolutely key to understanding all shader manipulation of graphics.
-[[BlendFunc]] or “Blend Function” is the equation at the core of processing shader graphics.  The formula reads as follows:
+BlendFunc or “Blend Function” is the equation at the core of processing shader graphics.  The formula reads as follows:
   '''[Source * <srcBlend>] + [Destination * <dstBlend>]'''

@@ Line 655: / Line 655: @@
 '''<texture1> … <texture8>:'''  the texturepath/texture name for each animation frame must be explicitly listed. Up to eight frames (eight separate .tga files) can be used to make an animated sequence.  Each frame is displayed for an equal subdivision of the frequency value.
-'''Example:''' ''[[AnimMap]] 0.25 animMap 10 textures/sfx/b_flame1.tga textures/sfx/b_flame2.tga textures/sfx/b_flame3.tga textures/sfx/b_flame4.tga'' would be a 4 frame animated sequence, calling each frame in sequence over a cycle length of 4 seconds.  Each frame would be displayed for 1 seconds before the next one is displayed. The cycle repeats after the last frame in sequence is shown.
+'''Example:''' ''AnimMap 0.25 animMap 10 textures/sfx/b_flame1.tga textures/sfx/b_flame2.tga textures/sfx/b_flame3.tga textures/sfx/b_flame4.tga'' would be a 4 frame animated sequence, calling each frame in sequence over a cycle length of 4 seconds.  Each frame would be displayed for 1 seconds before the next one is displayed. The cycle repeats after the last frame in sequence is shown.
 '''Design Notes:''' To make a texture image appear for an unequal (longer) amount of time (compared to other frames), repeat that frame more than once in the sequence.

← Older revision	Revision as of 08:44, 29 July 2014
(No difference)