polycount - User contributions [en]

CreateAccount

2010-05-31T22:03:29Z

VitoMiliano:

__NOTOC__
<<Action(newaccount)>>

PolycountOldTOC

2006-06-09T06:41:38Z

VitoMiliano:

__NOTOC__
<s> This was thrilling to compile. </s> This is ongoing thrills to convert to nice clean wiki formatting.

r13 has ranked pages to be converted in priority order. Pages that are crossed out and have a link next to them are ones that I have copy and pasted into the wiki. '''THEY ARE NOT DONE BEING CONVERTED YET.''' New pages should be made in a new hierarchy; "Old Site Whatever" is not where things should stay. Most are in disgusting auto-HTML-to-wiki markup, some are in a terrible wiki-but-not text format. You (whoever is doing this) must go through each page and verify each link. If a link is dead, Google search to try and find it again. If it's really gone, check the internet archive for it and make a page for it here, including salvaging any images you can. Some links go to other Polycount pages; find the wiki page that replaced that link and correct the link (unless it's a later priority, in which case leave it or make a placeholder wiki page and note that in the list). You also need to go through and clean up all the wiki formatting: it's been converted automatically from the original HTML, so it is really digusting, or it's just plain text, in which case it needs to be formatted in the first place. Some pages have duplicate information. Others are totally outdated and need to be rewritten. Still others need to be combined with existing resources on the site or with other pages. These pages should be nice and clean and mostly plain text so we can put them on the main Polycount site again. That is all.

Please keep things in the list format. Dynamic pages that will be difficult to redirect properly are in italics.

= General Links =
* Poll (poll/poll.shtml) X
* ''News archives'' (news/newsarchives.asp)
* ''News search'' (news/newsarchives.asp?function=search&advanced=1)
* <s> Contact (contacts/index.shtml) {1} </s> [[OldSiteContact]]
* Polycount for PalmOS (news/pqa.zip) X
* Links (links/index.shtml) {2}
* <s> Credits (credits/index.shtml) {1} this should be merged with the contact page </s> [[OldSiteCredits]]
= Download Database =
* ''UT2004 Models, UT2004 Vehicles, UT2003 Models, Quake 3 Models, UT Models, JKA Models, JK2 Models, GTA3 Models, Serious Sam Models, Quake 2 Models, Q3 Map Models, TA Team Models, TA Head Models, Elite Force Models, Half-Life Models, Heretic2 Models, [[CounterStrike]] Models, The Sims Models, Kingpin Models'' (downloads/ and downloads/index.asp?game=##&sort=date&order=DESC) {2}
= Other Models and Skins =
* Q3 Weapon Models (q3weapons/q3weapons-index.shtml) {3}
* HL Weapon Models (hlweapons/hlweapons-index.shtml) {3}
* UT2003 Accessories (dynamic.gamespy.com/~polycount/skins/ut2003skin-index.shtml wtf?) {3}
* Quake 2 Accessories (skins/q2skin-index.shtml) {3}
* Quake 3 Accessories (skins/q3skin-index.shtml) {3}
* Unreal T Accessories (skins/utskin-index.shtml) {3}
* Half-Life Accessories (skins/hlskin-index.shtml) {3}
* Rune Accessories (skins/runeskin-index.shtml) {3}
* Sims Accessories (skins/simskin-index.shtml) {3}
* Accessory Top-Picks (skins/top-picks/top-picks.shtml) {3} potentially X
* Top-Packs (skins/top-picks/top-packs/top-packs.shtml {3} potentially X
= Resources =
* <s> Resources (resources/index.shtml) {1} we should be able to get alot of the heavy lifting here from the community </s> [[OldSiteResources]]

Under Resources, there are these directories and significant files. Directories without any sub-content just have an index.shtml file in them listing resources elsewhere on the net. Most directories also have lots of other directories with supporting files, like images and stuff, which aren't listed for brevity.

* avp2 {3}
** index.shtml
** tutorials
*** talonengine
**** talonenginetut.shtml
* bandw {3} {i} wtf is this? Black and White
* chat-rooms {2}
** chat-index.shtml
** 2design X
*** 2design.shtml
* model_design
** model_design.shtml
* modjobs X
** modjobs.shtml
* drakan {3}
** index.shtml
** gfx
*** JSheffield.zip
* eliteforce {3}
** index.shtml
** tutorials.shtml
** tutorials
*** q3-ef
**** Q3AEF.shtml
* <s> FAQ-genera {1} probably needs reviewl </s>
** <s> faq-general-index.shtml</s> [[OldSiteResourcesFaqGeneral]]
* <s> general {1} </s> [[OldSiteResourcesGeneral]]
** misc {i} sunstorm?
*** sunstorm.shtml
* <s> tools {1} </s>
** <s> infografica.shtml </s> [[OldSiteResourcesGeneralToolsInfografica]]
** <s> polychop </s>
*** <s> gdmag.pdf </s> [[OldSiteResourcesGeneralToolsPolyChop]]
* tutorials {2}
** ALPHAWolf_Tut01
*** Low<code><nowiki></nowiki></code>Poly<code><nowiki></nowiki></code>Characters.shtml
* cswingstut
** cswingstut.shtml
* Hitman<code><nowiki></nowiki></code>Daz_Tut01
** Digital<code><nowiki></nowiki></code>Painting.shtml
* Model-unwrap
** model-unwrap.shtml
** model-unwrap-pic1.shtml
** model-unwrap-pic2.shtml
** model-unwrap-pic3.shtml
** model-unwrap-pic4.shtml
** model-unwrap-pic5.shtml
* NURBS-mapping
** Nurbs-mapping.shtml
** tutorial.html
** vrml1.html
** vrml2.html
** vrml3.html
* Shine_Tut03
** Poly<code><nowiki></nowiki></code>Reduce.shtml
* Shine_Tut04
** Making a Head.shtml
* Shine_Tut05
** Setup Bones Part1.shtml
* Surface<code><nowiki></nowiki></code>Tools
** Surface Tools for Low Poly Modeling2.doc
** Surface<code><nowiki></nowiki></code>Tools.shtml
** Surface<code><nowiki></nowiki></code>Tools-mts.shtml
* UVWunwrap
** UVWunwrap.shtml
* ASC_Export_Tut01.shtml
** Shine_Tut01.shtml
** Shine_Tut02.shtml
* <s> video_tutorials {1} </s>
** <s> video-tut-list.shtml </s> [[OldSiteResourcesGeneralVideoTutorials]]
* <s> apps.shtml {1} </s> [[OldSiteResourcesGeneralApplications]]
** <s> genmisc.shtml {1} </s> [[OldSiteResourcesGeneralMiscellaneous]]
** index.shtml
** <s> lightwave.shtml {1} </s> [[OldSiteResourcesGeneralLightwave]]
** <s> max.shtml {1} </s> [[OldSiteResourcesGeneralMax]]
** <s> maya.shtml {1} </s> [[OldSiteResourcesGeneralMaya]]
** <s> milkshape.shtml {1} </s> [[OldSiteResourcesGeneralMilkshape]]
** <s> misc.shtml {1} </s> "Sorry, I had something here, but it turned out to be illegal."
** <s> modelanim.shtml {1} </s> [[OldSiteResourcesGeneralModelingAndAnimation]]
** nst.shtml {3}
** q2m.shtml {3}
** <s> skinning.shtml {1} </s> [[OldSiteResourcesGeneralSkinning]]
** <s> tools.shtml {1} </s> [[OldSiteResourcesGeneralTools]]
** tutindex.shtml
** tutorials.shtml
* gfx (looks like game logos for pages maybe) {i} i suspect it is, thats what i think its a dup of that other directory
* <s>glossary (24 pages of definitions plus images) {1} </s> http://nathan.perilith.com/~vito/oldpolycount/glossary/
* <s> glossary2 (only one glossary page, but lots of examples files) {1} can we consolidate these? </s> http://nathan.perilith.com/~vito/oldpolycount/glossary2/glossary.html
* gta3 {3}
* halflife {2}
** index.shtml
** tools.shtml
** tutorials.shtml
** tutorials (directory with 20 pages of modeling tutorials plus example content)
* heretic2 {3}
** index.shtml
** tools.shtml
** tutorials.shtml
* jk2 {3}
** index.shtml
** tutorials
*** Model<code><nowiki></nowiki></code>Tutorial (eight files under here making this up)
*** jk2_model_construction.shtml
* kingpin {3}
** tools
*** framelist.shtml
*** tools.shtml
* index.shtml
** Kingpin-animations.html
* lithtech {3}
** tutorials
*** lithtech_primer.shtml
* index.shtml
** tools.shtml
** tutorials.shtml
* manual (how to review a model?) {i} it may go X
* nolf {3}
* quake {2}
** FAQ.shtml
** index.shtml
** tools.shtml
** tutorials.shtml
* <s> quake2 {1} </s>
** <s> tools </s>
*** <s> Prefabs </s>
**** <s> Alx_Prefabs-info.shtml </s> [[OldSiteResourcesQuake2ToolsPrefabsAlx]]
**** <s> Hunter_Prefabs-info.shtml </s> [[OldSiteResourcesQuake2ToolsPrefabsHunter]]
** <s> Testbox </s>
*** <s> testbox.shtml </s> [[OldSiteResourcesQuake2ToolsTestbox]]
* <s> tutorials </s>
** <s> NGLV </s> [[OldSiteResourcesQuake2TutorialsNglv]]
** <s> NST_Tut01 </s> [[OldSiteResourcesQuake2TutorialsNstTut1]]
** <s> Custom VWEP.shtml </s> [[OldSiteResourcesQuake2TutorialsCustomVwep]]
** <s> NST_Retro<code><nowiki></nowiki></code>Map.shtml </s> [[OldSiteResourcesQuake2TutorialsNstRetroMap]]
** <s> Weapon Skin Linking.shtml </s> [[OldSiteResourcesQuake2WeaponSkinLinking]]
* <s> FAQ.shtml </s> [[OldSiteResourcesQuake2Faq]]
** <s> FAQ-stecki.shtml </s> [[OldSiteResourcesQuake2PpmTroubleshooting]]
** <s> index.shtml </s> [[OldSiteResourcesQuake2]]
** <s> md2text.txt </s> [[OldSiteResourcesQuake2Md2ReadmeTemplate]]
** <s> q2frameslist.shtml </s> [[OldSiteResourcesQuake2FramesList]]
** <s> tools.shtml </s> [[OldSiteResourcesQuake2Tools]]
** <s> tutorials.shtml </s> [[OldSiteResourcesQuake2Tutorials]]
* quake3 {1}
** <s> Model_Doc </s>
*** <s> Model_manual_ps.htm </s> [[OldSiteResourcesQuake3ModelManual]]
* <s> Shader_Doc </s>
** <s> Q3<code><nowiki></nowiki></code>Ashader_manual.htm </s> [[OldSiteResourcesQuake3ShaderManual]]
* tools
** tutorials (lots of files below these, ugh)
*** josh
*** max-to-q3
*** MAX-to-q3data
*** Skin-shader
*** Sound<code><nowiki></nowiki></code>Pak
*** Steed-Tut
* index.shtml
** md3text.txt
** tools.shtml
** tutorials.shtml
* rune {3}
** tutorials
*** lodsettings
**** runetut-lodsettings.shtml
* index.shtml
* sims {3}
** index.shtml
** tools.shtml
** tutorials.shtml
* ssam {3}
* thps {3} {i}
* tribes {3}
** index.shtml
** tools.shtml
** tutorials.shtml
* unreal {2}
** tools
** tutorials (lots of files in these subdirs)
*** lodsettings
*** mage
*** pix
*** sounds
*** umod
*** umod-backup
*** UTut01.shtml
*** UTut02.shtml
*** UTut03.shtml
*** UTut04.shtml
*** UTut05.shtml
*** UTut06.shtml
*** Utut07.shtml
* index.shtml
** tools.shtml
** tutorials.shtml
** UTtut-mainpage.shtml
** UTtut-part5.shtml
* ut2003 {1}
** tutorials
*** backups (this might just be backup content, not sure, something about Intertwined)
*** ut2mod
*** pushing_tutorial.shtml
* index.shtml
** tools.shtml
** tutorials.shtml
Also what I'd consider resources are:

* Good, Bad and Ugly (skins/gbu/* with eight article directories under it) {2}
* Skin news archives (skins/archived-news/* with 30 pages of news under it) {i} no idea
* Articles (ten article directories below that:) {2}
** animation-tips
** BnW<code><nowiki></nowiki></code>interview
** chiq_interview_012602
** chrisbruce_072002
** Gwot062k2
** max3preview
** q3-model-preview
** Steed-gdc99
** Steed-Interview
** Steed-Interview-2
* Subdermal (six pages and a contest) {2}

= Not Linked To =
* [[AskDev]] (ask a developer column?) X this didnt pan out. a dev house wanted to help just answer questions. But pulled out right as we set it all up.
* docs/gamespace_release.zip X
* misc
** Discreet_QCon2k1 {3} {i} needs review
** e32k4 {3} {i} needs review
** gfx {i} is this just a directory full of original polycount gfx?
** id-model-renders {3}
** pimps {3} {i} needs review
** 12-3action.htm {3} {i} needs review
** gamespy-broadcastkey.txt X
** lead_action_designer.doc X
** micro-forte-syd-jobdoc.shtml X
** stuff.htm {3} {i} needs review
** Unreal_Coach_jobpost_053104.doc X
* modeloftheweek X
* modelpacks {3}
* paintchat {2} conditional that we can get it working again, free/cheap. if not... X
* previews X
** nicknacks X
* reviewlists X
* skindom (woah nelly tons of stuff here) {3}
* cutedoll.shtml (contest?) {3} archive purposes only
* info (actual static model info files, non-db) {2} after database
* reviews (actual static model review files, non-db) {2} after database

OldSiteResourcesQuake3ShaderManual

2006-06-09T06:41:10Z

VitoMiliano:

__NOTOC__
'''NOTE:''' The Quake 3 Arena Shader Manual is also
available for download in .PDF format at the following
link: [http://dl.fileplanet.com/dl/dl.asp?q2pmp/Q3AShader_manual_pdf.zip Quake 3 Arena Shader Manual in .PDF format] Quake III Arena

Shader Manual

Revision #12

By Paul Jaquays and Brian Hook

(with additional material by John Carmack, Christian Antkow, Kevin Cloud, & Adrian Carmack)

1 Preface: Making Your Own Shaders
The Manual for the [[Q3Radiant]] editor program contains a section called '''''Creating New Assets''''' that has the necessary information for setting up the files to create your own custom Quake III Arena shaders. It is recommended that you study the scripts in this document and in the individual shader scripts. Pay careful attention to syntax and punctuation. This is where you are most likely to make mistakes.

2 Introduction
The graphic engine for ''Quake III Arena'' has taken a step forward by putting much more direct control over the surface qualities of textures into the hands of designers and artists. In writing this manual, we have tried to define the concepts and tools that are used to modify textures in a way that, it is hoped, will be graspable by users who already have basic knowledge of computer graphics but are not necessarily computer programmers. It is not a tutorial, nor was it intended to be one.

= 2.1 What is a Shader? =
Shaders are short text scripts that define the properties of a surface as it appears and functions in a game world (or compatible editing tool). By convention, the documents that contain these scripts usually has the same name as the texture set which contains the textures being modified (e.g; base, hell, castle, etc,). Several specific script documents have also been created to handle special cases, like liquids, sky and special effects.

For ''Quake III Arena,'' Shader scripts are located in quake3/baseq3/scripts.

A ''Quake III Arena'' shader file consists of a series of surface attribute and rendering instructions formatted within braces (“{“ and “}”). Below you can see a simple example of syntax and format for a single process, including the Q3MAP keywords or “Surface Parameters”, which follow the first bracket and a single bracketed “stage”:

textures/liquids/lava

{

deformVertexes wave sin 0 3 0 0.1

tessSize 64

{

map textures/common/lava.tga

}

}

= 2.2 Shader Name & File Conventions =
The first line is the shader name. Shader names can be up to 63 characters long. The names are often a mirror of a pathname to a .tga file without the extension or basedir (/quake3/baseq3 in our case), but they do not need to be.

Shaders that are only going to be referenced by the game code, not modeling tools, often are just a single world, like “projectionShadow” or “viewBlood”.

Shaders that are used on characters or other polygon models need to mirror a .tga file, which allows the modelers to build with normal textures, then have the special effects show up when the model is loaded into the game.

Shaders that are placed on surfaces in the map editor commonly mirror a .tga file, but the “qer_editorimage” shader parameter can force the editor to use an arbitrary image for display.

Shader pathnames have a case sensitivity issue – on windows, they ''aren’t'' case sensitive, but on unix they ''are''. Try to always use lowercase for filenames, and always use forward slashes “/” for directory separators.

= 2.3 Shader Types =
The keywords that affect shaders are divided into two classes. The first class of keywords are global parameters. Some global parameters ( '''“surfaceparms.”''' And all '''“q3map_” keywords''') are processed by Q3MAP, and change physical attributes of the surface that uses the shader. These attributes can affect the player. To see changes in these parameters one must re-bsp the map.

The remaining global keywords, and all Stage Specific Keywords are processed by the renderer. They are appearance changes only and have no effect on game play or game mechanics. Changes to any of these attributes will take effect as soon as the game goes to another level or vid_restarts (type command '''vid_restart''' in the game console).

Shader keywords are ''not'' case sensitive.

'''IMPORTANT NOTE:''' some of the shader commands may be order dependent, so it’s good practice to place all global shader commands (keywords defined in this section) at the very beginning of the shader and to place shader stages at the end (see various examples).

= 2.4 Key Concepts =
Ideally, a designer or artist who is manipulating textures with shader files has a basic understanding of wave forms and knows about mixing colored light (high school physics sort of stuff). If not, there are some concepts you need to have a grasp on to make shaders work for you.

== 2.4.1 Surface Effects vs. Content Effects vs. Deformation Effects ==
Shaders not only modify the visible aspect of textures on a geometry brush, curve, patch or mesh model, but they can also have an effect on both the content, “shape,” and apparent movement of those things. A surface effect does nothing to modify the shape or content of the brush. Surface effects include glows, transparencies and rgb (red, green, blue) value changes. Content shaders affect the way the brush operates in the game world. Examples include water, fog, nonsolid, and structural. Deformation effects change the actual shape of the affected brush or curve, and may make it appear to move.

== 2.4.2 Power Has a Price ==
The shader script gives the designer, artist and programmer a great deal of easily accessible power over the appearance of and potential special effects that may be applied to surfaces in the game world. But it is power that comes with a price tag attached, and the cost is measured in performance speed. Each shader phase that affects the appearance of a texture causes the ''Q3:A'' engine to make another processing pass and redraw the world. Think of it as if you were adding all the shader-affected triangles to the total r_speed count for each stage in the shader script. A shader-manipulated texture that is seen through another shader manipulated texture (e.g.; a light in fog) has the effect of ''adding'' the total number of passes together for the affected triangles. A light that required two passes seen through a fog that requires one pass will be treated as having to redraw that part of the world three times.

== 2.4.3 RGB Color ==
RGB means “Red, Green, Blue.” Mixing red, green and blue light in differing intensities creates the colors in computers and television monitors. This is called ''additive color'' (as opposed to the mixing of pigments in paint or colored ink in the printing process, which is subtractive color). In ''Quake III Arena'' and most higher-end computer art programs (and the color selector in Windows), the intensities of the individual Red, Green and Blue components are expressed as number values. When mixed together on a screen, number values of equal intensity in each component color create a completely neutral (gray) color. The lower the number value (towards 0), the darker the shade. The higher the value, the lighter the shade or the more saturated the color until it reaches a maximum value of 255 (in the art programs). All colors possible on the computer can be expressed as a formula of three numbers. The value for complete black is 0 0 0. The value for complete white is 255 255 255. However, the ''Quake III Arena'' graphics engine requires that the color range be “normalized” into a range between 0.0 and 1.0.

== 2.4.4 Normalization: a Scale of 0 to 1 ==
The mathematics in ''Quake III Arena'' use a scale of 0.0 to 1.0 instead of 0 to 255. Most computer art programs that can express RGB values as numbers use the 0 to 255 scale. To convert numbers, divide each of the art program’s values for the component colors by 255. The resulting three values are your ''Quake III Arena'' formula for that color component. The same holds true for texture coordinates.

== 2.4.5 Texture Sizes ==
TGA texture files are measured in pixels (picture elements). Textures are measured in powers of 2, with 16 x16 pixels being the smallest (typically) texture in use. Most will be larger. Textures need not be square, so long as both dimensions are powers of 2. Examples include: 32x256, 16x32, 128x16.

== 2.4.6 Color Math ==
In ''Quake III Arena'' , colors are changed by mathematical equations worked on the textures by way of the scripts or “programlets” in the shader file. An equation that adds to or multiplies the number values in a texture causes it to become darker. Equations that subtract from or modulate number values in a texture cause it to become lighter. Either equation can change the hue and saturation of a color.

== 2.4.7 Measurements ==
The measurements used in the shaders are in either game units, color units, or texture units.

· '''Game unit:''' A game unit is used by deformations to specify sizes relative to the world. Game units are the same scale we have had since way back in the ''Wolfenstein'' days – 8 units equals one foot. The default texture scale used by the [[Q3Radiant]] map editor results in two texels for each game unit, but that can be freely changed.

· '''Color units''': Colors scale the values generated by the texture units to produce lighting effects. A value of 0.0 will be completely black, and a value of 1.0 will leave the texture unchanged. Colors are sometimes specified with a single value to be used across all red, green, and blue channels, or sometimes as separate values for each channel.

· '''Texture units:''' This is the normalized (see above) dimensions of the original texture image (or a previously modified texture at a given stage in the shader pipeline). A full texture, regardless of its original size in texels, has a normalized measurement of 1.0 x 1.0. For normal repeating textures, it is possible to have value greater than 1.0 or less than 0.0, resulting in repeating of the texture. The coordinates are usually assigned by the level editor or modeling tools, but you still need to be aware of this for scrolling or turbulent movement of the texture at runtime.

== 2.4.8 Waveform Functions ==
Many of the shader functions use waveforms to modulate measurements over time. Where appropriate, additional information is provided with wave modulated keyword functions to describe the effect of a particular waveform on that process. Currently there are five waveforms in use in ''Q3A'' shaders:

'''Sin''': Sin stands for sine wave, a regular smoothly flowing wave ranging from –1 to 1.

'''Triangle:''' Triangle is a wave with a sharp ascent and a sharp decay, ranging from 0 to 1. It will make a choppy looking wave forms.

'''Square''': A square wave simply switches from –1 to 1 with no in-between.

'''Sawtooth:''' In the sawtooth wave, the ascent is like a triangle wave from 0 to 1, but the decay cuts off sharply back to 0.

'''Inversesawtooth:''' This is the reverse of the sawtooth … instant ascent to the peak value (1), then a triangle wave descent to the valley value (0). The phase on this goes from 1.0 to 0.0 instead of 0.0 to 1.0. This wave is particularly useful for additive cross-fades.

'''Waveforms all have the following properties''':

'''<base>''' Where the wave form begins. Amplitude is measured from this base value.

'''<amplitude>''' This is the height of the wave created, measured from the base'''.''' You will probably need to test and tweak this value to get it correct for each new shader stage. The greater the amplitude, the higher the wave peaks and the deeper the valleys.

''' '''

'''<phase>''' This is a normalized value between 0.0 and 1.0. Changing phase to a non-zero value affects the point on the wave at which the wave form initially begins to be plotted. Example: In Sin or Triangle wave, a phase of 0.25 means it begins one fourth (25%) of the way along the curve, or more simply put, it begins at the peak of the wave. A phase of 0.5 would begin at the point the wave re-crosses the base line. A phase of 0.75 would be at the lowest point of the valley. If only one wave form is being used in a shader, a phase shift will probably not be noticed and phase should have a value of zero (0). However, including two or more stages of the same process in a single shader, but with the phases shifted can be used to create interesting visual effects. Example: using rgbGen in two stages with different colors and a 0.5 difference in phase would cause the manipulated texture to modulate between two distinct colors. Phase changes can also be used when you have two uses of the same effect near each other, and you don’t want them to be synchronized. You would write a separate shader for each, changing only the phase value.

'''<freq>''' Frequency. This value is expressed as repetitions or cycles of the wave per second. A value of 1 would cycle once per second. A value of 10 would cycle 10 times per second. A value of 0.1 would cycle once every 10 seconds.

3 General Shader Keywords
'''IMPORTANT NOTE:''' Once again, be aware that some of the shader commands may be order dependent, so it’s good practice to place all global shader commands (keywords defined in this section) at the very beginning of the shader and to place shader stages at the end (see various examples).

These Keywords are global to a shader and affect all stages. They are also ignored by Q3MAP.

= 3.1 skyParms <farbox> <cloudheight> <nearbox> =
Specifies how to use the surface as a sky, including an optional far box (stars, moon, etc), optional cloud layers with any shader attributes, and an optional near box (mountains in front of the clouds, etc).

'''<Farbox>''' Specifies a set of files to use as an environment box behind all cloud layers. Specify “-“ for no farbox, or a file base name. A base name of “env/test” would look for files “env/test_rt.tga”, “env/test_lf.tga”, “env/test_ft.tga”, “env/test_bk.tga”, “env/test_up.tga”, “env/test_dn.tga” to use as the right / left / front / back / up / down sides.

'''<cloudheight>''' controls apparent curvature of the cloud layers – lower numbers mean more curvature (and thus more distortion at the horizons). Higher height values create “flatter” skies with less horizon distortion. Think of height as the radius of a sphere on which the clouds are mapped. Good ranges are 64 to 256. The default value is 128.

'''<nearbox>''' Specified as farbox, to be alpha blended on top of the clouds. This has not been tested in a long time, so it probably doesn’t actually work. Set to “-“ to ignore.

Design Notes:

· If you are making a map where the sky is seen by looking up most of the time, use a lower cloudheight value. Under those circumstances the tighter curve looks more dynamic. If you are making a map where the sky is seen by looking out windows most of the time or has a map area that is open to the sky on one or more sides, use a higher height to make the clouds seem more natural.

· It is possible to create a sky with up to 8 cloud layers, but that also means 8 processing passes and a potentially large processing hit.

· Be aware that the skybox does not wrap around the entire world. The “floor” or bottom face of the skybox is not drawn by the game. If a player in the game can see that face, they will see the “hall of mirrors” effect.

'''Example: Sky script'''

textures/skies/xtoxicsky_dm9

{

qer_editorimage textures/skies/toxicsky.tga

surfaceparm noimpact

surfaceparm nolightmap

q3map_globaltexture

q3map_lightsubdivide 256

q3map_surfacelight 400

surfaceparm sky

q3map_sun 1 1 0.5 150 30 60

skyparms full 512 -

{

map textures/skies/inteldimclouds.tga

tcMod scroll 0.1 0.1

tcMod scale 3 2

}

{

map textures/skies/intelredclouds.tga

blendFunc add

tcMod scroll 0.05 0.05

tcMod scale 3 3

}

}

= 3.2 cull <side> =
Every surface of a polygon has two sides, a front and a back. Typically, we only see the front or “out” side. For example, a solid block you only show the front side. In many applications we see both. For example, in water, you can see both front and a back. The same is true for things like grates and screens.

To “cull” means to remove. The value parameter determines the type of face culling to apply. The default value is cull ''front'' if this keyword is not specified. However for items that should be inverted then the value ''back'' should be used. To disable culling, the value ''disable'' or ''none'' should be used. Only one cull instruction can be set for the shader.

== 3.2.1 cull front ==
The front or “outside” of the polygon is not drawn in the world. This is the default value. It is used if the keyword “'''cull'''” appears in the content instructions without a '''<side>''' value or if the keyword cull does not appear at all in the shader.

== 3.2.2 cull back ==
Cull back removes the back or “inside” of a polygon from being drawn in the world.

== 3.2.3 cull disable, cull none ==
Neither side of the polygon is removed. Both sides are drawn in the game. Very useful for making panels or barriers that have no depth, such as grates, screens, metal wire fences and so on and for liquid volumes that the player can see from within. Also used for energy fields, sprites, and weapon effects (e.g.; plasma).

Design Notes: For things like grates and screens, put the texture with the cull none property on one face only. On the other faces, use a non-drawing texture.

= 3.3 deformVertexes =
This function performs a general deformation on the surface’s vertexes, changing the actual shape of the surface before drawing the shader passes. You can stack multiple deformVertexes commands to modify positions in more complex ways, making an object move in two dimensions, for instance.

== 3.3.1 deformVertexes wave <div> <func> <base> <amplitude> <phase> <freq> ==
Designed for water surfaces, modifying the values differently at each point. It accepts the standard wave functions of the type '''sin''', '''triangle''', '''square, sawtooth''' or '''inversesawtooth'''. The “div” parameter is used to control the wave “spread” – a value equal to the tessSize of the surface is a good default value (tessSize is subdivision size, in game units, used for the shader when seen in the game world) .

== 3.3.2 deformVertexes normal <div> <func> <base> <amplitude ~0.1-~0.5> <frequency ~1.0-~4.0> ==
This deformation affects the normals of a vertex without actually moving it, which will effect later shader options like lighting and especially environment mapping. If the shader stages don’t use normals in any of their calculations, there will be no visible effect.

Design Notes: Putting values of 0.1 t o 0.5 in Amplitude and 1.0 to 4.0 in the Frequency can produce some satisfying results. Some things that have been done with it: A small fluttering bat, falling leaves, rain, flags.

== 3.3.3 deformVertexes bulge <bulgeWidth> <bulgeHeight> <bulgeSpeed> ==
This forces a bulge to move along the given '''s''' and '''t''' directions. Designed for use on curved pipes.

'''Specific parameter definitions for deform keywords:'''

'''<div> ''' This is roughly defined as the size of the waves that occur. It is measured in game units. Smaller values create a greater density of smaller wave forms occurring in a given area. Larger values create a lesser density of waves, or otherwise put, the appearance of larger waves. To look correct this value should closely correspond to the value (in pixels) set for tessSize (tessellation size) of the texture. A value of 100.0 is a good default value (which means your tessSize should be close to that for things to look “wavelike”).

''' '''

'''<func>''' This is the type of wave form being created. Sin stands for sine wave, a regular smoothly flowing wave. Triangle is a wave with a sharp ascent and a sharp decay. It will make a choppy looking wave forms. A square wave is simply on or off for the period of the frequency with no in between. The sawtooth wave has the ascent of a triangle wave, but has the decay cut off sharply like a square wave. An inversesawtooth wave reverses this.

'''<base>''' This is the distance, in game units that the apparent surface of the texture is displaced from the actual surface of the brush as placed in the editor. A positive value appears above the brush surface. A negative value appears below the brush surface. An example of this is the Quad effect, which essentially is a shell with a positive base value to stand it away from the model surface and a 0 (zero) value for amplitude.

'''<amplitude>''' The distance that the deformation moves away from the base value. See Wave Forms in the introduction for a description of amplitude.

'''<phase>''' See Wave Forms in the introduction for a description of phase)

'''<frequency>''' See Wave Forms in the introduction for a description of frequency)

Design Note: The div and amplitude parameters, when used in conjunction with liquid volumes like water should take into consideration how much the water will be moving. A large ocean area would have have massive swells (big div values) that rose and fell dramatically (big amplitude values). While a small, quiet pool may move very little.

== 3.3.4 deformVertexes move <x> <y> <z> <func> <base> <amplitude> <phase> <freq> ==
This keyword is used to make a brush, curve patch or md3 model appear to move together as a unit. The <x> <y> and <z> values are the distance and direction in game units the object appears to move relative to it’s point of origin in the map.

The <func> <base> <amplitude> <phase> and <freq> values are the same as found in other wave form manipulations.

The product of the function modifies the values x, y, and z. Therefore, if you have an amplitude of 5 and an x value of 2, the object will travel 10 units from its point of origin along the x axis. This results in a total of 20 units of motion along the x axis, since the amplitude is the variation both above and below the base.

It must be noted that an object made with this shader does not actually change position, it only appears to.

'''Design Note:''' If an object is made up of surfaces with different shaders, all must have matching deformVertexes move values or the object will appear to tear itself apart.

== 3.3.5 [[DeformVertexes]] autosprite ==
This function can be used to make any given triangle quad (pair of triangles that form a square rectangle) automatically behave like a sprite without having to make it a separate entity. This means that the “sprite” on which the texture is placed will rotate to always appear at right angles to the player’s view as a sprite would. Any four-sided brush side, flat patch, or pair of triangles in an .md3 model can have the '''autosprite''' effect on it. '''The brush face containing a texture with this shader keyword must be square.'''

'''Design Note''': This is best used on objects that would appear the same regardless of viewing angle. An example might be a glowing light flare.

== 3.3.6 [[DeformVertexes]] autosprite2 ==
Is a slightly modified “sprite” that only rotates around the middle of its longest axis. This allows you to make a pillar of fire that you can walk around, or an energy beam stretched across the room.

= 3.4 fogparms <red value> <green value> <blue value> <distance to Opaque> =
Note: you must also specify “surfaceparm fog” to cause q3map to identify the surfaces inside the volume. Fogparms only describes how to render the fog on the surfaces.

'''<red value> <green value> <blue value>''' These are normalized values. A good computer art program should give you the RGB values for a color. To obtain the values that define fog color for Quake III Arena , divide the desired color’s Red, Green and Blue values by 255 to obtain three normalized numbers within the 0.0 to 1.0 range.

'''<distance to opaque>''' This is the distance, in game units, until the fog becomes totally opaque, as measured from the point of view of the observer. By making the height of the fog brush shorter than the distance to opaque , the apparent density of the fog can be reduced (because it never reaches the depth at which full opacity occurs)..

· The fog volume can only have one surface visible (from outside the fog).

· Fog must be made of one brush. It cannot be made of adjacent brushes.

· Fog brushes must be axial. This means that only square or rectangular brushes may contain fog, and those must have their edges drawn along the axes of the map grid (all 90 degree angles).

·

'''Design Notes: '''

· If a water texture contains a fog parameter, it must be treated as if it were a fog texture when in use.

· If a room is to be filled completely with a fog volume, it can only be entered through one surface (and still have the fog function correctly).

· Additional shader passes may be placed on a fog brush, as with other brushes.

= 3.5 nopicmip =
This causes the texture to ignore user-set values for the '''r_picmip''' cvar command. The image will always be high resolution. Example: Used to keep images and text in the heads up display from blurring when user optimizes the game graphics.

= 3.6 nomipmap: =
This implies nopicmip, but also prevents the generation of any lower resolution mipmaps for use by the 3d card. This will cause the texture to alias when it gets smaller, but there are some cases where you would rather have this than a blurry image. Sometimes thin slivers of triangles force things to very low mipmap levels, which leave a few constant pixels on otherwise scrolling special effects.

= 3.7 polygonOffset =
Surfaces rendered with the '''polygonOffset''' keyword are rendered slightly off the polygon’s surface. This is typically used for wall markings and “decals.” The distance between the offset and the polygon is fixed. It is not a variable in Quake III Arena.

= 3.8 portal =
Specifies that this texture is the surface for a portal or mirror. In the game map, a portal entity must be placed directly in front of the texture (within 64 game units). All this does is set “sort portal”, so it isn’t needed if you specify that explicitly.

= 3.9 sort <value> =
Use this keyword to fine-tune the depth sorting of shaders as they are compared against other shaders in the game world. The basic concept is that if there is a question or a problem with shaders drawing in the wrong order against each other, this allows the designer to create a hierarchy of which shader draws in what order.

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.

The value here can be either a numerical value or one of the keywords in the following list (listed in order of ascending priority):

'''portal (1):''' This surface is a portal, it draws over every other shader seen inside the portal, but before anything in the main view.

'''Sky (2):''' 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.

'''Opaque (3):''' This surface is opaque (rarely needed since this is the default with no blendfunc)

'''Banner (6) :''' Transparent, but very close to walls.

'''Underwater (8):''' Draw behind normal transparent surfaces.

'''Additive (9):''' normal transparent surface (default for shaders with blendfuncs)

'''nearest (16):''' this shader should always sort closest to the viewer, e.g. muzzle flashes and blend blobs

4 Q3MAP Specific Shader Keywords
These keywords change the physical nature of the textures and the brushes that are marked with them. Changing any of these values will require the map to be re-compiled. These are global and affect the entire shader.

= 4.1 tessSize <amount> =
For consistency’s sake, this really should have been called q3map_tessSize. But it wasn’t. The tessSize shader controls the tessellation size (how finely a surface is chopped up in to triangles), in game units, of the surface. This is only applicable to solid brushes, not curves, and is generally only used on surfaces that are flagged with the '''deformVertexes''' keyword. Abuse of this can create a huge number of triangles. This happens during q3map processing, so maps must be reprocessed for changes to take effect.

'''Design Note:''' It can also be used on tesselating surfaces to make sure that tesselations are large, and thus, less costly in terms of triangles created.

= 4.2 q3map_backshader <shadername> =
This allows a brush to use a different shader when you are inside it looking out. By way of example, this would allow a water brush (or other) surfaces to have a different sort order (see '''''sort''''' above) or appearance when seen from the inside.

= 4.3 q3map_globaltexture =
Use this shader in the global keyword commands whenever the '''tcMod scale''' function is used in one of the later render stages. Many problems with getting shader effects to work across multiple adjacent brushes are a result of the way q3map optimizes texture precision. This option resolves that, but at the expense of some precision of the textures when they are far away from the origin of the map.

= 4.4 q3map_sun <red> <green> <blue> <intensity> <degrees> <elevation> =
This keyword in a sky shader will create the illusion of light cast into a map by a single, infinitely distance light source (sun, moon, hellish fire, etc.). This is only processed during the lighting phase of q3map.

'''<red> <green> <blue>''' Color is described by three normalized rgb values. Color will be normalized to a 0.0 to 1.0 range, so it doesn’t matter what range you use.

'''<intensity>''' is the brightness of the generated light. A value of 100 is a fairly bright sun. The intensity of the light falls off with angle but not distance.

'''<degrees>''' is the angle relative to the directions on the map file. A setting of 0 degrees equals east. 90 is north, 180 is west and 270 is south.

'''<elevation>''' is the distance, measured in degrees from the horizon (z value of zero in the map file). An elevation of 0 is sunrise/sunset. An elevation of 90 is noon

'''DESIGN NOTE: ''' Sky shaders should probably still have a '''q3map_surfacelight''' value. The “sun” gives a strong directional light, but doesn’t necessarily give the fill light needed to soften and illuminate shadows. Skies with clouds should probably have a weaker '''q3map_sun''' value and a higher '''q3map_surfacelight''' value. Heavy clouds diffuse light and weaken shadows. The opposite is true of a cloudless or nearly cloudless sky. In such cases, the “sun” or “moon” will cast stronger, shadows that have a greater degree of contrast.

'''Design Trick:''' Not certain what color formula you want to use for the sun’s light? Try this. Create a light entity. Use the [[Q3Radiant]] editor’s color selection tools to pick a color. The light’s _color key’s value will be the normalized RGB formula. Copy it from the value line in the editor (CTRL+c) and paste it into your shader.

= 4.5 q3map_surfaceLight <light value> =
The texture gives off light equal to the '''<light value>''' set for it. The relative surface area of the texture in the world affects the actual amount of light that appears to be radiated. To give off what appears to be the same amount of light, a smaller texture must be significantly brighter than a larger texture. Unless the qer_lightimage keyword is used to select a different source for the texture’s light color information, the color of the light will be the averaged color of the texture.

= 4.6 q3map_lightimage < texturepath/texturename> =
The keyword '''q3map_lightimage''' generates lighting from the average color of the TGA image specified by the q3map_lightimage.

The keyword sequence for generating light on a '''q3map_surfacelight''' should be ordered as follows:

1) '''q3map_lightimage''' ; (the texture providing the light and the color of the light)

2) '''qer_editorimage''' ; (the editor-only image used to select the source map for the texture)

3) the average color of the light emitted from the shader is calculated from the '''lightimage.''')

The reason '''q3map_lightimage''' is specified for the light in the example below, is because the blend map is predominantly yellow, and the designer wanted more yellow light to be emitted from the light.

'''Example: Taking light from another source texture'''

textures/eerie/ironcrosslt2_10000

{

q3map_lightimage textures/gothic_light/ironcrosslt2.blend.tga

// this TGA is the source for the color of the blended light

qer_editorimage textures/gothic_light/ironcrosslt2.tga

//base TGA (used because the shader is used with several

// different light values

q3map_surfacelight 10000

//emitted light value of 10,000

{

map $lightmap

//source texture is affected by the lightmap

rgbGen identity

// this command handles the overbright bits created by “sunlight”

// in the game

}

{

map textures/gothic_light/ironcrosslt2.tga

blendFunc filter

rgbGen identity

}

{

map textures/gothic_light/ironcrosslt2.blend.tga

blendFunc add

}

}

= 4.7 q3map_lightsubdivide <value> =
This allows the user to define how large, or small to make the subdivisions (triangles) in a textured surface, particularly aimed at light-emitting textures like skies. It defaults to 120 game units, but can be made larger (256 or 512) for sky boxes or smaller for light surfaces at the bottoms of cracks. This can be a dominant factor in processing time for q3map lighting.

= 4.8 surfaceparm <parm> =
All surfaceparm keywords are preceded by the word surfaceparm as follows: '''surfaceparm fog''' or '''surfaceparm noimpact.'''

== 4.8.1 alphashadow ==
This keyword applied to a texture on a brush, patch or model will cause the lighting phase of the q3map process to use the texture’s alpha channel as a mask for casting static shadows in the game world.

'''Design Note:''' Alphashadow does not work well with fine line detail on a texture. Fine lines may not cast acceptable shadows. It appears to work best with well-defined silhouettes and wider lines within the texture. Most of our tattered banners use this to cast tattered shadows.

== 4.8.2 areaportal ==
A brush marked with this keyword functions as an area portal, a break in the Q3MAP tree. It is typically placed on a very thin brush placed inside a door entity (but is not a part of that entity). The intent is to block the game from processing surface triangles located behind it when the door is closed. It is also used by the BSPC (bot area file creation compiler) in the same manner as a cluster portal. The brush must touch all the structural brushes surrounding the '''areaportal.'''

== 4.8.3 clusterportal ==
A brush marked with this keyword function creates a subdivision of the area file (.aas) used by the bots for navigation. It is typically placed in locations that are natural breaks in a map, such as entrances to halls, doors, tunnels, etc. The intent is keep the bot from having to process the entire map at once. As with the the areaportal parameter, the affected brush must touch all the structural brushes surrounding the '''areaportal.'''

== 4.8.4 donotenter ==
Read as “do not enter.” Like clusterportal, this is a bot-only property. A brush marked with donotenter will not affect non-bot players, but bots will not enter it. It should be used only when bots appear to have difficulty navigating around some map features.

== 4.8.5 flesh ==
This will cue different sounds (in a similar manner to metalsteps ) and cause blood to appear instead of bullet impact flashes.

== 4.8.6 fog ==
Fog defines the brush as being a “fog” brush. This is a Q3MAP function that chops and identifies all geometry inside the brush. The General shader keyword fogparms must also be specified to tell how to draw the fog.

== 4.8.7 lava ==
Assigns to the texture the game properties set for lava. This affects both the surface and the content of a brush.

== 4.8.8 metalsteps ==
The player sounds as if he is walking on clanging metal steps or gratings. Other than specifiying '''flesh''', '''metalsteps''', '''nosteps''', or default (i.e.; specify nothing) it is currently not possible for a designer to create or assign a specific sound routine to a texture. Note: If no sound is set for a texture, then the default footsteps sound routines are heard.

== 4.8.9 nodamage ==
The player takes no damage if he falls onto a texture with this surfaceparm

== 4.8.10 nodlight ==
Read as “No ''Dee'' Light”. A texture containing this parameter will not be affected or lit by dynamic lights, such as weapon effects. And example in ''Quake III Arena'' would be solid lava.

== 4.8.11 nodraw ==
A texture marked with nodraw will not visually appear in the game world. Most often used for triggers, clip brushes, origin brushes, and so on.

== 4.8.12 nodrop ==
When a player dies inside a volume (brush) marked nodrop, no weapon is dropped. The intend use is for “Pits of Death.” Have a kill trigger inside a nodrop volume, and when the players die here, they won't drop their weapons. The intent is to prevent unnecessary polygon pileups on the floors of pits.

== 4.8.13 noimpact ==
World entities will not impact on this texture. No explosions occur when projectiles strike this surface and no marks will be left on it. Sky textures are usually marked with this texture so those projectiles will not hit the sky and leave marks.

== 4.8.14 nomarks ==
Projectiles will explode upon contact with this surface, but will not leave marks. Blood will also not mark this surface. This is useful to keep lights from being temporarily obscured by battle damage.

'''Design Note:''' Use this on any surface with a deformVertexes keyword. Otherwise, the marks will appear on the unmodified surface location of the texture with the surface wriggles and squirms through the marks.

== 4.8.15 nolightmap ==
This texture does not have a lightmap phase. It is not affected by the ambient lighting of the world around it. It does not require the addition of an rgbGen identity keyword in that stage.

== 4.8.16 nosteps ==
The player makes no sound when walking on this texture.

== 4.8.17 nonsolid ==
This attribute indicates a brush, which does not block the movement of entities in the game world. It applied to triggers, hint brushes and similar brushes. This affects the content of a brush.

== 4.8.18 origin ==
Used on the “origin” texture. Rotating entities need to contain an origin brush in their construction. The brush must be rectangular (or square). The origin point is the exact center of the origin brush.

== 4.8.19 playerclip ==
Blocks player movement through a '''nonsolid''' texture. Other game world entities can pass through a brush marked '''playerclip'''. The intended use for this is to block the player but not block projectiles like rockets.

== 4.8.20 slick ==
This surfaceparm included in a texture should give it significantly reduced friction.

== 4.8.21 slime ==
Assigns to the texture the game properties for slime. This affects both the surface and the content of a brush.

== 4.8.22 structural ==
This surface attribute causes a brush to be seen by the Q3MAP process as a possible break-point in a BSP tree. It is used as a part of the shader for the “hint” texture. Generally speaking, any opaque texture not marked as “'''detail'''” is by default, '''structural,''' so you shouldn’t need to specify this.

== 4.8.23 trans ==
Tells q3map that pre-computed visibility should not be blocked by this surface. Generally, any shaders that have blendfuncs should be marked as surfaceparm trans.

== 4.8.24 water ==
Assigns to the texture the game properties for water.

5 Editor specific shader instructions
These instructions only affect the texture when it is seen in the [[Q3Radiant]] editor. They should be grouped with the surface parameters but ahead of them in sequence.

= 5.1 qer_editorimage < texture path/texturename> =
This keyword creates a shader name in memory, but in the editor, it displays the TGA art image specified in qer_editorimage (in the example below this is textures/eerie/lavahell.tga).

The editor maps a texture using the size attributes of the TGA file used for the editor image. When that editor image represents a shader, any texture used in any of the shader stages will be scaled up or down to the dimensions of the editor image. If a 128x128 pixel image is used to represent the shader in the editor, then a 256x256 image used in a later stage will be shrunk to fit. A 64x64 image would be stretched to fit. Be sure to check this on bouncy, acceleration, and power-up pads placed on surfaces other than 256 x 256. Use '''tcMod scale''' to change the size of the stretched texture. Remember that '''tcMod scale''' 0.5 0.5 will double your image, while '''tcMod scale''' 2 2 will halve it.

'''Design Notes:''' The base_light and gothic_light shaders contain numerous uses of this. It can be very useful for making different light styles (mostly to change the light brightnesses) without having to create a new piece of TGA art for each new shader.

textures/liquids/lavahell2 //path and name of new texture

{

qer_editorimage textures/eerie/lavahell.tga

//based on this

qer_nocarve

//cannot be cut by CSG subtract

surfaceparm noimpact

//projectiles do not hit it

surfaceparm lava

//has the game properties of lava

surfaceparm nolightmap

//environment lighting does not affect

q3map_surfacelight 3000

//light is emitted

tessSize 256

//relatively large triangles

cull disable

//no sides are removed

deformVertexes wave 100 sin 5 5 .5 0.02

fogparms 0.8519142 0.309723 0.0 128 128

{

map textures/eerie/lavahell.tga

//base texture artwork

tcMod turb .25 0.2 1 0.02

//texture is subjected to turbulence

tcMod scroll 0.1 0.1

//the turbulence is scrolled

}

}

= 5.2 qer_nocarve =
A brush marked with this instruction will not be affected by CSG subtract functions. It is especially useful for water and fog textures.

= 5.3 qer_trans <value> =
This parameter 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.

'''
'''
6 Stage Specific Keywords
Stage specifications only affect rendering. Changing any keywords or values within a stage will usually take effect as soon as a vid_restart is executed. Q3MAP ignores stage specific keywords entirely.

A stage can specify a texture map, a color function, an alpha function, a texture coordinate function, a blend function, and a few other rasterization options.

= 6.1 Texture map specification =
== 6.1.1 map <texturepath/texturename> ==
Specifies the source texture map (a 24 or 32-bit TGA file) used for this stage. The texture may or may not contain alpha channel information. The special keywords '''$lightmap''' and '''$whiteimage''' may be substituted in lieu of an actual texture map name. In those cases, the texture named in the first line of the shader becomes the texture that supplies the light mapping data for the process.

== $lightmap ==
This is the overall lightmap for the game world. It is calculated during the Q3MAP process. It is the initial color data found in the framebuffer. Note: due to the use of overbright bits in light calculation, the keyword '''rgbGen identity''' must accompany all '''$lightmap''' instructions.

== $whiteimage ==
This is used for specular lighting on MD3 models. This is is a white image generated internally by the game. This image can be used in lieu of $lightmap or an actual texture map if, for example, you wish for the vertex colors to come through unaltered.

== 6.1.2 Clampmap <texturepath> ==
Dictates that this stage should clamp texture coordinates instead of wrapping them. During a stretch function, the area, which the texture must cover during a wave cycle, enlarges and decreases. Instead of repeating a texture multiple times during enlargement (or seeing only a portion of the texture during shrinking) the texture dimensions increase or contract accordingly. This is only relevant when using something like deformTexCoordParms to stretch/compress texture coordinates for a specific special effect. Remember that the Quake III Arena engine normalizes all texture coordinates (regardless of actual texture size) into a scale of 0.0 to 1.0.

'''Proper Alignment:''' When using '''clampTexCoords''' be make sure the texture is properly aligned on the brush. The '''clampTexCoords''' function keeps the image from tiling. However, the editor doesn’t represent this properly and shows a tiled image. Therefore, what appears to be the correct position may be offset. This is very apparent on anything with a '''tcMod rotate''' and '''clampTexCoords''' function.

'''Avoiding Distortion:''' When seen at a given distance (which can vary, depending on hardware and the size of the texture), the compression phase of a stretch function will cause a “cross”-like visual artifact to form on the modified texture due to the way that textures are reduced. This occurs because the texture undergoing modification lacks sufficient “empty space” around the displayed (non-black) part of the texture (see figure 2a). To compensate for this, make the non-zero portion of the texture substantially smaller (50% of maximum stretched size -- see figure 2b) than the dimensions of the texture. Then, write a scaling function (tcScale) into the appropriate shader phase, to enlarge the image to the desired proportion.

The shaders for the bouncy pads (in the sfx.shader file) show the stretch function in use, including the scaling of the stretched texture:

'''Example: Using clampTexCoords to control a stretching texture'''

textures/sfx/metalbridge06_bounce

{

//q3map_surfacelight 2000

surfaceparm nodamage

q3map_lightimage textures/sfx/jumppadsmall.tga

q3map_surfacelight 400

{

map textures/sfx/metalbridge06_bounce.tga

rgbGen identity

}

{

map $lightmap

rgbGen identity

blendfunc gl_dst_color gl_zero

}

{

map textures/sfx/bouncepad01b_layer1.tga

blendfunc gl_one gl_one

rgbGen wave sin .5 .5 0 1.5

}

{

clampmap textures/sfx/jumppadsmall.tga

blendfunc gl_one gl_one

tcMod stretch sin 1.2 .8 0 1.5

rgbGen wave square .5 .5 .25 1.5

}

// END

}

== 6.1.3 [[AnimMap]] <frequency> <texture1> … <texture8> ==
The surfaces in the game can be animated by displaying a sequence of 1 to 8 frames (separate texture maps). These animations are affected by other keyword effects in the same and later shader stages.

'''<Frequency>:''' the number of times that the animation cycle will repeat within a one second time period. The larger the value, the more repeats within a second. Animations that should last for more than a second need to be expressed as decimal values.

'''<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.

'''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.

textures/sfx/flameanim_blue

{

// *************************************************

// * Blue Flame *

// * July 20, 1999 Surface Light 1800 *

// * Please Comment Changes *

// *************************************************

qer_editorimage textures/sfx/b_flame7.tga

q3map_lightimage textures/sfx/b_flame7.tga

surfaceparm trans

surfaceparm nomarks

surfaceparm nolightmap

cull none

q3map_surfacelight 1800

// texture changed to blue flame.... PAJ

{

animMap 10 textures/sfx/b_flame1.tga textures/sfx/b_flame2.tga textures/sfx/b_flame3.tga textures/sfx/b_flame4.tga textures/sfx/b_flame5.tga textures/sfx/b_flame6.tga textures/sfx/b_flame7.tga textures/sfx/b_flame8.tga

blendFunc GL_ONE GL_ONE

rgbGen wave inverseSawtooth 0 1 0 10

}

{

animMap 10 textures/sfx/b_flame2.tga textures/sfx/b_flame3.tga textures/sfx/b_flame4.tga textures/sfx/b_flame5.tga textures/sfx/b_flame6.tga textures/sfx/b_flame7.tga textures/sfx/b_flame8.tga textures/sfx/b_flame1.tga

blendFunc GL_ONE GL_ONE

rgbGen wave sawtooth 0 1 0 10

}

{

map textures/sfx/b_flameball.tga

blendFunc GL_ONE GL_ONE

rgbGen wave sin .6 .2 0 .6

}

}

= 6.2 Blend Functions =
Blend functions are the keyword commands that tell the ''Quake III Arena'' graphic engine’s renderer how graphic layers are to be mixed together.

== 6.2.1 Simplified blend functions: ==
The most common blend functions are set up here as simple commands, and should be used unless you really know what you are doing.

=== 6.2.1.1 blendfunc add ===
This is a shorthand command for '''blendfunc gl_one gl_one. ''' Effects like fire and energy are additive.''' '''

=== 6.2.1.2 blendfunc filter ===
This is a shorthand command that can be substituted for either '''blendfunc gl_dst_color gl_zero''' or '''blendfunc gl_zero gl_src_color'''. A filter will always result in darker pixels than what is behind it, but it can also remove color selectively. Lightmaps are filters.

=== 6.2.1.3 blendfunc blend ===
Shorthand for blendfunc gl_src_alpha gl_one_minus_src_alpha. This is conventional transparency, where part of the background is mixed with part of the texture.

== 6.2.2 Explicit blend functions: ==
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:

'''[Source * <srcBlend>] + [Destination * <dstBlend>]'''

'''Source''' is usually the RGB color data in a texture TGA file (remember it’s all numbers) modified by any rgbgen and alphagen. In the shader, the source is generally identified by command MAP, followed by the name of the image.

''' '''

'''Destination''' is the color data currently existing in the frame buffer.

Rather than think of the entire texture as a whole, it may be easier to think of the number values that correspond to a single pixel, because that is essentially what the computer is processing … one pixel of the bit map at a time.

The process for calculating the final look of a texture in place in the game world begins with the precalculated lightmap for the area where the texture will be located. This data is in the frame buffer. That is to say, it is the initial data in the '''Destination'''. In an unmanipulated texture (i.e.; one without a special shader script), color information from the texture is combined with the lightmap. In a shader-modified texture, the $lightmap stage must be present for the lightmap to be included in the calculation of the final texture appearance.

Each pass or “stage” of blending is combined (in a cumulative manner) with the color data passed onto it by the previous stage. How that data combines together depends on the values chosen for the Source Blends and Destination Blends at each stage. Remember it’s numbers that are being mathematically combined together that are ultimately interpreted as colors.

A general rule is that any '''Source Blend''' other than '''GL_ONE''' (or '''GL_SRC_ALPHA''' where the alpha channel is entirely white) will cause the Source to become darker.

== 6.2.3 Source Blend <srcBlend> ==
The following values are valid for the Source Blend part of the equation.

''' '''

'''GL_ONE''' This is the value 1. When multiplied by the '''Source''', the value stays the same the value of the color information does not change.

'''GL_ZERO''' This is the value 0. When multiplied by the '''Source''', all RGB data in the '''Source''' becomes Zero (essentially black).

'''GL_DST_COLOR''' This is the value of color data currently in the Destination (frame buffer). The value of that information depends on the information supplied by previous stages.

'''GL_ONE_MINUS_DST_COLOR ''' This is nearly the same as GL_DST_COLOR except that the value for each component color is inverted by subtracting it from one. (,i.e.; R = 1.0 – DST.R, G = 1.0 – DST.G, B = 1.0 – DST.B, etc.)

'''GL_SRC_ALPHA''' The TGA file being used for the '''Source''' data must have an alpha channel in addition to its RGB channels (for a total of four channels). The alpha channel is an 8-bit black and white only channel. An entirely white alpha channel will not darken the '''Source'''.

'''GL_ONE_MINUS_SRC_ALPHA ''' This is the same as GL_SRC_ALPHA except that the value in the alpha channel is inverted by subtracting it from one. (i.e.; A=1.0 – SRC.A)

== 6.2.4 Destination Blend <dstBlend> ==
The following values are valid for the Destination Blend part of the equation.

'''GL_ONE''' This is the value 1. When multiplied by the '''Destination''', the value stays the same the value of the color information does not change.

'''GL_ZERO''' This is the value 0. When multiplied by the '''Destination''', all RGB data in the '''Destination''' becomes Zero (essentially black).

'''GL_SRC_COLOR''' This is the value of color data currently in the '''Source''' (which is the texture being manipulated here).

'''GL_ONE_MINUS_SRC_COLOR ''' This is the value of color data currently in '''Source''', but subtracted from one (i.e.; inverted).

'''GL_SRC_ALPHA''' The TGA file being used for the '''Source''' data must have an alpha channel in addition to its RGB channels (four a total of four channels). The alpha channel is an 8-bit black and white only channel. An entirely white alpha channel will not darken the '''Source'''.

'''GL_ONE_MINUS_SRC_ALPHA ''' This is the same as GL_SRC_ALPHA except that the value in the alpha channel is inverted by subtracting it from one. (i.e.; A=1.0 – SRC.A).

''' '''

'''Doing the Math: The Final Result'''

The product of the '''Source''' side of the equation is added to the product of the '''Destination''' side of the equation. The sum is then placed into the frame buffer to become the '''Destination''' information for the next stage. Ultimately, the equation creates a modified color value that is used by other functions to define what happens in the texture when it is displayed in the game world.

== 6.2.5 Default Blend Function ==
''If no '''blendFunc''' is specified then no blending will take place.'' A warning is generated if any stage after the first stage does not have a '''blendFunc''' specified.

== 6.2.6 Technical Information/Limitations Regarding Blend Modes: ==
The Riva 128 graphics card supports ONLY the following blend modes:

GL_ONE, GL_ONE

GL_DST_COLOR, GL_ZERO

GL_ZERO, GL_SRC_COLOR

GL_SRC_ALPHA, GL_ONE_MINUS_SRC_ALPHA

GL_ONE_MINUS_SRC_ALPHA, GL_SRC_ALPHA

Cards running in 16 bit color cannot use any GL_DST_ALPHA blends.

= 6.3 rgbGen <func> =
There are two color sources for any given shader, the texture file and the vertex colors. Output at any given time will be equal to '''TEXTURE''' multiplied by '''VERTEXCOLOR'''. Most of the time VERTEXCOLOR will default to white (which is a normalized value of 1.0), so output will be TEXTURE (this usually lands in the '''Source''' side of the shader equation). Sometimes you do the opposite and use TEXTURE = WHITE, but this is only commonly used when doing specular lighting on entities (i.e.; shaders that level designers will probably never create

The most common reason to use rgbGen is to pulsate something. This means that the VERTEXCOLOR will oscillate between two values, and that value will be multiplied (darkening) the texture.

If no rgbGen is specified, either “identityLighting” or “identity” will be selected, depending on which blend modes are used.

Valid <func> parameters are '''wave, identity, identityLighting, entity, oneMinusEntity, fromVertex,''' and '''lightingDiffuse'''.

== 6.3.1 [[RgbGen]] identityLighting ==
Colors will be (1.0,1.0,1.0) if running without overbright bits (NT, linux, windowed modes), or (0.5, 0.5, 0.5) if running with overbright. Overbright allows a greater color range at the expense of a loss of precision. Additive and blended stages will get this by default.

== 6.3.2 rgbGen identity ==
Colors are assumed to be all white (1.0,1.0,1.0). All filters stages (lightmaps, etc) will get this by default.

== 6.3.3 rgbGen wave <func> <base> <amp> <phase> <freq> ==
Colors are generated using the specified waveform. An affected texture with become darker and lighter, but will not change hue. Hue stays constant. Note that the rgb values for color will not go below 0 (black) or above 1 (white). Valid waveforms are sin, triangle, square, sawtooth and inversesawtooth.

'''<func> Wave''' forms and their effects:

'''Sin:''' color flows smoothly through changes.

'''Triangle:''' color changes at a constant rate and spends no appreciable time at peaks and valleys.

'''Square:''' color alternates instantly between its peak and valley values.

'''Sawtooth:''' With a positive frequency value, the color changes at a constant rate to the peak then instantly drops to its valley value.

'''Inversesawtooth:''' An inverse sawtooth wave will reverse this, making the ascent immediate (like a square wave) and the decay fall off like a triangle wave.

'''<base>''' Baseline value. The initial RGB formula of a color (normalilzed.

'''<amp>''' Amplitude. This is the degree of change from the baseline value. In some cases you will want values outside the 0.0 to 1.0 range, but it will induce clamping (holding at the maximum or minimum value for a time period) instead of continuous change.

'''<phase>''' See the explanation for phase under the waveforms heading of Key Concepts.

'''<freq>''' Frequency. This is a value (NOT normalized) that indicates peaks per second.

== 6.3.4 [[RgbGen]] entity ==
Colors are grabbed from the entity’s '''modulate''' field. This is used for things like explosions.

'''Design Note''': This keyword would probably not be used by a level designer.

== 6.3.5 rgbGen oneMinusEntity ==
Colors are grabbed from 1.0 minus the entity’s modulate field.

'''Design Note''': This keyword would probably not be used by a level designer.

== 6.3.6 rgbGen Vertex ==
Colors are filled in directly by the data from the map or model files.

'''Design Note''': rgbGen vertex should be used when you want the RGB values to be computed

for a static model (i.e. mapobject) in the world using precomputed static

lighting from Q3BSP. This would be used on things like the gargoyles, the portal frame,

skulls, and other decorative MD3s put into the Quake III Arena world.

== 6.3.7 rgbGen oneMinusVertex ==
As rgbGen vertex, but inverted.

'''Design Note''': This keyword would probably not be used by a level designer

== 6.3.8 rgbGen lightingDiffuse ==
Colors are computed using a standard diffuse lighting equation. It uses the vertex normals to illuminate the object correctly.

'''Design Note:''' - rgbGen lightingDiffuse is used when you want the RGB values to be

computed for a dynamic model (i.e. non-map object) in the world using

regular in-game lighting. For example, you would specify on shaders for

items, characters, weapons, etc.

= 6.4 [[AlphaGen]] <func> =
The alpha channel can be specified like the rgb channels. If not specified, it defaults to 1.0.

== 6.4.1 [[AlphaGen]] portal ==
This rendering stage keyword is used in conjunction with the surface parameter keyword '''portal'''. The function accomplishes the “fade” that causes the scene in the portal to fade from view. Specifically, it means “Generate alpha values based on the distance from the viewer to the portal.” Use '''alphaGen''' portal on the last rendering pass.

= 6.5 tcGen <coordinate source> =
Specifies how texture coordinates are generated and where they come from. Valid functions are '''base''', '''lightmap''' and '''environment.'''

'''<base>''' = base texture coordinates from the original art.

'''<lightmap>''' = lightmap texture coordinates

'''<environment>''' = Make this object environment mapped.

== 6.5.1 tcGen vector (<sx> <sy> <sz>) (<tx> <ty> <tz>) ==
New texcoord generation by world projection. This allows you to project a

texture onto a surface in a fixed way, regardless of its orientation.

S coordinates correspond to the “x” coordinates on the texture itself.

T coordinates correspond to the “y” coordinates on the texture itself.

The measurements are in game units.

Example: tcGen vector (0.01 0 0) (0 0.01 0)

This would project a texture with a repeat every 100 units across the X/Y plane.

= 6.6 tcMod <func> <…> =
Specifies how texture coordinates are modified after they are generated. The valid functions for tcMod are '''rotate, scale, scroll, stretch and transform.''' '''Transform''' is a function generally reserved for use by programmers who suggest that designers leave it alone. When using multiple tcMod functions during a stage, place the '''scroll''' command last in order, because it performs a mod operation to save precision, and that can disturb other operations. Texture coordinates are modified in the order in which tcMods are specified. In other words, if you see:

'''tcMod scale 0.5 0.5'''

'''tcMod scroll 1 1'''

Then the texture coordinates will be '''scaled''' ''then'' '''scrolled.'''

== 6.6.1 tcMod rotate <degrees per per second> ==
This keyword causes the texture coordinates to rotate. The value is expressed in degrees rotated each second. A positive value means clockwise rotation. A negative value means counterclockwise rotation. For example “tcMod rotate 5” would rotate texture coordinates 5 degrees each second in a clockwise direction. The texture rotates around the center point of the texture map, so you are rotating a texture with a single repetition, be careful to center it on the brush (unless off-center rotation is desired).

== 6.6.2 tcMod scale <sScale> <tScale> ==
Resizes (enlarges or shrinks) the texture coordinates by multiplying them against the given factors of <sScale> and <tScale). The values “s” and “t” conform to the “x” and “y” values (respectively) as they are found in the original texture TGA. The values for '''sScale''' and '''tScale''' are NOT normalized. This means that a value greater than 1.0 will increase the size of the texture. A positive value less than one will reduce the texture to a fraction of its size and cause it to repeat within the same area as the original texture (Note: see '''clampTexCoords''' for ways to control this).;

'''Example:''' ''tcMod scale 0.5 2'' would cause the texture to repeat twice along its width, but expand to twice its height (in which case half of the texture would be seen in the same area as the original)

== 6.6.3 tcMod scroll <sSpeed> <tSpeed> ==
Scrolls the texture coordinates with the given speeds. ). The values “s” and “t” conform to the “x” and “y” values (respectively) as they are found in the original texture TGA, The scroll speed is measured in “textures” per second. A “texture” is the dimension of the texture being modified and includes any previous shader modifications to the original TGA). A negative s value would scroll the texture to the left. A negative t value would scroll the texture down.

Example: tcMod scroll 0.5 -0.5 moves the texture down and right (relative to the TGA files original coordinates) at the rate of a half texture each second of travel.

This should be the LAST tcMod in a stage. Otherwise there may be popping or snapping visual effects in some shaders.

== 6.6.4 tcMod stretch <func> <base> <amplitude> <phase> <frequency> ==
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

'''<base>:''' A base value of one is the original dimension of the texture when it reaches the stretch stage. Inserting other values positive or negative in this variable will produce unknown effects.

'''<amplitude>:''' This is the measurement of distance the texture will stretch from the base size. It is measured, like scroll, in textures. A value of 1 here will double the size of the texture at its peak.

'''<phase>:''' See the explanation for phase under the deform vertexes keyword.

'''<frequency>''': this is wave peaks per second.

'''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.

'''Triangle wave:''' The textures stretch at a constant rate and spend no appreciable time at the peak or valley points.

'''Square wave:''' The texture is shown at its peak for the duration of the frequency and then at its valley for the duration of the frequency.

'''Sawtooth:''' the texture stretches like a triangle wave until it reaches a peak, then instantly drops to the valley, as in a square wave.

'''Inversesawtooth''': this is the reverse of the sawtooth wave.

== 6.6.5 tcMod <transform> <m00> <m01> <m10> <m11> <t0> <t1> ==
Transforms each texture coordinate as follows:

S’ = s * m00 + t * m10 + t0

T’ = t * m01 + s * m11 + t1

This is for use by programmers.

== 6.6.6 tcMod turb <base> <amplitude> <phase> <freq> ==
Applies turbulence to the texture coordinate. Turbulence is a back and forth churning and swirling effect on the texture.

The parameters for this shader are defined as follows:

'''<base>''' Currently undefined.

'''<amplitude>''' This is essentially the intensity of the disturbance or twisting and squiggling of the texture.

''' '''

'''<phase>''' See the explanation for phase under the '''deform vertexes''' keyword.

'''<freq>''' Frequency. This value is expressed as repetitions or cycles of the wave per second. A value of one would cycle once per second. A value of 10 would cycle 10 times per second. A value of 0.1 would cycle once every 10 seconds.

= 6.7 depthFunc <func> =
This controls the depth comparison function used while rendering. The default is “lequal” (Less than or equal to) where any surface that is at the same depth or closer of an existing surface is drawn. This is used for textures with transparency or translucency. Under some circumstances you may wish to use “equal”, e.g. for lightmapped grates that are alpha tested (it is also used for mirrors).

= 6.8 depthWrite =
By default, writes to the depth buffer when depthFunc passes will happen for opaque surfaces and not for translucent surfaces. Blended surfaces can have the depth writes forced with this function.

= 6.9 Detail =
This feature was not used in Quake III Arena maps, but should still function.

Designates this stage as a detail texture stage, which means that if the c_var, r_detailtextures, is set to 0 then this stage will be ignored (detail will not be displayed). This keyword, by itself, does not affect rendering at all. If you do put in a detail texture, it has to conform to very specific rules. Specifically, the blendFunc:

'''blendFunc GL_DST_COLOR GL_SRC_COLOR'''

''' '''

This is also the simple blend function: '''blendfunc filter'''

And the average ''intensity'' of the detail texture itself must be around 127.

Detail is used to blend fine pixel detail back into a base texture whose scale has been increased significantly. When detail is written into a set of stage instructions, it allows the stage to be disabled by the c_var console command setting "r_detailtextures 0".

A texture whose scale has been increased beyond a 1:1 ratio tends not to have very high frequency content. In other words, one texel can cover a lot of real estate. Frequency is also known as “detail.” Lack of detail can appear acceptable if the player never has the opportunity to see the texture at close range. But seen close up, such textures look glaringly wrong within the sharp detail of the Quake III Arena environment. A detail texture solves this problem by taking a noisy "detail" pattern (a tiling texture that appears to have a great deal of surface roughness) and applying it to the base texture at a very densely packed scale (that is, reduced from its normal size). This is done programmatically in the shader, and does not require modification of the base texture. Note that if the detail texture is the same size and scale as the base texture that you may as well just add the detail directly to the base texture. The theory is that the detail texture's scale will be so high compared to the base texture (e.g.; 9 detail texels fitting into 1 base texel) that it is literally impossible to fit that detail into the base texture directly.

For this to work, the rules are as

follows:

A.) the lightmap must be rendered first. This is because the subsequent detail texture will be modifying the lightmap in the framebuffer directly;

B.) the detail texture must be rendered next since it modifies the lightmap in the framebuffer

C.) the base texture must be rendered last ;

D.) the detail texture MUST have a mean intensity around 127-129. If it does not then it will modify the displayed texture’s perceived brightness in the world

E.) the detail shader stage MUST have the "'''detail'''" keyword or it will not

be disabled if the user uses the "r_detailtextures 0" setting ;

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.;

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.

H.) detail textures add one pass of overdraw, so there is a definite performance hit .

I.) detail textures can be shared, so designers may wish to define only a very

small handful of detail textures for common surfaces such as rocks, etc.

An example (non-existent) detail shader is as follows:

'''Example: Texture with Detail'''

textures/bwhtest/foo

{

// draw the lightmap first

{

map $lightmap

rgbGen identity

}

// modify the lightmap in the framebuffer by

// a highly compressed detail texture

{

map textures/details/detail01.tga

blendFunc GL_DST_COLOR GL_SRC_COLOR

// YOU MUST USE THIS!!

detail

// for the detail to be disabled, this must be present

tcMod scale 9.1 9.2

}

// now slap on the base texture

{

map textures/castle/blocks11b.tga

blendFunc filter

}

}

= 6.10 alphaFunc <func> =
Determines the alpha test function used when rendering this map. Valid values are GT0, LT128, and GE128. These correspond to “GREATER THAN 0”, “LESS THAN 128”, and “GREATER THAN OR EQUAL TO 128”. This function is used when determining if a pixel should be written to the framebuffer. For example, if GT0 is specified, the only the portions of the texture map with corresponding alpha values greater than zero will be written to the framebuffer. By default alpha testing is disabled.

Both alpha testing and normal alpha blending can be used to get textures that have see-through parts. The difference is that alphaFunc is an all-or-nothing test, while blending smoothly blends between opaque and translucent at pixel edges. Alpha test can also be used with '''depthwrite''', allowing other effects to be conditionally layered on top of just the opaque pixels by setting '''depthFunc''' to equal.

7 Notes on Alpha Channels
To use some blend modes of alphaFunc, you must add an alpha channel to your texture files. Photoshop can do this. Paintshop Pro has the ability to make an alpha channel cannot work directly in to it. In Photoshop you want to set the type to Mask. Black has a value of 255. White has a value of 0. The darkness of a pixel’s alpha value determines the transparency of the corresponding RGB value in the game world. Darker = more transparent.

Care must be taken when reworking textures with alpha channels. Textures without alpha channels are saved as 24 bit images while textures with alpha channels are saved as 32 bit. If you save them out as 24 bit, the alpha channel is erased. Note: Adobe Photoshop will prompt you to save as 32, 24 or 16 bit. Choose wisely. If you save a texture as 32 bit and you don’t actually have anything in the alpha channel, Quake III Arena may still be forced to use a lower quality texture format (when in 16 bit rendering) than if you had saved it as 24 bit.

To create a texture that has “open” areas, make those areas black in the alpha channel and make white the areas that are to be opaque. Using gray shades can create varying degrees of opacity/transparency.

Example: An opaque texture with see-through holes knocked in it.

textures/base_floor/pjgrate1

{

surfaceparm metalsteps

cull none

// A GRATE OR GRILL THAT CAN BE SEEN FROM BOTH SIDES

{

map textures/base_floor/pjgrate1.tga

blendFunc GL_SRC_ALPHA GL_ONE_MINUS_SRC_ALPHA

alphaFunc GT0

depthWrite

rgbGen identity

}

{

map $lightmap

rgbGen identity

blendFunc GL_DST_COLOR GL_ZERO

depthFunc equal

}

}

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:

attachment:image003.jpg
attachment:image002.png

Figure 1

Start with a TGA file image. In this case, a pentagram on a plain white field (figure 1A). The color of the field surrrounding the image to be merged is not relevant to this process (although having a hard-edged break between the image to be isolated and the field makes the mask making process easier). Make an alpha channel. The area of the image to be merged with another image is masked off in white. The area to be masked out (not used) is pure black (figure 1B). The image to be merged into is greenfloor.tga (figure 1C).

Make a '''qer_editorimage''' of greenfloor.tga. This is placed in the frame buffer as the map image for the texture. By using GL_SRC_ALPHA as the source part of the blend equation, the shader adds in only the non-black parts of the pentagram. Using GL_MINUS_ONE_SRC_ALPHA, the shader inverts the pentagram’s alpha channel and adds in only the non-black parts of the green floor.

In a like manner, the alpha channel can be used to blend the textures more evenly. A simple experiment involves using a linear gradiant in the alpha channel (white to black) and merging two textures so they appear to cross fade into each other.

A more complicated experiment would be to take the pentagram in the first example and give it an aliased edge so that the pentagram appeared to fade or blend into the floor.

8 Troubleshooting Shaders

If a shader is not working, look first for syntax errors.

Are the brackets correctly set?

Do you have too many parameter values on a line?

Are you using a word in a parameter that wants a numerical value?

Are you using a numerical value in a parameter that wants a word?

Are the path names to your textures correct?

Are your texture names correct? There is a chance that the texture name is too long or too complex. Try renaming a texture with a shorter, simpler name.

9 Creating New Textures
If you are familiar with the required tools, creating new assets for use in Quake III Arena is not particularly difficult. As a general rule, you should create new directories for each map with names different from the names used by id. If you are making a map that will be called “H4x0r_D00M”, every directory containing new assets for that map should be titled H4x0r_D00M. This is to try and avoid asset directories overwriting each other as the editor and the game load in assets.

= 9.1 Tools Needed =
Any combination of graphic programs and plug-ins that can output a 24 bit MS windows compatible Targa (.tga) or JPEG (.jpg) graphic file. If you plan to make textures that will have an alpha channel component (a 4th 8-bit greyscale channel that is used by the shaders to further manipulate the art), you must have a program that can create 32-bit art with that fourth channel.

Adobe Photoshop has the ability to easily create alpha channels. Paint Shop Pro from JASC (v5.0+) can also make an alpha channel by creating a mask and naming it “alpha”.

Generally speaking, regardless of the program used, we found it best to do most of the art manipulation of the alpha channel in a separate layer or file and then paste it into the alpha channel before saving.

= 9.2 Setting up Files =
The editor and the game program look for assets to be located along the paths set up in your project file. Start by creating a directory for you new textures by creating file folders to make a directory path as follows: quake3\baseq3\textures\[mymapname]

The installation of [[Q3Radiant]] will create a text document called “shaderlist.txt” in the following path:

quake3\baseq3\scripts\shaderlist.txt

[[Q3Radiant]] will use the contents of this script to grab your new textures for inclusion in the game. The contents of shaderlist.txt document will contain a listing of all the shader documents that were used by id Software to create Quake III Arena.

Since you will obviously want to create your own shaders, you need to put them in separate folders and create a new shader script for them.

If you plan to work on several maps at once and want to distinguish between textures used in each map, simply add additional map names here. For map and mod makers, we STRONGLY recommend that any new shader scripts created use the name of the map or mod in the shader file name. We know we can’t avoid every incident of files overwriting each other, but we certainly can advise you how to try.

Now, in the scripts directory that you just created, create another text file and call it:

[mymapname].shader

This file will contain the shader scripts you write to modify a particular texture.

= 9.3 Rules and Guidelines =
== 9.3.1 Rules ==
Follow these rules when creating textures for the Quake III Arena engine:

· Save your textures into your new [map name] directories.

· Don’t use the same names that id used for textures. It will cause problems.

· For best quality, save textures without an alpha channel as 24 bit TARGA files. Using JPEG files can save memory space, but at the risk of losing detail and depth in the texture. JPEG files cannot be used for textures requiring an alpha channel.

· Textures containing an alpha channel must be saved as 32 bit TARGA files.

· If a new texture requires no further manipulation, it does not need a shader script.

· Size textures in powers of 2. Example: 8x8, 16x16, 32x32, 64x64 pixels and so on.

· Textures don’t need to be square. A 32x256 pixel texture is perfectly acceptable.

== 9.3.2 Guidelines ==
The following are some things the id designers learned about textures.

· Create textures in “suites” built around one or two large textures with a number of much smaller supporting detail or accent textures.

· Very large textures are possible, but some video cards compress textures larger than 256x256 pixels.

· Textures are grouped alphabetically by name in the texture display window, so you may want to give suites of textures similar names.

· Use the shader function qe3_editorimage to conserve memory when making multiple versions of a single texture (as in the case of a glowing texture with several light values).

· Unless you are creating special effects or textures designed to draw the player’s eye to a specific spot, muted, middle value colors work best with the game engine.

· Extremely busy (a lot of fussy detail) textures can break up or form visually unpleasant patterns when seen at distances.

= 9.4 Making the .pk3 File =
When you go to distribute your creation to the gaming world, you need to put your newly created map, textures, bot area files, and shader documents into an archive format called a “pk3” file. You do not need to include the shaderlist.txt file, since that is only used by the editor. You will need to keep the paths to the various assets the same. So your paths should be something like this:

Textures: baseq3/textures/[mymapnamefolder]

Bsp & aas: baseq3/maps/mymapname.bsp , mymapname.aas

Shader scripts: baseq3/scripts/mymapname.shader

You need to use an archiving program call Winzip to make the pk3 file. Get Winzip from http://www.winzip.com/winzip/winzip.htm

Make a zip archive called mymapname.zip

Zip all the required assets into a zip archive file (Quake III Arena ''DOES'' support compressed pk3 files).

Rename the zip archive to mymapname.pk3

Put it where the Quake III Arena community can find it.

OldSiteResourcesQuake3ShaderManual

2006-06-09T06:39:20Z

VitoMiliano:

__NOTOC__
'''NOTE:''' The Quake 3 Arena Shader Manual is also
available for download in .PDF format at the following
link: [http://dl.fileplanet.com/dl/dl.asp?q2pmp/Q3AShader_manual_pdf.zip Quake 3 Arena Shader Manual in .PDF format] Quake III Arena

Shader Manual

Revision #12

By Paul Jaquays and Brian Hook

(with additional material by John Carmack, Christian Antkow, Kevin Cloud, & Adrian Carmack)

1 Preface: Making Your Own Shaders
The Manual for the [[Q3Radiant]] editor program contains a section called '''''Creating New Assets''''' that has the necessary information for setting up the files to create your own custom Quake III Arena shaders. It is recommended that you study the scripts in this document and in the individual shader scripts. Pay careful attention to syntax and punctuation. This is where you are most likely to make mistakes.

2 Introduction
The graphic engine for ''Quake III Arena'' has taken a step forward by putting much more direct control over the surface qualities of textures into the hands of designers and artists. In writing this manual, we have tried to define the concepts and tools that are used to modify textures in a way that, it is hoped, will be graspable by users who already have basic knowledge of computer graphics but are not necessarily computer programmers. It is not a tutorial, nor was it intended to be one.

= 2.1 What is a Shader? =
Shaders are short text scripts that define the properties of a surface as it appears and functions in a game world (or compatible editing tool). By convention, the documents that contain these scripts usually has the same name as the texture set which contains the textures being modified (e.g; base, hell, castle, etc,). Several specific script documents have also been created to handle special cases, like liquids, sky and special effects.

For ''Quake III Arena,'' Shader scripts are located in quake3/baseq3/scripts.

A ''Quake III Arena'' shader file consists of a series of surface attribute and rendering instructions formatted within braces (“{“ and “}”). Below you can see a simple example of syntax and format for a single process, including the Q3MAP keywords or “Surface Parameters”, which follow the first bracket and a single bracketed “stage”:

textures/liquids/lava

{

deformVertexes wave sin 0 3 0 0.1

tessSize 64

{

map textures/common/lava.tga

}

}

= 2.2 Shader Name & File Conventions =
The first line is the shader name. Shader names can be up to 63 characters long. The names are often a mirror of a pathname to a .tga file without the extension or basedir (/quake3/baseq3 in our case), but they do not need to be.

Shaders that are only going to be referenced by the game code, not modeling tools, often are just a single world, like “projectionShadow” or “viewBlood”.

Shaders that are used on characters or other polygon models need to mirror a .tga file, which allows the modelers to build with normal textures, then have the special effects show up when the model is loaded into the game.

Shaders that are placed on surfaces in the map editor commonly mirror a .tga file, but the “qer_editorimage” shader parameter can force the editor to use an arbitrary image for display.

Shader pathnames have a case sensitivity issue – on windows, they ''aren’t'' case sensitive, but on unix they ''are''. Try to always use lowercase for filenames, and always use forward slashes “/” for directory separators.

= 2.3 Shader Types =
The keywords that affect shaders are divided into two classes. The first class of keywords are global parameters. Some global parameters ( '''“surfaceparms.”''' And all '''“q3map_” keywords''') are processed by Q3MAP, and change physical attributes of the surface that uses the shader. These attributes can affect the player. To see changes in these parameters one must re-bsp the map.

The remaining global keywords, and all Stage Specific Keywords are processed by the renderer. They are appearance changes only and have no effect on game play or game mechanics. Changes to any of these attributes will take effect as soon as the game goes to another level or vid_restarts (type command '''vid_restart''' in the game console).

Shader keywords are ''not'' case sensitive.

'''IMPORTANT NOTE:''' some of the shader commands may be order dependent, so it’s good practice to place all global shader commands (keywords defined in this section) at the very beginning of the shader and to place shader stages at the end (see various examples).

= 2.4 Key Concepts =
Ideally, a designer or artist who is manipulating textures with shader files has a basic understanding of wave forms and knows about mixing colored light (high school physics sort of stuff). If not, there are some concepts you need to have a grasp on to make shaders work for you.

== 2.4.1 Surface Effects vs. Content Effects vs. Deformation Effects ==
Shaders not only modify the visible aspect of textures on a geometry brush, curve, patch or mesh model, but they can also have an effect on both the content, “shape,” and apparent movement of those things. A surface effect does nothing to modify the shape or content of the brush. Surface effects include glows, transparencies and rgb (red, green, blue) value changes. Content shaders affect the way the brush operates in the game world. Examples include water, fog, nonsolid, and structural. Deformation effects change the actual shape of the affected brush or curve, and may make it appear to move.

== 2.4.2 Power Has a Price ==
The shader script gives the designer, artist and programmer a great deal of easily accessible power over the appearance of and potential special effects that may be applied to surfaces in the game world. But it is power that comes with a price tag attached, and the cost is measured in performance speed. Each shader phase that affects the appearance of a texture causes the ''Q3:A'' engine to make another processing pass and redraw the world. Think of it as if you were adding all the shader-affected triangles to the total r_speed count for each stage in the shader script. A shader-manipulated texture that is seen through another shader manipulated texture (e.g.; a light in fog) has the effect of ''adding'' the total number of passes together for the affected triangles. A light that required two passes seen through a fog that requires one pass will be treated as having to redraw that part of the world three times.

== 2.4.3 RGB Color ==
RGB means “Red, Green, Blue.” Mixing red, green and blue light in differing intensities creates the colors in computers and television monitors. This is called ''additive color'' (as opposed to the mixing of pigments in paint or colored ink in the printing process, which is subtractive color). In ''Quake III Arena'' and most higher-end computer art programs (and the color selector in Windows), the intensities of the individual Red, Green and Blue components are expressed as number values. When mixed together on a screen, number values of equal intensity in each component color create a completely neutral (gray) color. The lower the number value (towards 0), the darker the shade. The higher the value, the lighter the shade or the more saturated the color until it reaches a maximum value of 255 (in the art programs). All colors possible on the computer can be expressed as a formula of three numbers. The value for complete black is 0 0 0. The value for complete white is 255 255 255. However, the ''Quake III Arena'' graphics engine requires that the color range be “normalized” into a range between 0.0 and 1.0.

== 2.4.4 Normalization: a Scale of 0 to 1 ==
The mathematics in ''Quake III Arena'' use a scale of 0.0 to 1.0 instead of 0 to 255. Most computer art programs that can express RGB values as numbers use the 0 to 255 scale. To convert numbers, divide each of the art program’s values for the component colors by 255. The resulting three values are your ''Quake III Arena'' formula for that color component. The same holds true for texture coordinates.

== 2.4.5 Texture Sizes ==
TGA texture files are measured in pixels (picture elements). Textures are measured in powers of 2, with 16 x16 pixels being the smallest (typically) texture in use. Most will be larger. Textures need not be square, so long as both dimensions are powers of 2. Examples include: 32x256, 16x32, 128x16.

== 2.4.6 Color Math ==
In ''Quake III Arena'' , colors are changed by mathematical equations worked on the textures by way of the scripts or “programlets” in the shader file. An equation that adds to or multiplies the number values in a texture causes it to become darker. Equations that subtract from or modulate number values in a texture cause it to become lighter. Either equation can change the hue and saturation of a color.

== 2.4.7 Measurements ==
The measurements used in the shaders are in either game units, color units, or texture units.

· '''Game unit:''' A game unit is used by deformations to specify sizes relative to the world. Game units are the same scale we have had since way back in the ''Wolfenstein'' days – 8 units equals one foot. The default texture scale used by the [[Q3Radiant]] map editor results in two texels for each game unit, but that can be freely changed.

· '''Color units''': Colors scale the values generated by the texture units to produce lighting effects. A value of 0.0 will be completely black, and a value of 1.0 will leave the texture unchanged. Colors are sometimes specified with a single value to be used across all red, green, and blue channels, or sometimes as separate values for each channel.

· '''Texture units:''' This is the normalized (see above) dimensions of the original texture image (or a previously modified texture at a given stage in the shader pipeline). A full texture, regardless of its original size in texels, has a normalized measurement of 1.0 x 1.0. For normal repeating textures, it is possible to have value greater than 1.0 or less than 0.0, resulting in repeating of the texture. The coordinates are usually assigned by the level editor or modeling tools, but you still need to be aware of this for scrolling or turbulent movement of the texture at runtime.

== 2.4.8 Waveform Functions ==
Many of the shader functions use waveforms to modulate measurements over time. Where appropriate, additional information is provided with wave modulated keyword functions to describe the effect of a particular waveform on that process. Currently there are five waveforms in use in ''Q3A'' shaders:

'''Sin''': Sin stands for sine wave, a regular smoothly flowing wave ranging from –1 to 1.

'''Triangle:''' Triangle is a wave with a sharp ascent and a sharp decay, ranging from 0 to 1. It will make a choppy looking wave forms.

'''Square''': A square wave simply switches from –1 to 1 with no in-between.

'''Sawtooth:''' In the sawtooth wave, the ascent is like a triangle wave from 0 to 1, but the decay cuts off sharply back to 0.

'''Inversesawtooth:''' This is the reverse of the sawtooth … instant ascent to the peak value (1), then a triangle wave descent to the valley value (0). The phase on this goes from 1.0 to 0.0 instead of 0.0 to 1.0. This wave is particularly useful for additive cross-fades.

'''Waveforms all have the following properties''':

'''<base>''' Where the wave form begins. Amplitude is measured from this base value.

'''<amplitude>''' This is the height of the wave created, measured from the base'''.''' You will probably need to test and tweak this value to get it correct for each new shader stage. The greater the amplitude, the higher the wave peaks and the deeper the valleys.

''' '''

'''<phase>''' This is a normalized value between 0.0 and 1.0. Changing phase to a non-zero value affects the point on the wave at which the wave form initially begins to be plotted. Example: In Sin or Triangle wave, a phase of 0.25 means it begins one fourth (25%) of the way along the curve, or more simply put, it begins at the peak of the wave. A phase of 0.5 would begin at the point the wave re-crosses the base line. A phase of 0.75 would be at the lowest point of the valley. If only one wave form is being used in a shader, a phase shift will probably not be noticed and phase should have a value of zero (0). However, including two or more stages of the same process in a single shader, but with the phases shifted can be used to create interesting visual effects. Example: using rgbGen in two stages with different colors and a 0.5 difference in phase would cause the manipulated texture to modulate between two distinct colors. Phase changes can also be used when you have two uses of the same effect near each other, and you don’t want them to be synchronized. You would write a separate shader for each, changing only the phase value.

'''<freq>''' Frequency. This value is expressed as repetitions or cycles of the wave per second. A value of 1 would cycle once per second. A value of 10 would cycle 10 times per second. A value of 0.1 would cycle once every 10 seconds.

3 General Shader Keywords
'''IMPORTANT NOTE:''' Once again, be aware that some of the shader commands may be order dependent, so it’s good practice to place all global shader commands (keywords defined in this section) at the very beginning of the shader and to place shader stages at the end (see various examples).

These Keywords are global to a shader and affect all stages. They are also ignored by Q3MAP.

= 3.1 skyParms <farbox> <cloudheight> <nearbox> =
Specifies how to use the surface as a sky, including an optional far box (stars, moon, etc), optional cloud layers with any shader attributes, and an optional near box (mountains in front of the clouds, etc).

'''<Farbox>''' Specifies a set of files to use as an environment box behind all cloud layers. Specify “-“ for no farbox, or a file base name. A base name of “env/test” would look for files “env/test_rt.tga”, “env/test_lf.tga”, “env/test_ft.tga”, “env/test_bk.tga”, “env/test_up.tga”, “env/test_dn.tga” to use as the right / left / front / back / up / down sides.

'''<cloudheight>''' controls apparent curvature of the cloud layers – lower numbers mean more curvature (and thus more distortion at the horizons). Higher height values create “flatter” skies with less horizon distortion. Think of height as the radius of a sphere on which the clouds are mapped. Good ranges are 64 to 256. The default value is 128.

'''<nearbox>''' Specified as farbox, to be alpha blended on top of the clouds. This has not been tested in a long time, so it probably doesn’t actually work. Set to “-“ to ignore.

Design Notes:

· If you are making a map where the sky is seen by looking up most of the time, use a lower cloudheight value. Under those circumstances the tighter curve looks more dynamic. If you are making a map where the sky is seen by looking out windows most of the time or has a map area that is open to the sky on one or more sides, use a higher height to make the clouds seem more natural.

· It is possible to create a sky with up to 8 cloud layers, but that also means 8 processing passes and a potentially large processing hit.

· Be aware that the skybox does not wrap around the entire world. The “floor” or bottom face of the skybox is not drawn by the game. If a player in the game can see that face, they will see the “hall of mirrors” effect.

'''Example: Sky script'''

textures/skies/xtoxicsky_dm9

{

qer_editorimage textures/skies/toxicsky.tga

surfaceparm noimpact

surfaceparm nolightmap

q3map_globaltexture

q3map_lightsubdivide 256

q3map_surfacelight 400

surfaceparm sky

q3map_sun 1 1 0.5 150 30 60

skyparms full 512 -

{

map textures/skies/inteldimclouds.tga

tcMod scroll 0.1 0.1

tcMod scale 3 2

}

{

map textures/skies/intelredclouds.tga

blendFunc add

tcMod scroll 0.05 0.05

tcMod scale 3 3

}

}

= 3.2 cull <side> =
Every surface of a polygon has two sides, a front and a back. Typically, we only see the front or “out” side. For example, a solid block you only show the front side. In many applications we see both. For example, in water, you can see both front and a back. The same is true for things like grates and screens.

To “cull” means to remove. The value parameter determines the type of face culling to apply. The default value is cull ''front'' if this keyword is not specified. However for items that should be inverted then the value ''back'' should be used. To disable culling, the value ''disable'' or ''none'' should be used. Only one cull instruction can be set for the shader.

== 3.2.1 cull front ==
The front or “outside” of the polygon is not drawn in the world. This is the default value. It is used if the keyword “'''cull'''” appears in the content instructions without a '''<side>''' value or if the keyword cull does not appear at all in the shader.

== 3.2.2 cull back ==
Cull back removes the back or “inside” of a polygon from being drawn in the world.

== 3.2.3 cull disable, cull none ==
Neither side of the polygon is removed. Both sides are drawn in the game. Very useful for making panels or barriers that have no depth, such as grates, screens, metal wire fences and so on and for liquid volumes that the player can see from within. Also used for energy fields, sprites, and weapon effects (e.g.; plasma).

Design Notes: For things like grates and screens, put the texture with the cull none property on one face only. On the other faces, use a non-drawing texture.

= 3.3 deformVertexes =
This function performs a general deformation on the surface’s vertexes, changing the actual shape of the surface before drawing the shader passes. You can stack multiple deformVertexes commands to modify positions in more complex ways, making an object move in two dimensions, for instance.

== 3.3.1 deformVertexes wave <div> <func> <base> <amplitude> <phase> <freq> ==
Designed for water surfaces, modifying the values differently at each point. It accepts the standard wave functions of the type '''sin''', '''triangle''', '''square, sawtooth''' or '''inversesawtooth'''. The “div” parameter is used to control the wave “spread” – a value equal to the tessSize of the surface is a good default value (tessSize is subdivision size, in game units, used for the shader when seen in the game world) .

== 3.3.2 deformVertexes normal <div> <func> <base> <amplitude ~0.1-~0.5> <frequency ~1.0-~4.0> ==
This deformation affects the normals of a vertex without actually moving it, which will effect later shader options like lighting and especially environment mapping. If the shader stages don’t use normals in any of their calculations, there will be no visible effect.

Design Notes: Putting values of 0.1 t o 0.5 in Amplitude and 1.0 to 4.0 in the Frequency can produce some satisfying results. Some things that have been done with it: A small fluttering bat, falling leaves, rain, flags.

== 3.3.3 deformVertexes bulge <bulgeWidth> <bulgeHeight> <bulgeSpeed> ==
This forces a bulge to move along the given '''s''' and '''t''' directions. Designed for use on curved pipes.

'''Specific parameter definitions for deform keywords:'''

'''<div> ''' This is roughly defined as the size of the waves that occur. It is measured in game units. Smaller values create a greater density of smaller wave forms occurring in a given area. Larger values create a lesser density of waves, or otherwise put, the appearance of larger waves. To look correct this value should closely correspond to the value (in pixels) set for tessSize (tessellation size) of the texture. A value of 100.0 is a good default value (which means your tessSize should be close to that for things to look “wavelike”).

''' '''

'''<func>''' This is the type of wave form being created. Sin stands for sine wave, a regular smoothly flowing wave. Triangle is a wave with a sharp ascent and a sharp decay. It will make a choppy looking wave forms. A square wave is simply on or off for the period of the frequency with no in between. The sawtooth wave has the ascent of a triangle wave, but has the decay cut off sharply like a square wave. An inversesawtooth wave reverses this.

'''<base>''' This is the distance, in game units that the apparent surface of the texture is displaced from the actual surface of the brush as placed in the editor. A positive value appears above the brush surface. A negative value appears below the brush surface. An example of this is the Quad effect, which essentially is a shell with a positive base value to stand it away from the model surface and a 0 (zero) value for amplitude.

'''<amplitude>''' The distance that the deformation moves away from the base value. See Wave Forms in the introduction for a description of amplitude.

'''<phase>''' See Wave Forms in the introduction for a description of phase)

'''<frequency>''' See Wave Forms in the introduction for a description of frequency)

Design Note: The div and amplitude parameters, when used in conjunction with liquid volumes like water should take into consideration how much the water will be moving. A large ocean area would have have massive swells (big div values) that rose and fell dramatically (big amplitude values). While a small, quiet pool may move very little.

== 3.3.4 deformVertexes move <x> <y> <z> <func> <base> <amplitude> <phase> <freq> ==
This keyword is used to make a brush, curve patch or md3 model appear to move together as a unit. The <x> <y> and <z> values are the distance and direction in game units the object appears to move relative to it’s point of origin in the map.

The <func> <base> <amplitude> <phase> and <freq> values are the same as found in other wave form manipulations.

The product of the function modifies the values x, y, and z. Therefore, if you have an amplitude of 5 and an x value of 2, the object will travel 10 units from its point of origin along the x axis. This results in a total of 20 units of motion along the x axis, since the amplitude is the variation both above and below the base.

It must be noted that an object made with this shader does not actually change position, it only appears to.

'''Design Note:''' If an object is made up of surfaces with different shaders, all must have matching deformVertexes move values or the object will appear to tear itself apart.

== 3.3.5 [[DeformVertexes]] autosprite ==
This function can be used to make any given triangle quad (pair of triangles that form a square rectangle) automatically behave like a sprite without having to make it a separate entity. This means that the “sprite” on which the texture is placed will rotate to always appear at right angles to the player’s view as a sprite would. Any four-sided brush side, flat patch, or pair of triangles in an .md3 model can have the '''autosprite''' effect on it. '''The brush face containing a texture with this shader keyword must be square.'''

'''Design Note''': This is best used on objects that would appear the same regardless of viewing angle. An example might be a glowing light flare.

== 3.3.6 [[DeformVertexes]] autosprite2 ==
Is a slightly modified “sprite” that only rotates around the middle of its longest axis. This allows you to make a pillar of fire that you can walk around, or an energy beam stretched across the room.

= 3.4 fogparms <red value> <green value> <blue value> <distance to Opaque> =
Note: you must also specify “surfaceparm fog” to cause q3map to identify the surfaces inside the volume. Fogparms only describes how to render the fog on the surfaces.

'''<red value> <green value> <blue value>''' These are normalized values. A good computer art program should give you the RGB values for a color. To obtain the values that define fog color for Quake III Arena , divide the desired color’s Red, Green and Blue values by 255 to obtain three normalized numbers within the 0.0 to 1.0 range.

'''<distance to opaque>''' This is the distance, in game units, until the fog becomes totally opaque, as measured from the point of view of the observer. By making the height of the fog brush shorter than the distance to opaque , the apparent density of the fog can be reduced (because it never reaches the depth at which full opacity occurs)..

· The fog volume can only have one surface visible (from outside the fog).

· Fog must be made of one brush. It cannot be made of adjacent brushes.

· Fog brushes must be axial. This means that only square or rectangular brushes may contain fog, and those must have their edges drawn along the axes of the map grid (all 90 degree angles).

·

'''Design Notes: '''

· If a water texture contains a fog parameter, it must be treated as if it were a fog texture when in use.

· If a room is to be filled completely with a fog volume, it can only be entered through one surface (and still have the fog function correctly).

· Additional shader passes may be placed on a fog brush, as with other brushes.

= 3.5 nopicmip =
This causes the texture to ignore user-set values for the '''r_picmip''' cvar command. The image will always be high resolution. Example: Used to keep images and text in the heads up display from blurring when user optimizes the game graphics.

= 3.6 nomipmap: =
This implies nopicmip, but also prevents the generation of any lower resolution mipmaps for use by the 3d card. This will cause the texture to alias when it gets smaller, but there are some cases where you would rather have this than a blurry image. Sometimes thin slivers of triangles force things to very low mipmap levels, which leave a few constant pixels on otherwise scrolling special effects.

= 3.7 polygonOffset =
Surfaces rendered with the '''polygonOffset''' keyword are rendered slightly off the polygon’s surface. This is typically used for wall markings and “decals.” The distance between the offset and the polygon is fixed. It is not a variable in Quake III Arena.

= 3.8 portal =
Specifies that this texture is the surface for a portal or mirror. In the game map, a portal entity must be placed directly in front of the texture (within 64 game units). All this does is set “sort portal”, so it isn’t needed if you specify that explicitly.

= 3.9 sort <value> =
Use this keyword to fine-tune the depth sorting of shaders as they are compared against other shaders in the game world. The basic concept is that if there is a question or a problem with shaders drawing in the wrong order against each other, this allows the designer to create a hierarchy of which shader draws in what order.

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.

The value here can be either a numerical value or one of the keywords in the following list (listed in order of ascending priority):

'''portal (1):''' This surface is a portal, it draws over every other shader seen inside the portal, but before anything in the main view.

'''Sky (2):''' 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.

'''Opaque (3):''' This surface is opaque (rarely needed since this is the default with no blendfunc)

'''Banner (6) :''' Transparent, but very close to walls.

'''Underwater (8):''' Draw behind normal transparent surfaces.

'''Additive (9):''' normal transparent surface (default for shaders with blendfuncs)

'''nearest (16):''' this shader should always sort closest to the viewer, e.g. muzzle flashes and blend blobs

4 Q3MAP Specific Shader Keywords
These keywords change the physical nature of the textures and the brushes that are marked with them. Changing any of these values will require the map to be re-compiled. These are global and affect the entire shader.

= 4.1 tessSize <amount> =
For consistency’s sake, this really should have been called q3map_tessSize. But it wasn’t. The tessSize shader controls the tessellation size (how finely a surface is chopped up in to triangles), in game units, of the surface. This is only applicable to solid brushes, not curves, and is generally only used on surfaces that are flagged with the '''deformVertexes''' keyword. Abuse of this can create a huge number of triangles. This happens during q3map processing, so maps must be reprocessed for changes to take effect.

'''Design Note:''' It can also be used on tesselating surfaces to make sure that tesselations are large, and thus, less costly in terms of triangles created.

= 4.2 q3map_backshader <shadername> =
This allows a brush to use a different shader when you are inside it looking out. By way of example, this would allow a water brush (or other) surfaces to have a different sort order (see '''''sort''''' above) or appearance when seen from the inside.

= 4.3 q3map_globaltexture =
Use this shader in the global keyword commands whenever the '''tcMod scale''' function is used in one of the later render stages. Many problems with getting shader effects to work across multiple adjacent brushes are a result of the way q3map optimizes texture precision. This option resolves that, but at the expense of some precision of the textures when they are far away from the origin of the map.

= 4.4 q3map_sun <red> <green> <blue> <intensity> <degrees> <elevation> =
This keyword in a sky shader will create the illusion of light cast into a map by a single, infinitely distance light source (sun, moon, hellish fire, etc.). This is only processed during the lighting phase of q3map.

'''<red> <green> <blue>''' Color is described by three normalized rgb values. Color will be normalized to a 0.0 to 1.0 range, so it doesn’t matter what range you use.

'''<intensity>''' is the brightness of the generated light. A value of 100 is a fairly bright sun. The intensity of the light falls off with angle but not distance.

'''<degrees>''' is the angle relative to the directions on the map file. A setting of 0 degrees equals east. 90 is north, 180 is west and 270 is south.

'''<elevation>''' is the distance, measured in degrees from the horizon (z value of zero in the map file). An elevation of 0 is sunrise/sunset. An elevation of 90 is noon

'''DESIGN NOTE: ''' Sky shaders should probably still have a '''q3map_surfacelight''' value. The “sun” gives a strong directional light, but doesn’t necessarily give the fill light needed to soften and illuminate shadows. Skies with clouds should probably have a weaker '''q3map_sun''' value and a higher '''q3map_surfacelight''' value. Heavy clouds diffuse light and weaken shadows. The opposite is true of a cloudless or nearly cloudless sky. In such cases, the “sun” or “moon” will cast stronger, shadows that have a greater degree of contrast.

'''Design Trick:''' Not certain what color formula you want to use for the sun’s light? Try this. Create a light entity. Use the [[Q3Radiant]] editor’s color selection tools to pick a color. The light’s _color key’s value will be the normalized RGB formula. Copy it from the value line in the editor (CTRL+c) and paste it into your shader.

= 4.5 q3map_surfaceLight <light value> =
The texture gives off light equal to the '''<light value>''' set for it. The relative surface area of the texture in the world affects the actual amount of light that appears to be radiated. To give off what appears to be the same amount of light, a smaller texture must be significantly brighter than a larger texture. Unless the qer_lightimage keyword is used to select a different source for the texture’s light color information, the color of the light will be the averaged color of the texture.

= 4.6 q3map_lightimage < texturepath/texturename> =
The keyword '''q3map_lightimage''' generates lighting from the average color of the TGA image specified by the q3map_lightimage.

The keyword sequence for generating light on a '''q3map_surfacelight''' should be ordered as follows:

1) '''q3map_lightimage''' ; (the texture providing the light and the color of the light)

2) '''qer_editorimage''' ; (the editor-only image used to select the source map for the texture)

3) the average color of the light emitted from the shader is calculated from the '''lightimage.''')

The reason '''q3map_lightimage''' is specified for the light in the example below, is because the blend map is predominantly yellow, and the designer wanted more yellow light to be emitted from the light.

'''Example: Taking light from another source texture'''

textures/eerie/ironcrosslt2_10000

{

q3map_lightimage textures/gothic_light/ironcrosslt2.blend.tga

// this TGA is the source for the color of the blended light

qer_editorimage textures/gothic_light/ironcrosslt2.tga

//base TGA (used because the shader is used with several

// different light values

q3map_surfacelight 10000

//emitted light value of 10,000

{

map $lightmap

//source texture is affected by the lightmap

rgbGen identity

// this command handles the overbright bits created by “sunlight”

// in the game

}

{

map textures/gothic_light/ironcrosslt2.tga

blendFunc filter

rgbGen identity

}

{

map textures/gothic_light/ironcrosslt2.blend.tga

blendFunc add

}

}

= 4.7 q3map_lightsubdivide <value> =
This allows the user to define how large, or small to make the subdivisions (triangles) in a textured surface, particularly aimed at light-emitting textures like skies. It defaults to 120 game units, but can be made larger (256 or 512) for sky boxes or smaller for light surfaces at the bottoms of cracks. This can be a dominant factor in processing time for q3map lighting.

= 4.8 surfaceparm <parm> =
All surfaceparm keywords are preceded by the word surfaceparm as follows: '''surfaceparm fog''' or '''surfaceparm noimpact.'''

== 4.8.1 alphashadow ==
This keyword applied to a texture on a brush, patch or model will cause the lighting phase of the q3map process to use the texture’s alpha channel as a mask for casting static shadows in the game world.

'''Design Note:''' Alphashadow does not work well with fine line detail on a texture. Fine lines may not cast acceptable shadows. It appears to work best with well-defined silhouettes and wider lines within the texture. Most of our tattered banners use this to cast tattered shadows.

== 4.8.2 areaportal ==
A brush marked with this keyword functions as an area portal, a break in the Q3MAP tree. It is typically placed on a very thin brush placed inside a door entity (but is not a part of that entity). The intent is to block the game from processing surface triangles located behind it when the door is closed. It is also used by the BSPC (bot area file creation compiler) in the same manner as a cluster portal. The brush must touch all the structural brushes surrounding the '''areaportal.'''

== 4.8.3 clusterportal ==
A brush marked with this keyword function creates a subdivision of the area file (.aas) used by the bots for navigation. It is typically placed in locations that are natural breaks in a map, such as entrances to halls, doors, tunnels, etc. The intent is keep the bot from having to process the entire map at once. As with the the areaportal parameter, the affected brush must touch all the structural brushes surrounding the '''areaportal.'''

== 4.8.4 donotenter ==
Read as “do not enter.” Like clusterportal, this is a bot-only property. A brush marked with donotenter will not affect non-bot players, but bots will not enter it. It should be used only when bots appear to have difficulty navigating around some map features.

== 4.8.5 flesh ==
This will cue different sounds (in a similar manner to metalsteps ) and cause blood to appear instead of bullet impact flashes.

== 4.8.6 fog ==
Fog defines the brush as being a “fog” brush. This is a Q3MAP function that chops and identifies all geometry inside the brush. The General shader keyword fogparms must also be specified to tell how to draw the fog.

== 4.8.7 lava ==
Assigns to the texture the game properties set for lava. This affects both the surface and the content of a brush.

== 4.8.8 metalsteps ==
The player sounds as if he is walking on clanging metal steps or gratings. Other than specifiying '''flesh''', '''metalsteps''', '''nosteps''', or default (i.e.; specify nothing) it is currently not possible for a designer to create or assign a specific sound routine to a texture. Note: If no sound is set for a texture, then the default footsteps sound routines are heard.

== 4.8.9 nodamage ==
The player takes no damage if he falls onto a texture with this surfaceparm

== 4.8.10 nodlight ==
Read as “No ''Dee'' Light”. A texture containing this parameter will not be affected or lit by dynamic lights, such as weapon effects. And example in ''Quake III Arena'' would be solid lava.

== 4.8.11 nodraw ==
A texture marked with nodraw will not visually appear in the game world. Most often used for triggers, clip brushes, origin brushes, and so on.

== 4.8.12 nodrop ==
When a player dies inside a volume (brush) marked nodrop, no weapon is dropped. The intend use is for “Pits of Death.” Have a kill trigger inside a nodrop volume, and when the players die here, they won't drop their weapons. The intent is to prevent unnecessary polygon pileups on the floors of pits.

== 4.8.13 noimpact ==
World entities will not impact on this texture. No explosions occur when projectiles strike this surface and no marks will be left on it. Sky textures are usually marked with this texture so those projectiles will not hit the sky and leave marks.

== 4.8.14 nomarks ==
Projectiles will explode upon contact with this surface, but will not leave marks. Blood will also not mark this surface. This is useful to keep lights from being temporarily obscured by battle damage.

'''Design Note:''' Use this on any surface with a deformVertexes keyword. Otherwise, the marks will appear on the unmodified surface location of the texture with the surface wriggles and squirms through the marks.

== 4.8.15 nolightmap ==
This texture does not have a lightmap phase. It is not affected by the ambient lighting of the world around it. It does not require the addition of an rgbGen identity keyword in that stage.

== 4.8.16 nosteps ==
The player makes no sound when walking on this texture.

== 4.8.17 nonsolid ==
This attribute indicates a brush, which does not block the movement of entities in the game world. It applied to triggers, hint brushes and similar brushes. This affects the content of a brush.

== 4.8.18 origin ==
Used on the “origin” texture. Rotating entities need to contain an origin brush in their construction. The brush must be rectangular (or square). The origin point is the exact center of the origin brush.

== 4.8.19 playerclip ==
Blocks player movement through a '''nonsolid''' texture. Other game world entities can pass through a brush marked '''playerclip'''. The intended use for this is to block the player but not block projectiles like rockets.

== 4.8.20 slick ==
This surfaceparm included in a texture should give it significantly reduced friction.

== 4.8.21 slime ==
Assigns to the texture the game properties for slime. This affects both the surface and the content of a brush.

== 4.8.22 structural ==
This surface attribute causes a brush to be seen by the Q3MAP process as a possible break-point in a BSP tree. It is used as a part of the shader for the “hint” texture. Generally speaking, any opaque texture not marked as “'''detail'''” is by default, '''structural,''' so you shouldn’t need to specify this.

== 4.8.23 trans ==
Tells q3map that pre-computed visibility should not be blocked by this surface. Generally, any shaders that have blendfuncs should be marked as surfaceparm trans.

== 4.8.24 water ==
Assigns to the texture the game properties for water.

5 Editor specific shader instructions
These instructions only affect the texture when it is seen in the [[Q3Radiant]] editor. They should be grouped with the surface parameters but ahead of them in sequence.

= 5.1 qer_editorimage < texture path/texturename> =
This keyword creates a shader name in memory, but in the editor, it displays the TGA art image specified in qer_editorimage (in the example below this is textures/eerie/lavahell.tga).

The editor maps a texture using the size attributes of the TGA file used for the editor image. When that editor image represents a shader, any texture used in any of the shader stages will be scaled up or down to the dimensions of the editor image. If a 128x128 pixel image is used to represent the shader in the editor, then a 256x256 image used in a later stage will be shrunk to fit. A 64x64 image would be stretched to fit. Be sure to check this on bouncy, acceleration, and power-up pads placed on surfaces other than 256 x 256. Use '''tcMod scale''' to change the size of the stretched texture. Remember that '''tcMod scale''' 0.5 0.5 will double your image, while '''tcMod scale''' 2 2 will halve it.

'''Design Notes:''' The base_light and gothic_light shaders contain numerous uses of this. It can be very useful for making different light styles (mostly to change the light brightnesses) without having to create a new piece of TGA art for each new shader.

textures/liquids/lavahell2 //path and name of new texture

{

qer_editorimage textures/eerie/lavahell.tga

//based on this

qer_nocarve

//cannot be cut by CSG subtract

surfaceparm noimpact

//projectiles do not hit it

surfaceparm lava

//has the game properties of lava

surfaceparm nolightmap

//environment lighting does not affect

q3map_surfacelight 3000

//light is emitted

tessSize 256

//relatively large triangles

cull disable

//no sides are removed

deformVertexes wave 100 sin 5 5 .5 0.02

fogparms 0.8519142 0.309723 0.0 128 128

{

map textures/eerie/lavahell.tga

//base texture artwork

tcMod turb .25 0.2 1 0.02

//texture is subjected to turbulence

tcMod scroll 0.1 0.1

//the turbulence is scrolled

}

}

= 5.2 qer_nocarve =
A brush marked with this instruction will not be affected by CSG subtract functions. It is especially useful for water and fog textures.

= 5.3 qer_trans <value> =
This parameter 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.

'''
'''
6 Stage Specific Keywords
Stage specifications only affect rendering. Changing any keywords or values within a stage will usually take effect as soon as a vid_restart is executed. Q3MAP ignores stage specific keywords entirely.

A stage can specify a texture map, a color function, an alpha function, a texture coordinate function, a blend function, and a few other rasterization options.

= 6.1 Texture map specification =
== 6.1.1 map <texturepath/texturename> ==
Specifies the source texture map (a 24 or 32-bit TGA file) used for this stage. The texture may or may not contain alpha channel information. The special keywords '''$lightmap''' and '''$whiteimage''' may be substituted in lieu of an actual texture map name. In those cases, the texture named in the first line of the shader becomes the texture that supplies the light mapping data for the process.

== $lightmap ==
This is the overall lightmap for the game world. It is calculated during the Q3MAP process. It is the initial color data found in the framebuffer. Note: due to the use of overbright bits in light calculation, the keyword '''rgbGen identity''' must accompany all '''$lightmap''' instructions.

== $whiteimage ==
This is used for specular lighting on MD3 models. This is is a white image generated internally by the game. This image can be used in lieu of $lightmap or an actual texture map if, for example, you wish for the vertex colors to come through unaltered.

== 6.1.2 Clampmap <texturepath> ==
Dictates that this stage should clamp texture coordinates instead of wrapping them. During a stretch function, the area, which the texture must cover during a wave cycle, enlarges and decreases. Instead of repeating a texture multiple times during enlargement (or seeing only a portion of the texture during shrinking) the texture dimensions increase or contract accordingly. This is only relevant when using something like deformTexCoordParms to stretch/compress texture coordinates for a specific special effect. Remember that the Quake III Arena engine normalizes all texture coordinates (regardless of actual texture size) into a scale of 0.0 to 1.0.

'''Proper Alignment:''' When using '''clampTexCoords''' be make sure the texture is properly aligned on the brush. The '''clampTexCoords''' function keeps the image from tiling. However, the editor doesn’t represent this properly and shows a tiled image. Therefore, what appears to be the correct position may be offset. This is very apparent on anything with a '''tcMod rotate''' and '''clampTexCoords''' function.

'''Avoiding Distortion:''' When seen at a given distance (which can vary, depending on hardware and the size of the texture), the compression phase of a stretch function will cause a “cross”-like visual artifact to form on the modified texture due to the way that textures are reduced. This occurs because the texture undergoing modification lacks sufficient “empty space” around the displayed (non-black) part of the texture (see figure 2a). To compensate for this, make the non-zero portion of the texture substantially smaller (50% of maximum stretched size -- see figure 2b) than the dimensions of the texture. Then, write a scaling function (tcScale) into the appropriate shader phase, to enlarge the image to the desired proportion.

The shaders for the bouncy pads (in the sfx.shader file) show the stretch function in use, including the scaling of the stretched texture:

'''Example: Using clampTexCoords to control a stretching texture'''

textures/sfx/metalbridge06_bounce

{

//q3map_surfacelight 2000

surfaceparm nodamage

q3map_lightimage textures/sfx/jumppadsmall.tga

q3map_surfacelight 400

{

map textures/sfx/metalbridge06_bounce.tga

rgbGen identity

}

{

map $lightmap

rgbGen identity

blendfunc gl_dst_color gl_zero

}

{

map textures/sfx/bouncepad01b_layer1.tga

blendfunc gl_one gl_one

rgbGen wave sin .5 .5 0 1.5

}

{

clampmap textures/sfx/jumppadsmall.tga

blendfunc gl_one gl_one

tcMod stretch sin 1.2 .8 0 1.5

rgbGen wave square .5 .5 .25 1.5

}

// END

}

== 6.1.3 [[AnimMap]] <frequency> <texture1> … <texture8> ==
The surfaces in the game can be animated by displaying a sequence of 1 to 8 frames (separate texture maps). These animations are affected by other keyword effects in the same and later shader stages.

'''<Frequency>:''' the number of times that the animation cycle will repeat within a one second time period. The larger the value, the more repeats within a second. Animations that should last for more than a second need to be expressed as decimal values.

'''<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.

'''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.

textures/sfx/flameanim_blue

{

// *************************************************

// * Blue Flame *

// * July 20, 1999 Surface Light 1800 *

// * Please Comment Changes *

// *************************************************

qer_editorimage textures/sfx/b_flame7.tga

q3map_lightimage textures/sfx/b_flame7.tga

surfaceparm trans

surfaceparm nomarks

surfaceparm nolightmap

cull none

q3map_surfacelight 1800

// texture changed to blue flame.... PAJ

{

animMap 10 textures/sfx/b_flame1.tga textures/sfx/b_flame2.tga textures/sfx/b_flame3.tga textures/sfx/b_flame4.tga textures/sfx/b_flame5.tga textures/sfx/b_flame6.tga textures/sfx/b_flame7.tga textures/sfx/b_flame8.tga

blendFunc GL_ONE GL_ONE

rgbGen wave inverseSawtooth 0 1 0 10

}

{

animMap 10 textures/sfx/b_flame2.tga textures/sfx/b_flame3.tga textures/sfx/b_flame4.tga textures/sfx/b_flame5.tga textures/sfx/b_flame6.tga textures/sfx/b_flame7.tga textures/sfx/b_flame8.tga textures/sfx/b_flame1.tga

blendFunc GL_ONE GL_ONE

rgbGen wave sawtooth 0 1 0 10

}

{

map textures/sfx/b_flameball.tga

blendFunc GL_ONE GL_ONE

rgbGen wave sin .6 .2 0 .6

}

}

= 6.2 Blend Functions =
Blend functions are the keyword commands that tell the ''Quake III Arena'' graphic engine’s renderer how graphic layers are to be mixed together.

== 6.2.1 Simplified blend functions: ==
The most common blend functions are set up here as simple commands, and should be used unless you really know what you are doing.

=== 6.2.1.1 blendfunc add ===
This is a shorthand command for '''blendfunc gl_one gl_one. ''' Effects like fire and energy are additive.''' '''

=== 6.2.1.2 blendfunc filter ===
This is a shorthand command that can be substituted for either '''blendfunc gl_dst_color gl_zero''' or '''blendfunc gl_zero gl_src_color'''. A filter will always result in darker pixels than what is behind it, but it can also remove color selectively. Lightmaps are filters.

=== 6.2.1.3 blendfunc blend ===
Shorthand for blendfunc gl_src_alpha gl_one_minus_src_alpha. This is conventional transparency, where part of the background is mixed with part of the texture.

== 6.2.2 Explicit blend functions: ==
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:

'''[Source * <srcBlend>] + [Destination * <dstBlend>]'''

'''Source''' is usually the RGB color data in a texture TGA file (remember it’s all numbers) modified by any rgbgen and alphagen. In the shader, the source is generally identified by command MAP, followed by the name of the image.

''' '''

'''Destination''' is the color data currently existing in the frame buffer.

Rather than think of the entire texture as a whole, it may be easier to think of the number values that correspond to a single pixel, because that is essentially what the computer is processing … one pixel of the bit map at a time.

The process for calculating the final look of a texture in place in the game world begins with the precalculated lightmap for the area where the texture will be located. This data is in the frame buffer. That is to say, it is the initial data in the '''Destination'''. In an unmanipulated texture (i.e.; one without a special shader script), color information from the texture is combined with the lightmap. In a shader-modified texture, the $lightmap stage must be present for the lightmap to be included in the calculation of the final texture appearance.

Each pass or “stage” of blending is combined (in a cumulative manner) with the color data passed onto it by the previous stage. How that data combines together depends on the values chosen for the Source Blends and Destination Blends at each stage. Remember it’s numbers that are being mathematically combined together that are ultimately interpreted as colors.

A general rule is that any '''Source Blend''' other than '''GL_ONE''' (or '''GL_SRC_ALPHA''' where the alpha channel is entirely white) will cause the Source to become darker.

== 6.2.3 Source Blend <srcBlend> ==
The following values are valid for the Source Blend part of the equation.

''' '''

'''GL_ONE''' This is the value 1. When multiplied by the '''Source''', the value stays the same the value of the color information does not change.

'''GL_ZERO''' This is the value 0. When multiplied by the '''Source''', all RGB data in the '''Source''' becomes Zero (essentially black).

'''GL_DST_COLOR''' This is the value of color data currently in the Destination (frame buffer). The value of that information depends on the information supplied by previous stages.

'''GL_ONE_MINUS_DST_COLOR ''' This is nearly the same as GL_DST_COLOR except that the value for each component color is inverted by subtracting it from one. (,i.e.; R = 1.0 – DST.R, G = 1.0 – DST.G, B = 1.0 – DST.B, etc.)

'''GL_SRC_ALPHA''' The TGA file being used for the '''Source''' data must have an alpha channel in addition to its RGB channels (for a total of four channels). The alpha channel is an 8-bit black and white only channel. An entirely white alpha channel will not darken the '''Source'''.

'''GL_ONE_MINUS_SRC_ALPHA ''' This is the same as GL_SRC_ALPHA except that the value in the alpha channel is inverted by subtracting it from one. (i.e.; A=1.0 – SRC.A)

== 6.2.4 Destination Blend <dstBlend> ==
The following values are valid for the Destination Blend part of the equation.

'''GL_ONE''' This is the value 1. When multiplied by the '''Destination''', the value stays the same the value of the color information does not change.

'''GL_ZERO''' This is the value 0. When multiplied by the '''Destination''', all RGB data in the '''Destination''' becomes Zero (essentially black).

'''GL_SRC_COLOR''' This is the value of color data currently in the '''Source''' (which is the texture being manipulated here).

'''GL_ONE_MINUS_SRC_COLOR ''' This is the value of color data currently in '''Source''', but subtracted from one (i.e.; inverted).

'''GL_SRC_ALPHA''' The TGA file being used for the '''Source''' data must have an alpha channel in addition to its RGB channels (four a total of four channels). The alpha channel is an 8-bit black and white only channel. An entirely white alpha channel will not darken the '''Source'''.

'''GL_ONE_MINUS_SRC_ALPHA ''' This is the same as GL_SRC_ALPHA except that the value in the alpha channel is inverted by subtracting it from one. (i.e.; A=1.0 – SRC.A).

''' '''

'''Doing the Math: The Final Result'''

The product of the '''Source''' side of the equation is added to the product of the '''Destination''' side of the equation. The sum is then placed into the frame buffer to become the '''Destination''' information for the next stage. Ultimately, the equation creates a modified color value that is used by other functions to define what happens in the texture when it is displayed in the game world.

== 6.2.5 Default Blend Function ==
''If no '''blendFunc''' is specified then no blending will take place.'' A warning is generated if any stage after the first stage does not have a '''blendFunc''' specified.

== 6.2.6 Technical Information/Limitations Regarding Blend Modes: ==
The Riva 128 graphics card supports ONLY the following blend modes:

GL_ONE, GL_ONE

GL_DST_COLOR, GL_ZERO

GL_ZERO, GL_SRC_COLOR

GL_SRC_ALPHA, GL_ONE_MINUS_SRC_ALPHA

GL_ONE_MINUS_SRC_ALPHA, GL_SRC_ALPHA

Cards running in 16 bit color cannot use any GL_DST_ALPHA blends.

= 6.3 rgbGen <func> =
There are two color sources for any given shader, the texture file and the vertex colors. Output at any given time will be equal to '''TEXTURE''' multiplied by '''VERTEXCOLOR'''. Most of the time VERTEXCOLOR will default to white (which is a normalized value of 1.0), so output will be TEXTURE (this usually lands in the '''Source''' side of the shader equation). Sometimes you do the opposite and use TEXTURE = WHITE, but this is only commonly used when doing specular lighting on entities (i.e.; shaders that level designers will probably never create

The most common reason to use rgbGen is to pulsate something. This means that the VERTEXCOLOR will oscillate between two values, and that value will be multiplied (darkening) the texture.

If no rgbGen is specified, either “identityLighting” or “identity” will be selected, depending on which blend modes are used.

Valid <func> parameters are '''wave, identity, identityLighting, entity, oneMinusEntity, fromVertex,''' and '''lightingDiffuse'''.

== 6.3.1 [[RgbGen]] identityLighting ==
Colors will be (1.0,1.0,1.0) if running without overbright bits (NT, linux, windowed modes), or (0.5, 0.5, 0.5) if running with overbright. Overbright allows a greater color range at the expense of a loss of precision. Additive and blended stages will get this by default.

== 6.3.2 rgbGen identity ==
Colors are assumed to be all white (1.0,1.0,1.0). All filters stages (lightmaps, etc) will get this by default.

== 6.3.3 rgbGen wave <func> <base> <amp> <phase> <freq> ==
Colors are generated using the specified waveform. An affected texture with become darker and lighter, but will not change hue. Hue stays constant. Note that the rgb values for color will not go below 0 (black) or above 1 (white). Valid waveforms are sin, triangle, square, sawtooth and inversesawtooth.

'''<func> Wave''' forms and their effects:

'''Sin:''' color flows smoothly through changes.

'''Triangle:''' color changes at a constant rate and spends no appreciable time at peaks and valleys.

'''Square:''' color alternates instantly between its peak and valley values.

'''Sawtooth:''' With a positive frequency value, the color changes at a constant rate to the peak then instantly drops to its valley value.

'''Inversesawtooth:''' An inverse sawtooth wave will reverse this, making the ascent immediate (like a square wave) and the decay fall off like a triangle wave.

'''<base>''' Baseline value. The initial RGB formula of a color (normalilzed.

'''<amp>''' Amplitude. This is the degree of change from the baseline value. In some cases you will want values outside the 0.0 to 1.0 range, but it will induce clamping (holding at the maximum or minimum value for a time period) instead of continuous change.

'''<phase>''' See the explanation for phase under the waveforms heading of Key Concepts.

'''<freq>''' Frequency. This is a value (NOT normalized) that indicates peaks per second.

== 6.3.4 [[RgbGen]] entity ==
Colors are grabbed from the entity’s '''modulate''' field. This is used for things like explosions.

'''Design Note''': This keyword would probably not be used by a level designer.

== 6.3.5 rgbGen oneMinusEntity ==
Colors are grabbed from 1.0 minus the entity’s modulate field.

'''Design Note''': This keyword would probably not be used by a level designer.

== 6.3.6 rgbGen Vertex ==
Colors are filled in directly by the data from the map or model files.

'''Design Note''': rgbGen vertex should be used when you want the RGB values to be computed

for a static model (i.e. mapobject) in the world using precomputed static

lighting from Q3BSP. This would be used on things like the gargoyles, the portal frame,

skulls, and other decorative MD3s put into the Quake III Arena world.

== 6.3.7 rgbGen oneMinusVertex ==
As rgbGen vertex, but inverted.

'''Design Note''': This keyword would probably not be used by a level designer

== 6.3.8 rgbGen lightingDiffuse ==
Colors are computed using a standard diffuse lighting equation. It uses the vertex normals to illuminate the object correctly.

'''Design Note:''' - rgbGen lightingDiffuse is used when you want the RGB values to be

computed for a dynamic model (i.e. non-map object) in the world using

regular in-game lighting. For example, you would specify on shaders for

items, characters, weapons, etc.

= 6.4 [[AlphaGen]] <func> =
The alpha channel can be specified like the rgb channels. If not specified, it defaults to 1.0.

== 6.4.1 [[AlphaGen]] portal ==
This rendering stage keyword is used in conjunction with the surface parameter keyword '''portal'''. The function accomplishes the “fade” that causes the scene in the portal to fade from view. Specifically, it means “Generate alpha values based on the distance from the viewer to the portal.” Use '''alphaGen''' portal on the last rendering pass.

= 6.5 tcGen <coordinate source> =
Specifies how texture coordinates are generated and where they come from. Valid functions are '''base''', '''lightmap''' and '''environment.'''

'''<base>''' = base texture coordinates from the original art.

'''<lightmap>''' = lightmap texture coordinates

'''<environment>''' = Make this object environment mapped.

== 6.5.1 tcGen vector (<sx> <sy> <sz>) (<tx> <ty> <tz>) ==
New texcoord generation by world projection. This allows you to project a

texture onto a surface in a fixed way, regardless of its orientation.

S coordinates correspond to the “x” coordinates on the texture itself.

T coordinates correspond to the “y” coordinates on the texture itself.

The measurements are in game units.

Example: tcGen vector (0.01 0 0) (0 0.01 0)

This would project a texture with a repeat every 100 units across the X/Y plane.

= 6.6 tcMod <func> <…> =
Specifies how texture coordinates are modified after they are generated. The valid functions for tcMod are '''rotate, scale, scroll, stretch and transform.''' '''Transform''' is a function generally reserved for use by programmers who suggest that designers leave it alone. When using multiple tcMod functions during a stage, place the '''scroll''' command last in order, because it performs a mod operation to save precision, and that can disturb other operations. Texture coordinates are modified in the order in which tcMods are specified. In other words, if you see:

'''tcMod scale 0.5 0.5'''

'''tcMod scroll 1 1'''

Then the texture coordinates will be '''scaled''' ''then'' '''scrolled.'''

== 6.6.1 tcMod rotate <degrees per per second> ==
This keyword causes the texture coordinates to rotate. The value is expressed in degrees rotated each second. A positive value means clockwise rotation. A negative value means counterclockwise rotation. For example “tcMod rotate 5” would rotate texture coordinates 5 degrees each second in a clockwise direction. The texture rotates around the center point of the texture map, so you are rotating a texture with a single repetition, be careful to center it on the brush (unless off-center rotation is desired).

== 6.6.2 tcMod scale <sScale> <tScale> ==
Resizes (enlarges or shrinks) the texture coordinates by multiplying them against the given factors of <sScale> and <tScale). The values “s” and “t” conform to the “x” and “y” values (respectively) as they are found in the original texture TGA. The values for '''sScale''' and '''tScale''' are NOT normalized. This means that a value greater than 1.0 will increase the size of the texture. A positive value less than one will reduce the texture to a fraction of its size and cause it to repeat within the same area as the original texture (Note: see '''clampTexCoords''' for ways to control this).;

'''Example:''' ''tcMod scale 0.5 2'' would cause the texture to repeat twice along its width, but expand to twice its height (in which case half of the texture would be seen in the same area as the original)

== 6.6.3 tcMod scroll <sSpeed> <tSpeed> ==
Scrolls the texture coordinates with the given speeds. ). The values “s” and “t” conform to the “x” and “y” values (respectively) as they are found in the original texture TGA, The scroll speed is measured in “textures” per second. A “texture” is the dimension of the texture being modified and includes any previous shader modifications to the original TGA). A negative s value would scroll the texture to the left. A negative t value would scroll the texture down.

Example: tcMod scroll 0.5 -0.5 moves the texture down and right (relative to the TGA files original coordinates) at the rate of a half texture each second of travel.

This should be the LAST tcMod in a stage. Otherwise there may be popping or snapping visual effects in some shaders.

== 6.6.4 tcMod stretch <func> <base> <amplitude> <phase> <frequency> ==
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

'''<base>:''' A base value of one is the original dimension of the texture when it reaches the stretch stage. Inserting other values positive or negative in this variable will produce unknown effects.

'''<amplitude>:''' This is the measurement of distance the texture will stretch from the base size. It is measured, like scroll, in textures. A value of 1 here will double the size of the texture at its peak.

'''<phase>:''' See the explanation for phase under the deform vertexes keyword.

'''<frequency>''': this is wave peaks per second.

'''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.

'''Triangle wave:''' The textures stretch at a constant rate and spend no appreciable time at the peak or valley points.

'''Square wave:''' The texture is shown at its peak for the duration of the frequency and then at its valley for the duration of the frequency.

'''Sawtooth:''' the texture stretches like a triangle wave until it reaches a peak, then instantly drops to the valley, as in a square wave.

'''Inversesawtooth''': this is the reverse of the sawtooth wave.

== 6.6.5 tcMod <transform> <m00> <m01> <m10> <m11> <t0> <t1> ==
Transforms each texture coordinate as follows:

S’ = s * m00 + t * m10 + t0

T’ = t * m01 + s * m11 + t1

This is for use by programmers.

== 6.6.6 tcMod turb <base> <amplitude> <phase> <freq> ==
Applies turbulence to the texture coordinate. Turbulence is a back and forth churning and swirling effect on the texture.

The parameters for this shader are defined as follows:

'''<base>''' Currently undefined.

'''<amplitude>''' This is essentially the intensity of the disturbance or twisting and squiggling of the texture.

''' '''

'''<phase>''' See the explanation for phase under the '''deform vertexes''' keyword.

'''<freq>''' Frequency. This value is expressed as repetitions or cycles of the wave per second. A value of one would cycle once per second. A value of 10 would cycle 10 times per second. A value of 0.1 would cycle once every 10 seconds.

= 6.7 depthFunc <func> =
This controls the depth comparison function used while rendering. The default is “lequal” (Less than or equal to) where any surface that is at the same depth or closer of an existing surface is drawn. This is used for textures with transparency or translucency. Under some circumstances you may wish to use “equal”, e.g. for lightmapped grates that are alpha tested (it is also used for mirrors).

= 6.8 depthWrite =
By default, writes to the depth buffer when depthFunc passes will happen for opaque surfaces and not for translucent surfaces. Blended surfaces can have the depth writes forced with this function.

= 6.9 Detail =
This feature was not used in Quake III Arena maps, but should still function.

Designates this stage as a detail texture stage, which means that if the c_var, r_detailtextures, is set to 0 then this stage will be ignored (detail will not be displayed). This keyword, by itself, does not affect rendering at all. If you do put in a detail texture, it has to conform to very specific rules. Specifically, the blendFunc:

'''blendFunc GL_DST_COLOR GL_SRC_COLOR'''

''' '''

This is also the simple blend function: '''blendfunc filter'''

And the average ''intensity'' of the detail texture itself must be around 127.

Detail is used to blend fine pixel detail back into a base texture whose scale has been increased significantly. When detail is written into a set of stage instructions, it allows the stage to be disabled by the c_var console command setting "r_detailtextures 0".

A texture whose scale has been increased beyond a 1:1 ratio tends not to have very high frequency content. In other words, one texel can cover a lot of real estate. Frequency is also known as “detail.” Lack of detail can appear acceptable if the player never has the opportunity to see the texture at close range. But seen close up, such textures look glaringly wrong within the sharp detail of the Quake III Arena environment. A detail texture solves this problem by taking a noisy "detail" pattern (a tiling texture that appears to have a great deal of surface roughness) and applying it to the base texture at a very densely packed scale (that is, reduced from its normal size). This is done programmatically in the shader, and does not require modification of the base texture. Note that if the detail texture is the same size and scale as the base texture that you may as well just add the detail directly to the base texture. The theory is that the detail texture's scale will be so high compared to the base texture (e.g.; 9 detail texels fitting into 1 base texel) that it is literally impossible to fit that detail into the base texture directly.

For this to work, the rules are as

follows:

A.) the lightmap must be rendered first. This is because the subsequent detail texture will be modifying the lightmap in the framebuffer directly;

B.) the detail texture must be rendered next since it modifies the lightmap in the framebuffer

C.) the base texture must be rendered last ;

D.) the detail texture MUST have a mean intensity around 127-129. If it does not then it will modify the displayed texture’s perceived brightness in the world

E.) the detail shader stage MUST have the "'''detail'''" keyword or it will not

be disabled if the user uses the "r_detailtextures 0" setting ;

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.;

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.

H.) detail textures add one pass of overdraw, so there is a definite performance hit .

I.) detail textures can be shared, so designers may wish to define only a very

small handful of detail textures for common surfaces such as rocks, etc.

An example (non-existent) detail shader is as follows:

'''Example: Texture with Detail'''

textures/bwhtest/foo

{

// draw the lightmap first

{

map $lightmap

rgbGen identity

}

// modify the lightmap in the framebuffer by

// a highly compressed detail texture

{

map textures/details/detail01.tga

blendFunc GL_DST_COLOR GL_SRC_COLOR

// YOU MUST USE THIS!!

detail

// for the detail to be disabled, this must be present

tcMod scale 9.1 9.2

}

// now slap on the base texture

{

map textures/castle/blocks11b.tga

blendFunc filter

}

}

= 6.10 alphaFunc <func> =
Determines the alpha test function used when rendering this map. Valid values are GT0, LT128, and GE128. These correspond to “GREATER THAN 0”, “LESS THAN 128”, and “GREATER THAN OR EQUAL TO 128”. This function is used when determining if a pixel should be written to the framebuffer. For example, if GT0 is specified, the only the portions of the texture map with corresponding alpha values greater than zero will be written to the framebuffer. By default alpha testing is disabled.

Both alpha testing and normal alpha blending can be used to get textures that have see-through parts. The difference is that alphaFunc is an all-or-nothing test, while blending smoothly blends between opaque and translucent at pixel edges. Alpha test can also be used with '''depthwrite''', allowing other effects to be conditionally layered on top of just the opaque pixels by setting '''depthFunc''' to equal.

7 Notes on Alpha Channels
To use some blend modes of alphaFunc, you must add an alpha channel to your texture files. Photoshop can do this. Paintshop Pro has the ability to make an alpha channel cannot work directly in to it. In Photoshop you want to set the type to Mask. Black has a value of 255. White has a value of 0. The darkness of a pixel’s alpha value determines the transparency of the corresponding RGB value in the game world. Darker = more transparent.

Care must be taken when reworking textures with alpha channels. Textures without alpha channels are saved as 24 bit images while textures with alpha channels are saved as 32 bit. If you save them out as 24 bit, the alpha channel is erased. Note: Adobe Photoshop will prompt you to save as 32, 24 or 16 bit. Choose wisely. If you save a texture as 32 bit and you don’t actually have anything in the alpha channel, Quake III Arena may still be forced to use a lower quality texture format (when in 16 bit rendering) than if you had saved it as 24 bit.

To create a texture that has “open” areas, make those areas black in the alpha channel and make white the areas that are to be opaque. Using gray shades can create varying degrees of opacity/transparency.

Example: An opaque texture with see-through holes knocked in it.

textures/base_floor/pjgrate1

{

surfaceparm metalsteps

cull none

// A GRATE OR GRILL THAT CAN BE SEEN FROM BOTH SIDES

{

map textures/base_floor/pjgrate1.tga

blendFunc GL_SRC_ALPHA GL_ONE_MINUS_SRC_ALPHA

alphaFunc GT0

depthWrite

rgbGen identity

}

{

map $lightmap

rgbGen identity

blendFunc GL_DST_COLOR GL_ZERO

depthFunc equal

}

}

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:

attachment:image003.jpg

Figure 1

Start with a TGA file image. In this case, a pentagram on a plain white field (figure 1A). The color of the field surrrounding the image to be merged is not relevant to this process (although having a hard-edged break between the image to be isolated and the field makes the mask making process easier). Make an alpha channel. The area of the image to be merged with another image is masked off in white. The area to be masked out (not used) is pure black (figure 1B). The image to be merged into is greenfloor.tga (figure 1C).

Make a '''qer_editorimage''' of greenfloor.tga. This is placed in the frame buffer as the map image for the texture. By using GL_SRC_ALPHA as the source part of the blend equation, the shader adds in only the non-black parts of the pentagram. Using GL_MINUS_ONE_SRC_ALPHA, the shader inverts the pentagram’s alpha channel and adds in only the non-black parts of the green floor.

In a like manner, the alpha channel can be used to blend the textures more evenly. A simple experiment involves using a linear gradiant in the alpha channel (white to black) and merging two textures so they appear to cross fade into each other.

A more complicated experiment would be to take the pentagram in the first example and give it an aliased edge so that the pentagram appeared to fade or blend into the floor.

8 Troubleshooting Shaders

If a shader is not working, look first for syntax errors.

Are the brackets correctly set?

Do you have too many parameter values on a line?

Are you using a word in a parameter that wants a numerical value?

Are you using a numerical value in a parameter that wants a word?

Are the path names to your textures correct?

Are your texture names correct? There is a chance that the texture name is too long or too complex. Try renaming a texture with a shorter, simpler name.

9 Creating New Textures
If you are familiar with the required tools, creating new assets for use in Quake III Arena is not particularly difficult. As a general rule, you should create new directories for each map with names different from the names used by id. If you are making a map that will be called “H4x0r_D00M”, every directory containing new assets for that map should be titled H4x0r_D00M. This is to try and avoid asset directories overwriting each other as the editor and the game load in assets.

= 9.1 Tools Needed =
Any combination of graphic programs and plug-ins that can output a 24 bit MS windows compatible Targa (.tga) or JPEG (.jpg) graphic file. If you plan to make textures that will have an alpha channel component (a 4th 8-bit greyscale channel that is used by the shaders to further manipulate the art), you must have a program that can create 32-bit art with that fourth channel.

Adobe Photoshop has the ability to easily create alpha channels. Paint Shop Pro from JASC (v5.0+) can also make an alpha channel by creating a mask and naming it “alpha”.

Generally speaking, regardless of the program used, we found it best to do most of the art manipulation of the alpha channel in a separate layer or file and then paste it into the alpha channel before saving.

= 9.2 Setting up Files =
The editor and the game program look for assets to be located along the paths set up in your project file. Start by creating a directory for you new textures by creating file folders to make a directory path as follows: quake3\baseq3\textures\[mymapname]

The installation of [[Q3Radiant]] will create a text document called “shaderlist.txt” in the following path:

quake3\baseq3\scripts\shaderlist.txt

[[Q3Radiant]] will use the contents of this script to grab your new textures for inclusion in the game. The contents of shaderlist.txt document will contain a listing of all the shader documents that were used by id Software to create Quake III Arena.

Since you will obviously want to create your own shaders, you need to put them in separate folders and create a new shader script for them.

If you plan to work on several maps at once and want to distinguish between textures used in each map, simply add additional map names here. For map and mod makers, we STRONGLY recommend that any new shader scripts created use the name of the map or mod in the shader file name. We know we can’t avoid every incident of files overwriting each other, but we certainly can advise you how to try.

Now, in the scripts directory that you just created, create another text file and call it:

[mymapname].shader

This file will contain the shader scripts you write to modify a particular texture.

= 9.3 Rules and Guidelines =
== 9.3.1 Rules ==
Follow these rules when creating textures for the Quake III Arena engine:

· Save your textures into your new [map name] directories.

· Don’t use the same names that id used for textures. It will cause problems.

· For best quality, save textures without an alpha channel as 24 bit TARGA files. Using JPEG files can save memory space, but at the risk of losing detail and depth in the texture. JPEG files cannot be used for textures requiring an alpha channel.

· Textures containing an alpha channel must be saved as 32 bit TARGA files.

· If a new texture requires no further manipulation, it does not need a shader script.

· Size textures in powers of 2. Example: 8x8, 16x16, 32x32, 64x64 pixels and so on.

· Textures don’t need to be square. A 32x256 pixel texture is perfectly acceptable.

== 9.3.2 Guidelines ==
The following are some things the id designers learned about textures.

· Create textures in “suites” built around one or two large textures with a number of much smaller supporting detail or accent textures.

· Very large textures are possible, but some video cards compress textures larger than 256x256 pixels.

· Textures are grouped alphabetically by name in the texture display window, so you may want to give suites of textures similar names.

· Use the shader function qe3_editorimage to conserve memory when making multiple versions of a single texture (as in the case of a glowing texture with several light values).

· Unless you are creating special effects or textures designed to draw the player’s eye to a specific spot, muted, middle value colors work best with the game engine.

· Extremely busy (a lot of fussy detail) textures can break up or form visually unpleasant patterns when seen at distances.

= 9.4 Making the .pk3 File =
When you go to distribute your creation to the gaming world, you need to put your newly created map, textures, bot area files, and shader documents into an archive format called a “pk3” file. You do not need to include the shaderlist.txt file, since that is only used by the editor. You will need to keep the paths to the various assets the same. So your paths should be something like this:

Textures: baseq3/textures/[mymapnamefolder]

Bsp & aas: baseq3/maps/mymapname.bsp , mymapname.aas

Shader scripts: baseq3/scripts/mymapname.shader

You need to use an archiving program call Winzip to make the pk3 file. Get Winzip from http://www.winzip.com/winzip/winzip.htm

Make a zip archive called mymapname.zip

Zip all the required assets into a zip archive file (Quake III Arena ''DOES'' support compressed pk3 files).

Rename the zip archive to mymapname.pk3

Put it where the Quake III Arena community can find it.

OldSiteResourcesQuake3ModelManual

2006-06-09T06:34:10Z

VitoMiliano:

__NOTOC__
Putting New Models in Quake III Arena
Based on original notes by Paul Steed

Edited by Paul Jaquays
Edited 12/22/99 by ps

The purpose of this document is to explain how to set up a model for Quake 3 Arena, create the necessary animation and conversion files, and then export it into the MD3 format required by the game. It is intended to be informative only and not a tutorial on building or animating models.

The player models for Quake III Arena were built using the commercial modeling software, 3D Studio Max R2.5 (3ds Max) by Kinetix. These models were then animated using Physique and Biped, components of a plugin for 3dsMax called Character Studio (also by Kinetix). The following instructions assume that you will model and animate with 3dsMax and Character Studio.

# Setting up the Files
Begin in your ''Quake3'' directory. If you don’t have one already, create a ''baseq3'' directory. Inside the ''baseq3'' directory, create a ''models'' directory. Inside the models directory, create a players directory. Inside the players directory, create a directory with the name of your model (we will use [character] in this document to represent information requiring the name of the model). It is generally a good idea to create a ‘work’ directory under [character] so that the [character] directory itself remains uncluttered. Place all versions of your model and temp textures here, saving the [character] directory purely for the finished model files.

# Building and Naming the Mesh
The mesh should be built keeping in mind the game engine needs three distinct body part grouping: the head, the upper body, and the lower body. These groupings can consist of different parts or sub-objects, but keep in mind too many sub-objects does impact performance and game play speed. A good rule of thumb is to consolidate your objects (i.e. attach them to each other) as long as they remain a part of a major group. For example, you decide to create a character that has its arms as separate objects for easier animation. Unless the arms or torso has different textures assigned to them go ahead and attach the arms to the torso. It may be more difficult to assign the vertices to the biped skeleton later on, but the efficiency of the model is much better. However, if you must keep the limbs detached for unique shader assignment then keep the following naming conventions in mind:

= 2.1 Head Geometry =
All head geometry needs to begin with lower case 'H_' (h_head, h_glasses, h_hat, etc...). Keep in mind that the head has no animations itself other than to respond to player mouse-look input.

= 2.2 Upper Body Geometry =
All upper body geometry needs to begin with lower case 'U_' (u_torso, u_arms, u_abdomen, etc.) This is your model’s torso and arms. The individual animations for the upper body are listed below.

= 2.3 Lower Body Geometry =
All lower body geometry begins with lower case 'L_' (l_hips, l_legs, l_lfoot, l_rfoot, etc...). This is your model’s buttocks, legs and feet. The individual animations for the upper body are listed below.

= 2.4 Tags =
Tags are connection points for other model parts and represent the limited hierarchical system of the game. They include links between the three character body parts and the weapons. Keep in mind that these tags are representations of geometry so they can be animated to represent that geometry. For example, tag_head represents the head, tag_torso represents the torso and tag_weapon represents the weapon. This is important to understand since for example, any time the character is performing a locomotive animation, the upper body can and will animate independently of the lower body, using the relative position of the tag as a base or ‘home’ position. The tags for the body parts and weapons are named tag_weapon, tag_torso and tag_head.

# Texturing
Once you finish building your character go ahead and attach it to your biped and do some basic test animations to make certain the mesh doesn’t deform in weird ways. Turn edges, ad faces, whatever you need to do to make sure that while animating, the character retains its mesh integrity. Handing the mesh over to another artist to assign UVW’s or assigning and texturing yourself without testing the animation integrity of the mesh is very risky. Major modifications after UV assignment can cost you valuable time resulting in re-assigning not just the UV’s, but re-attaching the mesh to your biped as well. Once your model is ready, go ahead and apply the texture to it. Typically the textures used in Q3A consist of one 256 x 256 texture for the body and one 128 x 128 texture for the head. Keep in mind that it’s best to consolidate your texture on a single page rather than break it up into smaller pages. Also some video cards cannot process a texture size larger than 256, so making a high-rez 1024 x 512 texture just won’t be seen since the card will knock it down to 256 x 128 to digest it.

# Set Up for Animation

Once the character is textured or skinned, bring the mesh back into 3dsMax (2.5) and attach it to an adjusted Biped using the Character Studio plug-in. As a rule of thumb, it’s always better to just assign the mesh to the biped using the default settings and then manually assign vertices to appropriate skeletal ‘limbs’.

# Animation
When animating the character, keep all animations in one file. It's crucial that the animations adhere to a specific order that pertains to the separate body parts as this supports our current tag system.
Basically the order of animations goes: full body (animations that combine both upper and lower), upper body, and lower body. Each character file has the following animations in them and for now that's all the modeler is allowed. The division is basically death (all body parts), extraneous upper body, and dedicated locomotive animations. That way all the upper body animations can be performed at any time, separate from whatever it is that that lower body animations may be doing. There is a set number of animation types which are (in order):
= - death1 (approx. 30 frames) - death2 (approx. 30 frames) - death3 (approx. 30 frames) =
= - taunt (approx. 45 frames) - weapon attack (exactly 6 frames) - melee attack (exactly 6 frames) - change weapon (exactly 9 frames) - weapon idle (exactly 1 frame) - melee idle (exactly 1 frame) =

-crouched walk (approx. 10 frames)
- walk (approx. 15 frames)
- run (approx. 12 frames)
- backpedal (approx. 10 frames)
- swim (approx. 10 frames)
- jump forward (approx. 10 frames)
- jump forward-land (approx. 6 frames)
- jump backward (approx. 10 frames)
- jump backward-land (approx. 6 frames)
- standing idle (approx. 10 frames)
- crouched idle (approx. 10 frames)
- turn in place (approx. 8 frames)

A good rule of thumb is to create an idle pose at the frame right after the final death frame. Keep this pose for the entire lower body and center of mass of the biped up through melee idle frame since any animation by the lower body during these frames will not register during the grab process. Similarly, once the animations for the lower body start, copy the pose for the upper body at the weapon idle frame to the first frame of the crouched walk animation and don’t animate the upper body at all after that frame. This allows you to more closely approximate what happens during the game where the upper body is basically just along for the ride as the lower body carries it along via the tag_torso.

Keep in mind that an animation.cfg has to be generated for each character that is a direct reflection of your animation file above.

# Setting up Tags After the modeler is satisfied with the animations for the character, it’s time to bring in the tags that up until now, have kept in a separate file. This is milestone mark that lets the modeler know that the character is nearly complete. ‘Merge’ the tags into your scene. Turn off 'inherit scale' for the tags under the hierarchy/link command panel in Max. Then, assign a Physique modifier (Character Studio), linking them to specific areas in the biped:
tag_torso is linked to the Biped 'pelvis'
tag_head is linked to the Biped 'head'.

tag_weapon is linked to the right ‘hand’.

= 6.1 Animate Body Tags =
Now, go in and actually animate the tag_torso so that it matches the default position (established previously at approximately the standing idle frame- from the top view it looks like a perfect 90 degree triangle with the base half as wide as the length, pointing forward) when appropriate. “Appropriate” means that as the character goes through the lower body animations, if the triangle is pointing anywhere else but forward, the upper body will point that way as well since to the code the upper body IS the tag. This works out to the modeler’s advantage, though because even if the upper body LOOKS crazy in the animation you simply rely on the tag representation to compensate for it.

= 6.2 Handling Weapon Tags =
Tag_weapon is a bit different. Basically there is no difference between view model weapons (the weapon as seen by the player when it is in use by his or another player) and the world model weapons (weapons as they are found rotating in the maps) in Quake III Arena. However, for visually clarity and identification, they are doubled in scale when they become seen as world models. They are the same object. This reduces the number of models needed the game and creates an overall more efficient system. Unfortunately a drawback to the system is that there can be only one firing animation for the character. Thusly all weapons need to fit within the grip of the character regardless of size or geometry. This also makes it impossible to see hands on your weapons or otherwise perform vertex animation on the weapons other than barrel rotations vis the tag system (tag_barrel).

Since the placement is always the same for the character's hands on the weapons , create the animations to the point where it begins the weapon attack sequence. Then merge one of the weapon models into the character file as a guide. The weapons have a nested triangle of same dimensions as the tag_head and tag_torso triangles (each weapon in the game has this triangle saved with it. Move the weapon into a horizontal firing position (using the side view) to about where the character would be holding the weapon correctly. Then move the character's hands into the appropriate position and link the weapon to the character's right hand.

When you get to the point where you bring in the tags, make a snapshot of the weapon, hide the original and simply delete all the vertices and faces of the copy of the weapon object except for the nested triangle. Rename it tag_weapon, turn off the 'inherit scale' attributes (very important), and assign Physique to it (linking it to the 'right hand' of the biped) and voila. Ready to export.

# Level of Detail
Each of the Quake III Arena player characters have a base model and two lower polygon versions of the model (to help with speed issues). For use in the game, the three levels of detail are file formatted as follows:

[character].[file extension] This is the highest detail model for close up viewing

[character]_1.[file extension] This is a slightly lower polygon model for mid distance viewing

[character]_2.[file extension] This is the lowest polygon model for long distance viewing.

Level of detail means you need to make three versions of your model to get the best performance during gameplay. Each version needs to have the same textures assigned and same animations assigned to them in order to work in the game. The numbers you need to shoot for are 800 faces for the highest level, 500 faces for next level and 300 for the lowest level. This works out roughly to be a 60% drop in each LOD, but your numbers will vary in order to maintain mesh integrity. Most LOD’s created in Q3A were done with the plugin called MRM (multiple resolution mesh) by Intel. The stock Optimize modifier or manual optimization techniques can be applied.

# Exporting

Once the tags are in place (also with the Physique modifier attached to them) the model is ready to export to an ase(ascii) file.''' ''' To make the models available for use in Quake III Arena, the model was exported to a native 3dsMax ASCII format file called an ‘.ase’ file. This export option in Max has several check boxes to tweak and then just exports the character with its animation data (via Character Studio) to a huge ase/ascii file. Under ‘Output Options’ make sure the ‘Mesh Definition’, ‘Materials’, ‘Transform Animation Keys’, and ‘Animated Mesh’ boxes are checked. Under ‘Mesh Options’ and ‘Object Types’ make sure ‘Mapping Coordinates’ and ‘Geometric’ are the only boxes checked, respectively and let it run. Your ‘Time Configuration’ must reflect a ‘0’ starting point up through the last frame of your animation. The native Max exporter will rely on the time configuration as a guide on which frames to actually grab during the conversion process. Of course there will be better exporters available in the future…this is just how it was done for the characters in Q3A.

# Animation Config File
The character's animations are controlled by an 'animation.cfg' file where the model maker specifies reference frames and frame rates. The animation.cfg file is a text file (originally created with MS Excel) which contains the frame and animation sequence data. Place this in the model’s directory. Note, when the modeler is testing the model in Quake III Arena, changes to the animation.cfg can be made without having to re-grab the model…just do a ‘vid_restart’ at the cvar command line prompt.

Edit an animation.cfg file which matches the frame/animation sequences and place it in the character's directory. Each animation can have different frame rates that the modeler can tweak, save out in the animation.cfg, hit 'vid_restart' to see the change right away in the game (no need to re-grab the model). The file for visor is shown here below in it’s entirety. You may clip this portion of the file out and use it as the basis for your own animation files.

////////////////////////////////////////////////////////////////////////////////

// animation config file

sex m

headoffset 0 0 0

footsteps normal

// first frame, num frames, looping frames, frames per second

0 30 0 25 // BOTH_DEATH1

29 1 0 25 // BOTH_DEAD1

30 30 0 25 // BOTH_DEATH2

59 1 0 25 // BOTH_DEAD2

60 30 0 25 // BOTH_DEATH3

89 1 0 25 // BOTH_DEAD3

90 40 0 20 // TORSO_GESTURE

130 6 0 15 // TORSO_ATTACK (MUST NOT CHANGE -- hand animation is synced to this)

136 6 0 15 // TORSO_ATTACK2 (MUST NOT CHANGE -- hand animation is synced to this)

142 5 0 20 // TORSO_DROP (MUST NOT CHANGE -- hand animation is synced to this)

147 4 0 20 // TORSO_RAISE (MUST NOT CHANGE -- hand animation is synced to this)

151 1 0 15 // TORSO_STAND

152 1 0 15 // TORSO_STAND2

153 8 8 20 // LEGS_WALKCR

161 12 12 20 // LEGS_WALK

173 9 9 18 // LEGS_RUN

182 10 10 20 // LEGS_BACK

192 10 10 15 // LEGS_SWIM

202 8 0 15 // LEGS_JUMP

210 1 0 15 // LEGS_LAND

211 8 0 15 // LEGS_JUMPB

219 1 0 15 // LEGS_LANDB

220 10 10 15 // LEGS_IDLE

230 10 10 15 // LEGS_IDLECR

240 7 7 15 // LEGS_TURN

//////////////////////////////////////////////////////////////////

# The Conversion Process
The models need to be run through id’s custom md3 conversion/'grabber' program. The program uses the information in the Quake Data text file ([filename].qdt) to grab and convert the 3dsMax files.

= 10.1 The Conversion File =
Create a “Quake Data” text file for the model with the extension “.qdt”. The contents for our [character].qdt file would read something like:

$asecanimconvert models/players/[character]/[character].ase -playerparms 92 155

$asecanimconvert models/players/[character]/[character]_1.ase -lod 1 -playerparms 92 155

$asecanimconvert models/players/[character]/[character]_2.ase -lod 2 -playerparms 92 155

== 10.1.1 “$asecanimconvert” ==
This is the grrabber program executable.

== 10.1.2 “models/players/[character]/[character].ase” ==
This is the path to the model’s .ase file. The program looks for files starting in your Quake3\baseq3 directory.

== 10.1.3 “-lod 1” or “-lod 2” ==
This tells the converter that this is the first level of reduced detail for the model. The value “-lod 2” is for the second, or lowest level of detail for the model.

== 10.1.3 “-playerparms 92 155” ==
This tells the converter which frame the upper body anims only start (first value) and which frame the lower body only anims start (second value). The numbers here are only used as examples

'''''10.2 Run the Conversion'''''

When the qdt file is set up correctly, run the grabber by opening MSDOS command prompt, going to the quake3 directory containing the model files and typing in 'q3data [character].qdt'

''' 11. Review the Model'''

Load up Quake 3 Arena. Go to map Q3DM0 (or any map containing a mirror). Bring down the console and type “\model [character name]”. Hit your Show Score key (default is TAB). You should see your new model here. Tweak the frame rates in your animation.cfg file and save them. Type in “\vid_restart” on the console and hit enter to see the changes.

PolycountOldTOC

2006-06-09T06:09:56Z

VitoMiliano: All Quake 2 stuff done

__NOTOC__
<s> This was thrilling to compile. </s> This is ongoing thrills to convert to nice clean wiki formatting.

r13 has ranked pages to be converted in priority order. Pages that are crossed out and have a link next to them are ones that I have copy and pasted into the wiki. '''THEY ARE NOT DONE BEING CONVERTED YET.''' New pages should be made in a new hierarchy; "Old Site Whatever" is not where things should stay. Most are in disgusting auto-HTML-to-wiki markup, some are in a terrible wiki-but-not text format. You (whoever is doing this) must go through each page and verify each link. If a link is dead, Google search to try and find it again. If it's really gone, check the internet archive for it and make a page for it here, including salvaging any images you can. Some links go to other Polycount pages; find the wiki page that replaced that link and correct the link (unless it's a later priority, in which case leave it or make a placeholder wiki page and note that in the list). You also need to go through and clean up all the wiki formatting: it's been converted automatically from the original HTML, so it is really digusting, or it's just plain text, in which case it needs to be formatted in the first place. Some pages have duplicate information. Others are totally outdated and need to be rewritten. Still others need to be combined with existing resources on the site or with other pages. These pages should be nice and clean and mostly plain text so we can put them on the main Polycount site again. That is all.

Please keep things in the list format. Dynamic pages that will be difficult to redirect properly are in italics.

= General Links =
* Poll (poll/poll.shtml) X
* ''News archives'' (news/newsarchives.asp)
* ''News search'' (news/newsarchives.asp?function=search&advanced=1)
* <s> Contact (contacts/index.shtml) {1} </s> [[OldSiteContact]]
* Polycount for PalmOS (news/pqa.zip) X
* Links (links/index.shtml) {2}
* <s> Credits (credits/index.shtml) {1} this should be merged with the contact page </s> [[OldSiteCredits]]
= Download Database =
* ''UT2004 Models, UT2004 Vehicles, UT2003 Models, Quake 3 Models, UT Models, JKA Models, JK2 Models, GTA3 Models, Serious Sam Models, Quake 2 Models, Q3 Map Models, TA Team Models, TA Head Models, Elite Force Models, Half-Life Models, Heretic2 Models, [[CounterStrike]] Models, The Sims Models, Kingpin Models'' (downloads/ and downloads/index.asp?game=##&sort=date&order=DESC) {2}
= Other Models and Skins =
* Q3 Weapon Models (q3weapons/q3weapons-index.shtml) {3}
* HL Weapon Models (hlweapons/hlweapons-index.shtml) {3}
* UT2003 Accessories (dynamic.gamespy.com/~polycount/skins/ut2003skin-index.shtml wtf?) {3}
* Quake 2 Accessories (skins/q2skin-index.shtml) {3}
* Quake 3 Accessories (skins/q3skin-index.shtml) {3}
* Unreal T Accessories (skins/utskin-index.shtml) {3}
* Half-Life Accessories (skins/hlskin-index.shtml) {3}
* Rune Accessories (skins/runeskin-index.shtml) {3}
* Sims Accessories (skins/simskin-index.shtml) {3}
* Accessory Top-Picks (skins/top-picks/top-picks.shtml) {3} potentially X
* Top-Packs (skins/top-picks/top-packs/top-packs.shtml {3} potentially X
= Resources =
* <s> Resources (resources/index.shtml) {1} we should be able to get alot of the heavy lifting here from the community </s> [[OldSiteResources]]

Under Resources, there are these directories and significant files. Directories without any sub-content just have an index.shtml file in them listing resources elsewhere on the net. Most directories also have lots of other directories with supporting files, like images and stuff, which aren't listed for brevity.

* avp2 {3}
** index.shtml
** tutorials
*** talonengine
**** talonenginetut.shtml
* bandw {3} {i} wtf is this? Black and White
* chat-rooms {2}
** chat-index.shtml
** 2design X
*** 2design.shtml
* model_design
** model_design.shtml
* modjobs X
** modjobs.shtml
* drakan {3}
** index.shtml
** gfx
*** JSheffield.zip
* eliteforce {3}
** index.shtml
** tutorials.shtml
** tutorials
*** q3-ef
**** Q3AEF.shtml
* <s> FAQ-genera {1} probably needs reviewl </s>
** <s> faq-general-index.shtml</s> [[OldSiteResourcesFaqGeneral]]
* <s> general {1} </s> [[OldSiteResourcesGeneral]]
** misc {i} sunstorm?
*** sunstorm.shtml
* <s> tools {1} </s>
** <s> infografica.shtml </s> [[OldSiteResourcesGeneralToolsInfografica]]
** <s> polychop </s>
*** <s> gdmag.pdf </s> [[OldSiteResourcesGeneralToolsPolyChop]]
* tutorials {2}
** ALPHAWolf_Tut01
*** Low<code><nowiki></nowiki></code>Poly<code><nowiki></nowiki></code>Characters.shtml
* cswingstut
** cswingstut.shtml
* Hitman<code><nowiki></nowiki></code>Daz_Tut01
** Digital<code><nowiki></nowiki></code>Painting.shtml
* Model-unwrap
** model-unwrap.shtml
** model-unwrap-pic1.shtml
** model-unwrap-pic2.shtml
** model-unwrap-pic3.shtml
** model-unwrap-pic4.shtml
** model-unwrap-pic5.shtml
* NURBS-mapping
** Nurbs-mapping.shtml
** tutorial.html
** vrml1.html
** vrml2.html
** vrml3.html
* Shine_Tut03
** Poly<code><nowiki></nowiki></code>Reduce.shtml
* Shine_Tut04
** Making a Head.shtml
* Shine_Tut05
** Setup Bones Part1.shtml
* Surface<code><nowiki></nowiki></code>Tools
** Surface Tools for Low Poly Modeling2.doc
** Surface<code><nowiki></nowiki></code>Tools.shtml
** Surface<code><nowiki></nowiki></code>Tools-mts.shtml
* UVWunwrap
** UVWunwrap.shtml
* ASC_Export_Tut01.shtml
** Shine_Tut01.shtml
** Shine_Tut02.shtml
* <s> video_tutorials {1} </s>
** <s> video-tut-list.shtml </s> [[OldSiteResourcesGeneralVideoTutorials]]
* <s> apps.shtml {1} </s> [[OldSiteResourcesGeneralApplications]]
** <s> genmisc.shtml {1} </s> [[OldSiteResourcesGeneralMiscellaneous]]
** index.shtml
** <s> lightwave.shtml {1} </s> [[OldSiteResourcesGeneralLightwave]]
** <s> max.shtml {1} </s> [[OldSiteResourcesGeneralMax]]
** <s> maya.shtml {1} </s> [[OldSiteResourcesGeneralMaya]]
** <s> milkshape.shtml {1} </s> [[OldSiteResourcesGeneralMilkshape]]
** <s> misc.shtml {1} </s> "Sorry, I had something here, but it turned out to be illegal."
** <s> modelanim.shtml {1} </s> [[OldSiteResourcesGeneralModelingAndAnimation]]
** nst.shtml {3}
** q2m.shtml {3}
** <s> skinning.shtml {1} </s> [[OldSiteResourcesGeneralSkinning]]
** <s> tools.shtml {1} </s> [[OldSiteResourcesGeneralTools]]
** tutindex.shtml
** tutorials.shtml
* gfx (looks like game logos for pages maybe) {i} i suspect it is, thats what i think its a dup of that other directory
* <s>glossary (24 pages of definitions plus images) {1} </s> http://nathan.perilith.com/~vito/oldpolycount/glossary/
* <s> glossary2 (only one glossary page, but lots of examples files) {1} can we consolidate these? </s> http://nathan.perilith.com/~vito/oldpolycount/glossary2/glossary.html
* gta3 {3}
* halflife {2}
** index.shtml
** tools.shtml
** tutorials.shtml
** tutorials (directory with 20 pages of modeling tutorials plus example content)
* heretic2 {3}
** index.shtml
** tools.shtml
** tutorials.shtml
* jk2 {3}
** index.shtml
** tutorials
*** Model<code><nowiki></nowiki></code>Tutorial (eight files under here making this up)
*** jk2_model_construction.shtml
* kingpin {3}
** tools
*** framelist.shtml
*** tools.shtml
* index.shtml
** Kingpin-animations.html
* lithtech {3}
** tutorials
*** lithtech_primer.shtml
* index.shtml
** tools.shtml
** tutorials.shtml
* manual (how to review a model?) {i} it may go X
* nolf {3}
* quake {2}
** FAQ.shtml
** index.shtml
** tools.shtml
** tutorials.shtml
* <s> quake2 {1} </s>
** <s> tools </s>
*** <s> Prefabs </s>
**** <s> Alx_Prefabs-info.shtml </s> [[OldSiteResourcesQuake2ToolsPrefabsAlx]]
**** <s> Hunter_Prefabs-info.shtml </s> [[OldSiteResourcesQuake2ToolsPrefabsHunter]]
** <s> Testbox </s>
*** <s> testbox.shtml </s> [[OldSiteResourcesQuake2ToolsTestbox]]
* <s> tutorials </s>
** <s> NGLV </s> [[OldSiteResourcesQuake2TutorialsNglv]]
** <s> NST_Tut01 </s> [[OldSiteResourcesQuake2TutorialsNstTut1]]
** <s> Custom VWEP.shtml </s> [[OldSiteResourcesQuake2TutorialsCustomVwep]]
** <s> NST_Retro<code><nowiki></nowiki></code>Map.shtml </s> [[OldSiteResourcesQuake2TutorialsNstRetroMap]]
** <s> Weapon Skin Linking.shtml </s> [[OldSiteResourcesQuake2WeaponSkinLinking]]
* <s> FAQ.shtml </s> [[OldSiteResourcesQuake2Faq]]
** <s> FAQ-stecki.shtml </s> [[OldSiteResourcesQuake2PpmTroubleshooting]]
** <s> index.shtml </s> [[OldSiteResourcesQuake2]]
** <s> md2text.txt </s> [[OldSiteResourcesQuake2Md2ReadmeTemplate]]
** <s> q2frameslist.shtml </s> [[OldSiteResourcesQuake2FramesList]]
** <s> tools.shtml </s> [[OldSiteResourcesQuake2Tools]]
** <s> tutorials.shtml </s> [[OldSiteResourcesQuake2Tutorials]]
* quake3 {1}
** Model_Doc
*** Model_manual_ps.htm
* Shader_Doc
** Q3<code><nowiki></nowiki></code>Ashader_manual.htm
* tools
** tutorials (lots of files below these, ugh)
*** josh
*** max-to-q3
*** MAX-to-q3data
*** Skin-shader
*** Sound<code><nowiki></nowiki></code>Pak
*** Steed-Tut
* index.shtml
** md3text.txt
** tools.shtml
** tutorials.shtml
* rune {3}
** tutorials
*** lodsettings
**** runetut-lodsettings.shtml
* index.shtml
* sims {3}
** index.shtml
** tools.shtml
** tutorials.shtml
* ssam {3}
* thps {3} {i}
* tribes {3}
** index.shtml
** tools.shtml
** tutorials.shtml
* unreal {2}
** tools
** tutorials (lots of files in these subdirs)
*** lodsettings
*** mage
*** pix
*** sounds
*** umod
*** umod-backup
*** UTut01.shtml
*** UTut02.shtml
*** UTut03.shtml
*** UTut04.shtml
*** UTut05.shtml
*** UTut06.shtml
*** Utut07.shtml
* index.shtml
** tools.shtml
** tutorials.shtml
** UTtut-mainpage.shtml
** UTtut-part5.shtml
* ut2003 {1}
** tutorials
*** backups (this might just be backup content, not sure, something about Intertwined)
*** ut2mod
*** pushing_tutorial.shtml
* index.shtml
** tools.shtml
** tutorials.shtml
Also what I'd consider resources are:

* Good, Bad and Ugly (skins/gbu/* with eight article directories under it) {2}
* Skin news archives (skins/archived-news/* with 30 pages of news under it) {i} no idea
* Articles (ten article directories below that:) {2}
** animation-tips
** BnW<code><nowiki></nowiki></code>interview
** chiq_interview_012602
** chrisbruce_072002
** Gwot062k2
** max3preview
** q3-model-preview
** Steed-gdc99
** Steed-Interview
** Steed-Interview-2
* Subdermal (six pages and a contest) {2}

= Not Linked To =
* [[AskDev]] (ask a developer column?) X this didnt pan out. a dev house wanted to help just answer questions. But pulled out right as we set it all up.
* docs/gamespace_release.zip X
* misc
** Discreet_QCon2k1 {3} {i} needs review
** e32k4 {3} {i} needs review
** gfx {i} is this just a directory full of original polycount gfx?
** id-model-renders {3}
** pimps {3} {i} needs review
** 12-3action.htm {3} {i} needs review
** gamespy-broadcastkey.txt X
** lead_action_designer.doc X
** micro-forte-syd-jobdoc.shtml X
** stuff.htm {3} {i} needs review
** Unreal_Coach_jobpost_053104.doc X
* modeloftheweek X
* modelpacks {3}
* paintchat {2} conditional that we can get it working again, free/cheap. if not... X
* previews X
** nicknacks X
* reviewlists X
* skindom (woah nelly tons of stuff here) {3}
* cutedoll.shtml (contest?) {3} archive purposes only
* info (actual static model info files, non-db) {2} after database
* reviews (actual static model review files, non-db) {2} after database

OldSiteResourcesQuake2Tools

2006-06-09T06:09:33Z

VitoMiliano:

__NOTOC__
'''Quake2 Tools'''

[http://asp.planetquake.com/dl/dl.asp?q2pmp/q2_source.zip ID's Quake 2 Utilities]
The source code and utilities to make all your quake 2 bells and whistles. Don't leave home without them.

[http://asp.planetquake.com/dl/dl.asp?q2pmp/NSTv09b3.zip NPherno's Skin Tool, version 0.9 beta 3]
The best skin painter and skin vert layout program around. A little learning curve with the advanced features, but once you see yourself painting directly on your model, you'll detail that old copy of Paint Shop Pro. This program will of course allow you to paint on the model, but it also allows you to pull the faces off a new model and arrange them on the 2d skin for optimization and production. I can't say enough about this program. It's simply the best. You'll find new betas of the final 1.0 version being offered in the messageboards.

[tutorials/NGLV/NGLV.shtml NPherno's GL Viewer]
Tools needed for this program: A Quake 2 model, A video car with good Open GL support, Skins to put on the model, & Time and patience.

'''Overview:''' So now you're asking, "What is this thing and why should I use it?" Well that's understandable, plenty of people use Skinview and find this sort of thing useless. Fine, this app is about creating some excellent views of your model with colored lighting and a 4 pass rendering system. Yep, that means four skins per model. This is what id has say will be available to us for Quake3 models. If it doesn't happen for Q3, it is somewhat already part of Half Life, which does offer specularity texture maps for the models. So you can sort of "practice" now plus getting some superb images for your models which is always an excellent thing.

'''[http://pakrat.fragland.net/ PakRat]''' by [mailto:naughton@mac.com Tom Naughton]
[[PakRat]] is a program that displays MDL, MD2, and MD3 models and soon Quake 3 maps. You can drag textures from any paint program and drop them on any mesh (great for skinning). It also sports drag and drop MD3 assembly. It's free, open source, under active development, and Mac only.

[http://grad.qeradiant.com/skined/ SkinEd]
A nice skinning tool similar to NST, but concentrates on just painting the skin. Even does a nice 3d view as well to help you look around it. Works for Quake2 and Unreal.

[http://asp.planetquake.com/dl/dl.asp?q2pmp/SkinView43.zip SkinView Mod 4.3] by [http://telefragged.com/skinview/ The Skinview Team]
This is a very nice tool for model authors and skinners who are worried on how their models will look in the game. This tool will load up your model and skin and display it while its cycling through a single animation. It also shows it off in several different lights and settings. It's a invaluable tool. I highly recommend everyone working on a project to take look at your work in this at least once to see what to expect. Here's [http://telefragged.com/skinview/ a link to the offical site] so you can read about it while downloading it.

[http://www.swissquake.ch/chumbalum-soft/ chUmbaLum sOft's Quake2 Model Viewer]
Features/Options: Player model browser, ( browse through player models and double-click to load them ) modified/improved pak file loading, ( double-click to load, or right-click for a popupmenu ), and a skin loading bug for pcx files which had a wrong header has been fixed.

[http://asp.planetquake.com/dl/dl.asp?q2pmp/q2mdlr9b.zip Q2 Modeler v.9b] by [mailto:phillip_martin@optusnet.com.au Philip Martin]
'''[http://www.eldermage.com/dl/q2mdl911.zip Updated to v.911b]''' by [mailto:jaimi@eldermage.com Jaimi McEntire]
A free modeler to make your models with. Many of the models on this site were modeled using this tool. This program is an invaluable tool to the modelers of the community, both the beginner who can use this tool alone to create their models and the advanced who can bring the models from other programs to here for compiling and skin generation [I personally couldn't do reviews or my own models with out it.] '''Note''': Version .9b was thought to be the final version of the tool. The original author has stopped development on it, but another brave soul, [mailto:jaimi@eldermage.com Jaimi McEntire], has picked up the torch, and will lead it once again to glory. Jaimi has also updated it to [http://www.eldermage.com/dl/q2mdl911.zip version .911b]. Also, here's the [http://asp.planetquake.com/dl/dl.asp?q2pmp/MDL.HLP Help file for latest version] (place in the directory with the rest and it should work fine).

[http://www.planetquake.com/qview/ QView] by [mailto:lonerunner@planetquake.com LoneRunner]
QView is a small easy and free viewer for anybody who like to view models from games based on '''any''' Quake engine. A great list of features, and available source code. Definitely a good one to check out. Word them up, yo.

'''[http://skynet.telefragged.com/ MAX to md2 Exporter]'''
A new plugin for 3D Studio MAX has arrived in alpha form. It's a MAX to md2 exporter, similar to the [http://home.earthlink.net/~benthroop/ QTiP] plugin. It's being produced by the throbbing hunks of manly loving on the [http://skynet.telefragged.com/ The Skynet Project: Tactical Combat Simulation] page. It was originally going to be used for their Terminator based Q2 mod, which is neither Q2 nor Terminator based, because... well they state the reasons why. Here's a cut, well more a full copy of the all the info they have listed about the plugin on their site. "Max to Md2 is plugin for 3D Studio MAX 2.x. It imports & exports MD2's into 3D Studio MAX mesh or NURBS format."

[tools/testbox/testbox.shtml Test Box] by [mailto:wrath@planetquake.com Wrath]
This is actually a cube model with the entire Quake 2 palette mapped onto each side. Meant for model and skin authors to get a feel for what their colors are going to do in game as Open GL can surprise a few people when they see what happens to their perfect skins.

[tools/Prefabs/Alx_Prefabs-info.shtml Prefabs ]by [mailto:BigRocket@juno.com Big Rocket]
A series of prefab primitive objects that you can use to help start a model. Very useful in conjunction with model editing programs such as Quake 2 Modeler that doesn't offer primitive creation built in.

[tools/Prefabs/Hunter_Prefabs-info.shtml More Prefabs ]by [mailto:Hunter@polycount.com Hunter]
Yet another series of prefab primitive objects. Basically a larger selection of Primative shapes at your disposal, in creating your own PPMs for Quake 2, 3 etc.. (Comes in .md2 and .AQM formats)

[http://asp.planetquake.com/dl/dl.asp?q2pmp/iouv.zip IOUV Max Script v0.7] by [mailto:benny@mail.bip.net Elmek]
This script allows you to bring a skin from a Quake2 model into 3DStudio MAX for texture mapping. The new version will also allow you to export the skin back out. This lets you use some of the more advanced skin editing plugin tools that are available for 3DStudio MAX. The zip file contains an extensive how-to text that should get even the most timid modelers through the procedure. [Although if you're using MAX you can't be too timid :) ]

[http://home.earthlink.net/~benthroop/ QTiP 1.2]
Plugin for 3D Studio Max that will export directly to the md2 format. Its a very nice program, but has a few bugs in it still. The team doing it still offer a little support, but for the most part have frozen development of the plugin as it stands now. It comes in 2 flavors for MAX 1.x and 2.x users so make sure you grab what you need. The site also has a full tutorial as well.

'''[http://www.3dmatrix.com/ qME]
''' A nice basic model creation utility that can be used for Quake 1 and 2. It comes with a variety of tools, but most have found it is a limiting program. It's an excellent place to start though, the demo is free and will let you do models up to 30 frames. The final version was 30 dollars to purchase with no restrictions built into it. You'll need to get it from the 3D Matrix site as they do the selling of it.

'''[http://asp.planetquake.com/dl/dl.asp?q2pmp/q2ranger.zip Ranger or Q2 Ranger]''' by [http://mondomed.com/ Mondo Media]
A nice MAX script that allows you to select different active ranges in an single MAX file. An application of this is to only work and view a select number of frames in a long animation, say like the Q2 model format. The zip comes with pre-made ranges for the Q2 frame list. Check Mondo's site for a ton of nice helper tools like this.

OldSiteResourcesQuake2FramesList

2006-06-09T06:07:56Z

VitoMiliano:

__NOTOC__
'''Welcome To The HTML Version Of The Q2 198 Commandments..'''

Below you'll find the the list of all the frames in order as they need to appear in your own model so they will match the animation commands from the game engine correctly. This is a modified version of the original that I've provided a link below to. The only differences is that: I've renumbered the last column to accurately display the number order, rearranged the different sections into the correct order, pulled 2 extra frames from the original that did not appear in the final models, stripped away all the extra monster and player animations that we're not concerned with. This is not meant to say Mr. Steed's original was bad. He made it and was able to decipher through any inaccuracies that were in there. I've tried to straighten it up, so that new modeler's can use it immediately.

[http://asp.planetquake.com/dl/dl.asp?q2pmp/q2an1895.xls Paul Steed's Original Spreadsheet]

[http://asp.planetquake.com/dl/dl.asp?q2pmp/male2.xls rogue13's modified version]

{| border="1" cellpadding="2" cellspacing="0"
|-
|align="center" < height="9px">|'''''ANIMATION'''''
|align="center" < width="61px" height="9px">|'''FRAME #'''
|align="center" < width="211px" height="9px">|'''OFFSET'''
|align="center" < width="213px" height="9px">|'''ACTION DESCRIPTION'''
|align="center" < width="83px" height="9px">|'''FILE NAME'''
|align="center" < width="66px" height="9px">|'''NOTES'''
|-
|align="center" |'''''STAND'''''
|align="center" < width="61px">|1
|<width="211px" |40>|
|align="center" < width="213px">|idle
|align="center" < width="83px">|stand01
|align="center" < width="66px">|1
|-
|rowspan="39" |
|align="center" < width="61px">|2
|align="center" < width="213px">|idle
|align="center" < width="83px">|stand02
|align="center" < width="66px">|2
|-
|align="center" < width="61px">|3
|align="center" < width="211px">|idle
|align="center" < width="83px">|stand03
|align="center" < width="66px">|3
|-
|align="center" < width="61px">|4
|align="center" < width="211px">|idle
|align="center" < width="83px">|stand04
|align="center" < width="66px">|4
|-
|align="center" < width="61px">|5
|align="center" < width="211px">|idle
|align="center" < width="83px">|stand05
|align="center" < width="66px">|5
|-
|align="center" < width="61px">|6
|align="center" < width="211px">|idle
|align="center" < width="83px">|stand06
|align="center" < width="66px">|6
|-
|align="center" < width="61px">|7
|align="center" < width="211px">|idle
|align="center" < width="83px">|stand07
|align="center" < width="66px">|7
|-
|align="center" < width="61px">|8
|align="center" < width="211px">|idle
|align="center" < width="83px">|stand08
|align="center" < width="66px">|8
|-
|align="center" < width="61px">|9
|align="center" < width="211px">|idle
|align="center" < width="83px">|stand09
|align="center" < width="66px">|9
|-
|align="center" < width="61px">|10
|align="center" < width="211px">|idle
|align="center" < width="83px">|stand10
|align="center" < width="66px">|10
|-
|align="center" < width="61px">|11
|align="center" < width="211px">|idle
|align="center" < width="83px">|stand11
|align="center" < width="66px">|11
|-
|align="center" < width="61px">|12
|align="center" < width="211px">|idle
|align="center" < width="83px">|stand12
|align="center" < width="66px">|12
|-
|align="center" < width="61px">|13
|align="center" < width="211px">|idle
|align="center" < width="83px">|stand13
|align="center" < width="66px">|13
|-
|align="center" < width="61px">|14
|align="center" < width="211px">|idle
|align="center" < width="83px">|stand14
|align="center" < width="66px">|14
|-
|align="center" < width="61px">|15
|align="center" < width="211px">|idle
|align="center" < width="83px">|stand15
|align="center" < width="66px">|15
|-
|align="center" < width="61px">|16
|align="center" < width="211px">|idle
|align="center" < width="83px">|stand16
|align="center" < width="66px">|16
|-
|align="center" < width="61px">|17
|align="center" < width="211px">|idle
|align="center" < width="83px">|stand17
|align="center" < width="66px">|17
|-
|align="center" < width="61px">|18
|align="center" < width="211px">|idle
|align="center" < width="83px">|stand18
|align="center" < width="66px">|18
|-
|align="center" < width="61px">|19
|align="center" < width="211px">|idle
|align="center" < width="83px">|stand19
|align="center" < width="66px">|19
|-
|align="center" < width="61px">|20
|align="center" < width="211px">|idle
|align="center" < width="83px">|stand20
|align="center" < width="66px">|20
|-
|align="center" < width="61px">|21
|align="center" < width="211px">|idle
|align="center" < width="83px">|stand21
|align="center" < width="66px">|21
|-
|align="center" < width="61px">|22
|align="center" < width="211px">|idle
|align="center" < width="83px">|stand22
|align="center" < width="66px">|22
|-
|align="center" < width="61px">|23
|align="center" < width="211px">|idle
|align="center" < width="83px">|stand23
|align="center" < width="66px">|23
|-
|align="center" < width="61px">|24
|align="center" < width="211px">|idle
|align="center" < width="83px">|stand24
|align="center" < width="66px">|24
|-
|align="center" < width="61px">|25
|align="center" < width="211px">|idle
|align="center" < width="83px">|stand25
|align="center" < width="66px">|25
|-
|align="center" < width="61px">|26
|align="center" < width="211px">|idle
|align="center" < width="83px">|stand26
|align="center" < width="66px">|26
|-
|align="center" < width="61px">|27
|align="center" < width="211px">|idle
|align="center" < width="83px">|stand27
|align="center" < width="66px">|27
|-
|align="center" < width="61px">|28
|align="center" < width="211px">|idle
|align="center" < width="83px">|stand28
|align="center" < width="66px">|28
|-
|align="center" < width="61px">|29
|align="center" < width="211px">|idle
|align="center" < width="83px">|stand29
|align="center" < width="66px">|29
|-
|align="center" < width="61px">|30
|align="center" < width="211px">|idle
|align="center" < width="83px">|stand30
|align="center" < width="66px">|30
|-
|align="center" < width="61px">|31
|align="center" < width="211px">|idle
|align="center" < width="83px">|stand31
|align="center" < width="66px">|31
|-
|align="center" < width="61px">|32
|align="center" < width="211px">|idle
|align="center" < width="83px">|stand32
|align="center" < width="66px">|32
|-
|align="center" < width="61px">|33
|align="center" < width="211px">|idle
|align="center" < width="83px">|stand33
|align="center" < width="66px">|33
|-
|align="center" < width="61px">|34
|align="center" < width="211px">|idle
|align="center" < width="83px">|stand34
|align="center" < width="66px">|34
|-
|align="center" < width="61px">|35
|align="center" < width="211px">|idle
|align="center" < width="83px">|stand35
|align="center" < width="66px">|35
|-
|align="center" < width="61px">|36
|align="center" < width="211px">|idle
|align="center" < width="83px">|stand36
|align="center" < width="66px">|36
|-
|align="center" < width="61px">|37
|align="center" < width="211px">|idle
|align="center" < width="83px">|stand37
|align="center" < width="66px">|37
|-
|align="center" < width="61px">|38
|align="center" < width="211px">|idle
|align="center" < width="83px">|stand38
|align="center" < width="66px">|38
|-
|align="center" < width="61px">|39
|align="center" < width="211px">|idle
|align="center" < width="83px">|stand39
|align="center" < width="66px">|39
|-
|align="center" < width="61px">|'''40'''
|align="center" < width="211px">|'''default'''
|align="center" < width="83px">|'''stand40'''
|align="center" < width="66px">|40
|-
|align="center" < height="20px">|'''''ANIMATION'''''
|align="center" < width="61px" height="20px">|'''FRAME #'''
|align="center" < width="211px" height="20px">|'''OFFSET'''
|align="center" < width="213px" height="20px">|'''ACTION DESCRIPTION'''
|align="center" < width="83px" height="20px">|'''FILE NAME'''
|align="center" < width="66px" height="20px">|'''NOTES'''
|-
|align="center" |'''''RUN'''''
|align="center" < width="61px">|1
|<width="211px" |6>|
|align="center" < width="213px">|runs
|align="center" < width="83px">|run1
|align="center" < width="66px">|3
|-
|rowspan="5" |
|align="center" < width="61px">|'''2'''
|align="center" < width="213px">|'''plants foot'''
|align="center" < width="83px">|'''run2'''
|align="center" < width="66px">|4
|-
|align="center" < width="61px">|3
|align="center" < width="211px">|runs
|align="center" < width="83px">|run3
|align="center" < width="66px">|5
|-
|align="center" < width="61px">|4
|align="center" < width="211px">|runs
|align="center" < width="83px">|run4
|align="center" < width="66px">|6
|-
|align="center" < width="61px">|'''5'''
|align="center" < width="211px">|'''plants foot'''
|align="center" < width="83px">|'''run5'''
|align="center" < width="66px">|7
|-
|align="center" < width="61px">|6
|align="center" < width="211px">|runs
|align="center" < width="83px">|run6
|align="center" < width="66px">|8
|-
|align="center" < height="20px">|'''''ANIMATION'''''
|align="center" < width="61px" height="20px">|'''FRAME #'''
|align="center" < width="211px" height="20px">|'''OFFSET'''
|align="center" < width="213px" height="20px">|'''ACTION DESCRIPTION'''
|align="center" < width="83px" height="20px">|'''FILE NAME'''
|align="center" < width="66px" height="20px">|'''NOTES'''
|-
|align="center" |'''''ATTACK'''''
|align="center" < width="61px">|'''1'''
|<width="211px" |8>|
|align="center" < width="213px">|'''POW (-6.4, -10.3, 28.0)'''
|align="center" < width="83px">|'''attack1'''
|align="center" < width="66px">|2
|-
|rowspan="7" |
|align="center" < width="61px">|2
|align="center" < width="213px">|recoils
|align="center" < width="83px">|attack2
|align="center" < width="66px">|3
|-
|align="center" < width="61px">|3
|align="center" < width="211px">|reaches up to cock weapon
|align="center" < width="83px">|attack3
|align="center" < width="66px">|4
|-
|align="center" < width="61px">|4
|align="center" < width="211px">|pulls slide back
|align="center" < width="83px">|attack4
|align="center" < width="66px">|5
|-
|align="center" < width="61px">|'''5'''
|align="center" < width="211px">|'''slide back'''
|align="center" < width="83px">|'''attack5'''
|align="center" < width="66px">|6
|-
|align="center" < width="61px">|'''6'''
|align="center" < width="211px">|'''slide forward'''
|align="center" < width="83px">|'''attack6'''
|align="center" < width="66px">|7
|-
|align="center" < width="61px">|7
|align="center" < width="211px">|returns to default
|align="center" < width="83px">|attack7
|align="center" < width="66px">|8
|-
|align="center" < width="61px">|'''8'''
|align="center" < width="211px">|'''default'''
|align="center" < width="83px">|'''attack8'''
|align="center" < width="66px">|9
|-
|align="center" |'''''ANIMATION'''''
|align="center" < width="61px">|'''FRAME #'''
|align="center" < width="211px">|'''OFFSET'''
|align="center" < width="213px">|'''ACTION DESCRIPTION'''
|align="center" < width="83px">|'''FILE NAME'''
|align="center" < width="66px">|'''NOTES'''
|-
|align="center" |'''''PAIN 1'''''
|align="center" < width="61px">|1
|<width="211px" |4>|
|align="center" < width="213px">|'''OUCH!'''
|align="center" < width="83px">|pain101
|<width="66px" |4>|
|-
|rowspan="3" |
|align="center" < width="61px">|2
|align="center" < width="213px">|recovers
|align="center" < width="83px">|pain102
|-
|align="center" < width="61px">|3
|align="center" < width="211px">|default
|align="center" < width="83px">|pain103
|-
|align="center" < width="61px">|4
|align="center" < width="211px">|default
|align="center" < width="83px">|pain104
|-
|align="center" |'''''ANIMATION'''''
|align="center" < width="61px">|'''FRAME #'''
|align="center" < width="211px">|'''OFFSET'''
|align="center" < width="213px">|'''ACTION DESCRIPTION'''
|align="center" < width="83px">|'''FILE NAME'''
|align="center" < width="66px">|'''NOTES'''
|-
|align="center" |'''''PAIN 2'''''
|align="center" < width="61px">|1
|<width="211px" |4>|
|align="center" < width="213px">|'''OUCH!'''
|align="center" < width="83px">|pain201
|<width="66px" |4>|
|-
|rowspan="3" |
|align="center" < width="61px">|2
|align="center" < width="213px">|recovers
|align="center" < width="83px">|pain202
|-
|align="center" < width="61px">|3
|align="center" < width="211px">|default
|align="center" < width="83px">|pain203
|-
|align="center" < width="61px">|4
|align="center" < width="211px">|default
|align="center" < width="83px">|pain204
|-
|align="center" |'''''ANIMATION'''''
|align="center" < width="61px">|'''FRAME #'''
|align="center" < width="211px">|'''OFFSET'''
|align="center" < width="213px">|'''ACTION DESCRIPTION'''
|align="center" < width="83px">|'''FILE NAME'''
|align="center" < width="66px">|'''NOTES'''
|-
|align="center" |'''''PAIN 3'''''
|align="center" < width="61px">|1
|<width="211px" |4>|
|align="center" < width="213px">|'''OUCH!'''
|align="center" < width="83px">|pain301
|<width="66px" |4>|
|-
|rowspan="3" |
|align="center" < width="61px">|2
|align="center" < width="213px">|recovers
|align="center" < width="83px">|pain302
|-
|align="center" < width="61px">|3
|align="center" < width="211px">|default
|align="center" < width="83px">|pain303
|-
|align="center" < width="61px">|4
|align="center" < width="211px">|default
|align="center" < width="83px">|pain304
|-
|align="center" |'''''ANIMATION'''''
|align="center" < width="61px">|'''FRAME #'''
|align="center" < width="211px">|'''OFFSET'''
|align="center" < width="213px">|'''ACTION DESCRIPTION'''
|align="center" < width="83px">|'''FILE NAME'''
|align="center" < width="66px">|'''NOTES'''
|-
|align="center" |'''''JUMP'''''
|align="center" < width="61px">|'''1'''
|<width="211px" |6>|
|align="center" < width="213px">|'''JUMP'''
|align="center" < width="83px">|'''jump1'''
|align="center" < width="66px">|2
|-
|rowspan="5" |
|align="center" < width="61px">|2
|align="center" < width="213px">|airborn
|align="center" < width="83px">|jump2
|align="center" < width="66px">|3
|-
|align="center" < width="61px">|3
|align="center" < width="211px">|airborn
|align="center" < width="83px">|jump3
|align="center" < width="66px">|4
|-
|align="center" < width="61px">|'''4'''
|align="center" < width="211px">|'''LANDS'''
|align="center" < width="83px">|'''jump4'''
|align="center" < width="66px">|5
|-
|align="center" < width="61px">|5
|align="center" < width="211px">|recovers
|align="center" < width="83px">|jump5
|align="center" < width="66px">|6
|-
|align="center" < width="61px">|'''6'''
|align="center" < width="211px">|'''default'''
|align="center" < width="83px">|'''jump6'''
|align="center" < width="66px">|7
|-
|align="center" |'''''ANIMATION'''''
|align="center" < width="61px">|'''FRAME #'''
|align="center" < width="211px">|'''OFFSET'''
|align="center" < width="213px">|'''ACTION DESCRIPTION'''
|align="center" < width="83px">|'''FILE NAME'''
|align="center" < width="66px">|'''NOTES'''
|-
|align="center" |'''''FLIPOFF'''''
|align="center" < width="61px">|1
|<width="211px" |12>|
|align="center" < width="213px">|reaches up for the finger
|align="center" < width="83px">|flip01
|align="center" < width="66px">|2
|-
|rowspan="11" |
|align="center" < width="61px">|2
|align="center" < width="213px">|reaches up for the finger
|align="center" < width="83px">|flip02
|align="center" < width="66px">|3
|-
|align="center" < width="61px">|3
|align="center" < width="211px">|fuck you
|align="center" < width="83px">|flip03
|align="center" < width="66px">|4
|-
|align="center" < width="61px">|4
|align="center" < width="211px">|fuck you
|align="center" < width="83px">|flip04
|align="center" < width="66px">|5
|-
|align="center" < width="61px">|5
|align="center" < width="211px">|fuck you
|align="center" < width="83px">|flip05
|align="center" < width="66px">|6
|-
|align="center" < width="61px">|6
|align="center" < width="211px">|fuck you
|align="center" < width="83px">|flip06
|align="center" < width="66px">|7
|-
|align="center" < width="61px">|7
|align="center" < width="211px">|fuck you
|align="center" < width="83px">|flip07
|align="center" < width="66px">|8
|-
|align="center" < width="61px">|8
|align="center" < width="211px">|fuck you
|align="center" < width="83px">|flip08
|align="center" < width="66px">|9
|-
|align="center" < width="61px">|9
|align="center" < width="211px">|fuck you
|align="center" < width="83px">|flip09
|align="center" < width="66px">|10
|-
|align="center" < width="61px">|10
|align="center" < width="211px">|returns to default
|align="center" < width="83px">|flip10
|align="center" < width="66px">|11
|-
|align="center" < width="61px">|11
|align="center" < width="211px">|returns to default
|align="center" < width="83px">|flip11
|align="center" < width="66px">|12
|-
|align="center" < width="61px">|'''12'''
|align="center" < width="211px">|'''default'''
|align="center" < width="83px">|'''flip12'''
|align="center" < width="66px">|13
|-
|align="center" < height="8px">|'''''ANIMATION'''''
|align="center" < width="61px" height="8px">|'''FRAME #'''
|align="center" < width="211px" height="8px">|'''OFFSET'''
|align="center" < width="213px" height="8px">|'''ACTION DESCRIPTION'''
|align="center" < width="83px" height="8px">|'''FILE NAME'''
|align="center" < width="66px" height="8px">|'''NOTES'''
|-
|align="center" |'''''SALUTE'''''
|align="center" < width="61px">|1
|<width="211px" |11>|
|align="center" < width="213px">|brings arm up
|align="center" < width="83px">|salute01
|align="center" < width="66px">|2
|-
|rowspan="10" |
|align="center" < width="61px">|2
|align="center" < width="213px">|brings arm up
|align="center" < width="83px">|salute02
|align="center" < width="66px">|3
|-
|align="center" < width="61px">|'''3'''
|align="center" < width="211px">|'''SALUTE!'''
|align="center" < width="83px">|'''salute03'''
|align="center" < width="66px">|4
|-
|align="center" < width="61px">|4
|align="center" < width="211px">|holds salute
|align="center" < width="83px">|salute04
|align="center" < width="66px">|5
|-
|align="center" < width="61px">|5
|align="center" < width="211px">|holds salute
|align="center" < width="83px">|salute05
|align="center" < width="66px">|6
|-
|align="center" < width="61px">|6
|align="center" < width="211px">|holds salute
|align="center" < width="83px">|salute06
|align="center" < width="66px">|7
|-
|align="center" < width="61px">|'''7'''
|align="center" < width="211px">|'''pops salute'''
|align="center" < width="83px">|'''salute07'''
|align="center" < width="66px">|8
|-
|align="center" < width="61px">|8
|align="center" < width="211px">|holds
|align="center" < width="83px">|salute08
|align="center" < width="66px">|9
|-
|align="center" < width="61px">|9
|align="center" < width="211px">|returns to default
|align="center" < width="83px">|salute09
|align="center" < width="66px">|10
|-
|align="center" < width="61px">|10
|align="center" < width="211px">|returns to default
|align="center" < width="83px">|salute10
|align="center" < width="66px">|11
|-
|align="center" < width="61px">|'''11'''
|align="center" < width="211px">|'''default'''
|align="center" < width="83px">|'''salute11'''
|align="center" < width="66px">|13
|-
|align="center" |'''''ANIMATION'''''
|align="center" < width="61px">|'''FRAME #'''
|align="center" < width="211px">|'''OFFSET'''
|align="center" < width="213px">|'''ACTION DESCRIPTION'''
|align="center" < width="83px">|'''FILE NAME'''
|align="center" < width="66px">|'''NOTES'''
|-
|align="center" |'''''TAUNT'''''
|align="center" < width="61px">|1
|<width="211px" |17>|
|align="center" < width="213px">|reaches for crotch
|align="center" < width="83px">|taunt01
|align="center" < width="66px">|2
|-
|rowspan="16" |
|align="center" < width="61px">|2
|align="center" < width="213px">|reaches for crotch
|align="center" < width="83px">|taunt02
|align="center" < width="66px">|3
|-
|align="center" < width="61px">|3
|align="center" < width="211px">|grabs crotch
|align="center" < width="83px">|taunt03
|align="center" < width="66px">|4
|-
|align="center" < width="61px">|4
|align="center" < width="211px">|grabs crotch
|align="center" < width="83px">|taunt04
|align="center" < width="66px">|5
|-
|align="center" < width="61px">|5
|align="center" < width="211px">|grabs crotch
|align="center" < width="83px">|taunt05
|align="center" < width="66px">|6
|-
|align="center" < width="61px">|6
|align="center" < width="211px">|grabs crotch
|align="center" < width="83px">|taunt06
|align="center" < width="66px">|7
|-
|align="center" < width="61px">|7
|align="center" < width="211px">|grabs crotch
|align="center" < width="83px">|taunt07
|align="center" < width="66px">|8
|-
|align="center" < width="61px">|'''8'''
|align="center" < width="211px">|'''grabs UP!'''
|align="center" < width="83px">|'''taunt08'''
|align="center" < width="66px">|9
|-
|align="center" < width="61px">|9
|align="center" < width="211px">|grabs crotch
|align="center" < width="83px">|taunt09
|align="center" < width="66px">|10
|-
|align="center" < width="61px">|10
|align="center" < width="211px">|grabs crotch
|align="center" < width="83px">|taunt10
|align="center" < width="66px">|11
|-
|align="center" < width="61px">|11
|align="center" < width="211px">|grabs crotch
|align="center" < width="83px">|taunt11
|align="center" < width="66px">|12
|-
|align="center" < width="61px">|'''12'''
|align="center" < width="211px">|'''grabs UP!'''
|align="center" < width="83px">|'''taunt12'''
|align="center" < width="66px">|13
|-
|align="center" < width="61px">|13
|align="center" < width="211px">|grabs crotch
|align="center" < width="83px">|taunt13
|align="center" < width="66px">|14
|-
|align="center" < width="61px">|14
|align="center" < width="211px">|returns to default
|align="center" < width="83px">|taunt14
|align="center" < width="66px">|15
|-
|align="center" < width="61px">|15
|align="center" < width="211px">|returns to default
|align="center" < width="83px">|taunt15
|align="center" < width="66px">|16
|-
|align="center" < width="61px">|16
|align="center" < width="211px">|returns to default
|align="center" < width="83px">|taunt16
|align="center" < width="66px">|17
|-
|align="center" < width="61px">|'''17'''
|align="center" < width="211px">|'''default'''
|align="center" < width="83px">|'''taunt17'''
|align="center" < width="66px">|18
|-
|align="center" |'''''ANIMATION'''''
|align="center" < width="61px">|'''FRAME #'''
|align="center" < width="211px">|'''OFFSET'''
|align="center" < width="213px">|'''ACTION DESCRIPTION'''
|align="center" < width="83px">|'''FILE NAME'''
|align="center" < width="66px">|'''NOTES'''
|-
|align="center" |'''''WAVE'''''
|align="center" < width="61px">|1
|<width="211px" |11>|
|align="center" < width="213px">|brings arm up to wave
|align="center" < width="83px">|wave01
|align="center" < width="66px">|2
|-
|rowspan="10" |
|align="center" < width="61px">|2
|align="center" < width="213px">|brings arm up to wave
|align="center" < width="83px">|wave02
|align="center" < width="66px">|3
|-
|align="center" < width="61px">|'''3'''
|align="center" < width="211px">|'''waves'''
|align="center" < width="83px">|'''wave03'''
|align="center" < width="66px">|4
|-
|align="center" < width="61px">|'''4'''
|align="center" < width="211px">|'''waves'''
|align="center" < width="83px">|'''wave04'''
|align="center" < width="66px">|5
|-
|align="center" < width="61px">|'''5'''
|align="center" < width="211px">|'''waves'''
|align="center" < width="83px">|'''wave05'''
|align="center" < width="66px">|6
|-
|align="center" < width="61px">|'''6'''
|align="center" < width="211px">|'''waves'''
|align="center" < width="83px">|'''wave06'''
|align="center" < width="66px">|7
|-
|align="center" < width="61px">|7
|align="center" < width="211px">|returns to default
|align="center" < width="83px">|wave07
|align="center" < width="66px">|8
|-
|align="center" < width="61px">|8
|align="center" < width="211px">|returns to default
|align="center" < width="83px">|wave08
|align="center" < width="66px">|9
|-
|align="center" < width="61px">|9
|align="center" < width="211px">|returns to default
|align="center" < width="83px">|wave09
|align="center" < width="66px">|10
|-
|align="center" < width="61px">|10
|align="center" < width="211px">|returns to default
|align="center" < width="83px">|wave10
|align="center" < width="66px">|11
|-
|align="center" < width="61px">|'''11'''
|align="center" < width="211px">|'''default'''
|align="center" < width="83px">|'''wave11'''
|align="center" < width="66px">|12
|-
|align="center" |'''''ANIMATION'''''
|align="center" < width="61px">|'''FRAME #'''
|align="center" < width="211px">|'''OFFSET'''
|align="center" < width="213px">|'''ACTION DESCRIPTION'''
|align="center" < width="83px">|'''FILE NAME'''
|align="center" < width="66px">|'''NOTES'''
|-
|align="center" |'''''POINT'''''
|align="center" < width="61px">|1
|<width="211px" |12>|
|align="center" < width="213px">|raises hand to point
|align="center" < width="83px">|point01
|align="center" < width="66px">|2
|-
|rowspan="11" |
|align="center" < width="61px">|2
|align="center" < width="213px">|raises hand to point
|align="center" < width="83px">|point02
|align="center" < width="66px">|3
|-
|align="center" < width="61px">|3
|align="center" < width="211px">|raises hand to point
|align="center" < width="83px">|point03
|align="center" < width="66px">|4
|-
|align="center" < width="61px">|4
|align="center" < width="211px">|points
|align="center" < width="83px">|point04
|align="center" < width="66px">|5
|-
|align="center" < width="61px">|5
|align="center" < width="211px">|points
|align="center" < width="83px">|point05
|align="center" < width="66px">|6
|-
|align="center" < width="61px">|6
|align="center" < width="211px">|points
|align="center" < width="83px">|point06
|align="center" < width="66px">|7
|-
|align="center" < width="61px">|7
|align="center" < width="211px">|points
|align="center" < width="83px">|point07
|align="center" < width="66px">|8
|-
|align="center" < width="61px">|8
|align="center" < width="211px">|points
|align="center" < width="83px">|point08
|align="center" < width="66px">|9
|-
|align="center" < width="61px">|9
|align="center" < width="211px">|points
|align="center" < width="83px">|point09
|align="center" < width="66px">|10
|-
|align="center" < width="61px">|10
|align="center" < width="211px">|returns to default
|align="center" < width="83px">|point10
|align="center" < width="66px">|11
|-
|align="center" < width="61px">|11
|align="center" < width="211px">|returns to default
|align="center" < width="83px">|point11
|align="center" < width="66px">|12
|-
|align="center" < width="61px">|12
|align="center" < width="211px">|default
|align="center" < width="83px">|point12
|align="center" < width="66px">|13
|-
|align="center" |'''''ANIMATION'''''
|align="center" < width="61px">|'''FRAME #'''
|align="center" < width="211px">|'''OFFSET'''
|align="center" < width="213px">|'''ACTION DESCRIPTION'''
|align="center" < width="83px">|'''FILE NAME'''
|align="center" < width="66px">|'''NOTES'''
|-
|align="center" |'''''CROUCH STAND'''''
|align="center" < width="61px">|1
|<width="211px" |19>|
|align="center" < width="213px">|idle
|align="center" < width="83px">|crstnd01
|align="center" < width="66px">|3
|-
|rowspan="18" |
|align="center" < width="61px">|2
|align="center" < width="213px">|idle
|align="center" < width="83px">|crstnd02
|align="center" < width="66px">|4
|-
|align="center" < width="61px">|3
|align="center" < width="211px">|idle
|align="center" < width="83px">|crstnd03
|align="center" < width="66px">|5
|-
|align="center" < width="61px">|4
|align="center" < width="211px">|idle
|align="center" < width="83px">|crstnd04
|align="center" < width="66px">|6
|-
|align="center" < width="61px">|5
|align="center" < width="211px">|idle
|align="center" < width="83px">|crstnd05
|align="center" < width="66px">|7
|-
|align="center" < width="61px">|6
|align="center" < width="211px">|idle
|align="center" < width="83px">|crstnd06
|align="center" < width="66px">|8
|-
|align="center" < width="61px">|7
|align="center" < width="211px">|idle
|align="center" < width="83px">|crstnd07
|align="center" < width="66px">|9
|-
|align="center" < width="61px">|8
|align="center" < width="211px">|idle
|align="center" < width="83px">|crstnd08
|align="center" < width="66px">|10
|-
|align="center" < width="61px">|9
|align="center" < width="211px">|idle
|align="center" < width="83px">|crstnd09
|align="center" < width="66px">|11
|-
|align="center" < width="61px">|10
|align="center" < width="211px">|idle
|align="center" < width="83px">|crstnd10
|align="center" < width="66px">|12
|-
|align="center" < width="61px">|11
|align="center" < width="211px">|idle
|align="center" < width="83px">|crstnd11
|align="center" < width="66px">|13
|-
|align="center" < width="61px">|12
|align="center" < width="211px">|idle
|align="center" < width="83px">|crstnd12
|align="center" < width="66px">|14
|-
|align="center" < width="61px">|13
|align="center" < width="211px">|idle
|align="center" < width="83px">|crstnd13
|align="center" < width="66px">|15
|-
|align="center" < width="61px">|14
|align="center" < width="211px">|idle
|align="center" < width="83px">|crstnd14
|align="center" < width="66px">|16
|-
|align="center" < width="61px">|15
|align="center" < width="211px">|idle
|align="center" < width="83px">|crstnd15
|align="center" < width="66px">|17
|-
|align="center" < width="61px">|16
|align="center" < width="211px">|idle
|align="center" < width="83px">|crstnd16
|align="center" < width="66px">|18
|-
|align="center" < width="61px">|17
|align="center" < width="211px">|idle
|align="center" < width="83px">|crstnd17
|align="center" < width="66px">|19
|-
|align="center" < width="61px">|18
|align="center" < width="211px">|idle
|align="center" < width="83px">|crstnd18
|align="center" < width="66px">|20
|-
|align="center" < width="61px">|19
|align="center" < width="211px">|idle
|align="center" < width="83px">|crstnd19
|align="center" < width="66px">|21
|-
|align="center" |'''''ANIMATION'''''
|align="center" < width="61px">|'''FRAME #'''
|align="center" < width="211px">|'''OFFSET'''
|align="center" < width="213px">|'''ACTION DESCRIPTION'''
|align="center" < width="83px">|'''FILE NAME'''
|align="center" < width="66px">|'''NOTES'''
|-
|align="center" |'''''CROUCH WALK'''''
|align="center" < width="61px">|'''1'''
|<width="211px" |6>|
|align="center" < width="213px">|'''plants foot'''
|align="center" < width="83px">|'''crwalk1'''
|align="center" < width="66px">|3
|-
|rowspan="5" |
|align="center" < width="61px">|2
|align="center" < width="213px">|walks
|align="center" < width="83px">|crwalk2
|align="center" < width="66px">|4
|-
|align="center" < width="61px">|'''3'''
|align="center" < width="211px">|walks
|align="center" < width="83px">|crwalk3
|align="center" < width="66px">|5
|-
|align="center" < width="61px">|'''4'''
|align="center" < width="211px">|'''plants foot'''
|align="center" < width="83px">|'''crwalk4'''
|align="center" < width="66px">|6
|-
|align="center" < width="61px">|5
|align="center" < width="211px">|walks
|align="center" < width="83px">|crwalk5
|align="center" < width="66px">|7
|-
|align="center" < width="61px">|6
|align="center" < width="211px">|walks
|align="center" < width="83px">|crwalk6
|align="center" < width="66px">|8
|-
|align="center" |'''''ANIMATION'''''
|align="center" < width="61px">|'''FRAME #'''
|align="center" < width="211px">|'''OFFSET'''
|align="center" < width="213px">|'''ACTION DESCRIPTION'''
|align="center" < width="83px">|'''FILE NAME'''
|align="center" < width="66px">|'''NOTES'''
|-
|align="center" |'''''CROUCH ATTACK'''''
|align="center" < width="61px">|'''1'''
|<width="211px" |9>|
|align="center" < width="213px">|'''POW'''
|align="center" < width="83px">|'''crattak1'''
|align="center" < width="66px">|4
|-
|rowspan="8" |
|align="center" < width="61px">|2
|align="center" < width="213px">|recoils
|align="center" < width="83px">|crattak2
|align="center" < width="66px">|5
|-
|align="center" < width="61px">|3
|align="center" < width="211px">|recoils
|align="center" < width="83px">|crattak3
|align="center" < width="66px">|6
|-
|align="center" < width="61px">|4
|align="center" < width="211px">|reaches for slide
|align="center" < width="83px">|crattak4
|align="center" < width="66px">|7
|-
|align="center" < width="61px">|'''5'''
|align="center" < width="211px">|'''pulls slide forward'''
|align="center" < width="83px">|'''crattak5'''
|align="center" < width="66px">|8
|-
|align="center" < width="61px">|'''6'''
|align="center" < width="211px">|'''pulls slide back'''
|align="center" < width="83px">|'''crattak6'''
|align="center" < width="66px">|9
|-
|align="center" < width="61px">|7
|align="center" < width="211px">|returns to default
|align="center" < width="83px">|crattak7
|align="center" < width="66px">|10
|-
|align="center" < width="61px">|8
|align="center" < width="211px">|returns to default
|align="center" < width="83px">|crattak8
|align="center" < width="66px">|11
|-
|align="center" < width="61px">|'''9'''
|align="center" < width="211px">|'''default'''
|align="center" < width="83px">|'''crattak9'''
|align="center" < width="66px">|12
|-
|align="center" |'''''ANIMATION'''''
|align="center" < width="61px">|'''FRAME #'''
|align="center" < width="211px">|'''OFFSET'''
|align="center" < width="213px">|'''ACTION DESCRIPTION'''
|align="center" < width="83px">|'''FILE NAME'''
|align="center" < width="66px">|'''NOTES'''
|-
|align="center" |'''''CROUCH PAIN'''''
|align="center" < width="61px">|'''1'''
|align="center" < width="211px">|-2
|align="center" < width="213px">|'''OUCH!'''
|align="center" < width="83px">|'''crpain1.tri'''
|align="center" < width="66px">|'''3'''
|-
|rowspan="3" |
|align="center" < width="61px">|2
|align="center" < width="211px">|-2
|align="center" < width="213px">|recoils
|align="center" < width="83px">|crpain2.tri
|align="center" < width="66px">|'''4'''
|-
|align="center" < width="61px">|3
|align="center" < width="211px">|1
|align="center" < width="213px">|recoils
|align="center" < width="83px">|crpain3.tri
|align="center" < width="66px">|'''5'''
|-
|align="center" < width="61px">|'''4'''
|align="center" < width="211px">|3
|align="center" < width="213px">|'''crouch default'''
|align="center" < width="83px">|'''crpain4.tri'''
|align="center" < width="66px">|'''6'''
|-
|align="center" |'''''ANIMATION'''''
|align="center" < width="61px">|'''FRAME #'''
|align="center" < width="211px">|'''OFFSET'''
|align="center" < width="213px">|'''ACTION DESCRIPTION'''
|align="center" < width="83px">|'''FILE NAME'''
|align="center" < width="66px">|'''NOTES'''
|-
|align="center" |'''''CROUCH DEATH'''''
|align="center" < width="61px">|'''1'''
|<width="211px" |5>|
|align="center" < width="213px">|'''OUCH'''
|align="center" < width="83px">|'''crdeath1'''
|align="center" < width="66px">|3
|-
|rowspan="4" |
|align="center" < width="61px">|2
|align="center" < width="213px">|dying
|align="center" < width="83px">|crdeath2
|align="center" < width="66px">|4
|-
|align="center" < width="61px">|3
|align="center" < width="211px">|dying
|align="center" < width="83px">|crdeath3
|align="center" < width="66px">|5
|-
|align="center" < width="61px">|4
|align="center" < width="211px">|dying
|align="center" < width="83px">|crdeath4
|align="center" < width="66px">|6
|-
|align="center" < width="61px">|'''5'''
|align="center" < width="211px">|'''dead'''
|align="center" < width="83px">|'''crdeath5'''
|align="center" < width="66px">|7
|-
|align="center" |'''''ANIMATION'''''
|align="center" < width="61px">|'''FRAME #'''
|align="center" < width="211px">|'''OFFSET'''
|align="center" < width="213px">|'''ACTION DESCRIPTION'''
|align="center" < width="83px">|'''FILE NAME'''
|align="center" < width="66px">|'''NOTES'''
|-
|align="center" |'''''DEATH 1'''''
|align="center" < width="61px">|'''1'''
|align="center" < width="211px">|0
|align="center" < width="213px">|'''OUCH'''
|align="center" < width="83px">|'''death101'''
|<width="66px" |6>|
|-
|rowspan="5" |
|align="center" < width="61px">|2
|align="center" < width="211px">|0
|align="center" < width="213px">|body settles
|align="center" < width="83px">|death102
|-
|align="center" < width="61px">|3
|align="center" < width="211px">|'''-14'''
|align="center" < width="213px">|body settles
|align="center" < width="83px">|death103
|-
|align="center" < width="61px">|4
|align="center" < width="211px">|19
|align="center" < width="213px">|body settles
|align="center" < width="83px">|death104
|-
|align="center" < width="61px">|5
|align="center" < width="211px">|5
|align="center" < width="213px">|body settles
|align="center" < width="83px">|death105
|-
|align="center" < width="61px">|'''6'''
|align="center" < width="211px">|'''-2'''
|align="center" < width="213px">|'''dead'''
|align="center" < width="83px">|'''death106'''
|-
|align="center" < height="18px">|'''''ANIMATION'''''
|align="center" < width="61px" height="18px">|'''FRAME #'''
|align="center" < width="211px" height="18px">|'''OFFSET'''
|align="center" < width="213px" height="18px">|'''ACTION DESCRIPTION'''
|align="center" < width="83px" height="18px">|'''FILE NAME'''
|align="center" < width="66px" height="18px">|'''NOTES'''
|-
|align="center" |'''''DEATH 2'''''
|align="center" < width="61px">|'''1'''
|align="center" < width="211px">|0
|align="center" < width="213px">|'''OUCH'''
|align="center" < width="83px">|'''death201'''
|<width="66px" |6>|
|-
|rowspan="5" |
|align="center" < width="61px">|2
|align="center" < width="211px">|0
|align="center" < width="213px">|body settles
|align="center" < width="83px">|death202
|-
|align="center" < width="61px">|3
|align="center" < width="211px">|'''-11'''
|align="center" < width="213px">|body settles
|align="center" < width="83px">|death203
|-
|align="center" < width="61px">|4
|align="center" < width="211px">|'''-5'''
|align="center" < width="213px">|body settles
|align="center" < width="83px">|death204
|-
|align="center" < width="61px">|5
|align="center" < width="211px">|0
|align="center" < width="213px">|body settles
|align="center" < width="83px">|death205
|-
|align="center" < width="61px">|'''6'''
|align="center" < width="211px">|0
|align="center" < width="213px">|'''dead'''
|align="center" < width="83px">|'''death206'''
|-
|align="center" < height="11px">|'''''ANIMATION'''''
|align="center" < width="61px" height="11px">|'''FRAME #'''
|align="center" < width="211px" height="11px">|'''OFFSET'''
|align="center" < width="213px" height="11px">|'''ACTION DESCRIPTION'''
|align="center" < width="83px" height="11px">|'''FILE NAME'''
|align="center" < width="66px" height="11px">|'''NOTES'''
|-
|align="center" |'''''DEATH 3'''''
|align="center" < width="61px">|'''1'''
|<width="211px" |8>|
|align="center" < width="213px">|'''OUCH'''
|align="center" < width="83px">|'''death301'''
|<width="66px" |8>|
|-
|rowspan="7" |
|align="center" < width="61px">|2
|align="center" < width="213px">|body settles
|align="center" < width="83px">|death302
|-
|align="center" < width="61px">|3
|align="center" < width="211px">|body settles
|align="center" < width="83px">|death303
|-
|align="center" < width="61px">|4
|align="center" < width="211px">|body settles
|align="center" < width="83px">|death304
|-
|align="center" < width="61px">|5
|align="center" < width="211px">|body settles
|align="center" < width="83px">|death305
|-
|align="center" < width="61px">|6
|align="center" < width="211px">|body settles
|align="center" < width="83px">|death306
|-
|align="center" < width="61px">|7
|align="center" < width="211px">|body settles
|align="center" < width="83px">|death307
|-
|align="center" < width="61px">|'''8'''
|align="center" < width="211px">|'''dead'''
|align="center" < width="83px">|'''death308'''

OldSiteResourcesQuake2Md2ReadmeTemplate

2006-06-09T06:05:27Z

VitoMiliano:

__NOTOC__
<INSERT DATE HERE>
================================================================
Model Name : <NAME HERE>
installation directory : quake2/baseq2/players/<DIR HERE>
Author : <YOUR NAME>
Skin Author : <Skinners name> *only if different to modeler*
Email Address : <YOUR ADDRESSS>

Model description : <DESCRIPTION HERE>

Other info : <OTHER STUFF>

Additional Credits to : <id Software, etc etc >

Thanks to : <PPL TO THANK>
================================================================
* Play Information *

New Sounds : <YES/NO>
CTF Skins : <YES/NO>
VWEP Support : <YES/NO>

* Construction *
Poly Count : <### polys>
Vert Count : <### Verts>
Skin Count : <## Skins>
Base : <New model or modified exsisting model>
Editor used : <What editors you used>
Known Bugs : <Any bugs>
Build/Animation time : <time>

* How to use this model *

<INSTALLATION INFO>

* Copyright / Permissions *

QUAKE(R) and QUAKE II(R) are registered trademarks of id Software, Inc.

<Other Legal info about the use of your model>

OldSiteResourcesQuake2

2006-06-09T06:04:03Z

VitoMiliano:

__NOTOC__
You have a bunch of high powered weapons, and you run from room to room killing anything that moves. That's the gist of Quake2. But that's ok because most of use enjoy the online death matching, which is why we do models in the first place, more.

'''[tools.shtml Tools]'''

A variety of utilities to help you get through the night on your modeling efforts for Q2.

'''[tutorials.shtml Tutorials]'''

You want to see how to do any aspect of Q2 modeling, we got the goods and some links too.

[q2frameslist.shtml Frames List]

It's not quite a tools, and it's definitely not a tutorial, so the frames list for Quake2 player models gets its own section. If you want to pursue Quake2 player models, you will need this chart to be able to arrange your frames correctly.

'''[FAQ.shtml FAQ]'''

Got the number one question of Q2 player models answered as well as links to a couple more FAQs.

OldSiteResourcesQuake2PpmTroubleshooting

2006-06-09T05:51:29Z

VitoMiliano:

__NOTOC__
''''''TROUBLESHOOTING PLUG-IN PLAYER MODELS -by Stecki''''''

* Please read the text file included with most PPM's (and files for that matter) before contacting the authors. Many times, troubleshooting is addressed in those files. Also, they may give website addresses that can point you in the right direction to solving your problems...
* Okay, so you downloaded the latest PPM and it's not showing up. There are a few simple things you can check out before you fire off the e-mails to the author of the PPM or hit the [http://dynamic.gamespy.com/~q2pmp/ubb/Ultimate.cgi messageboards].
* If your PPM isn't showing up at all in the Multiplayer Selection Screen, then the most likely solution is to make sure there no files, except subdirectories in the baseq2/players folder. If there is even a hidden file in this directory, it can cause this error. So make sure the baseq2/players directory is clear of all files except the directories for the PPM's themselves.
* If this does not work, then the first step in troubleshooting is to rename the male marine to something else, and rename the troubled PPM to male. See if you even see the model, since the male model should always work.
* If it's not coming up now, check to make sure that the skins have a corresponding icon file. For example, if a skin is named "waste.pcx" it must have a file that corresponds with it called "waste_i.pcx" If this file isn't there, create one. Q2 needs this file so that it can register the skin (and consequently the model).
* After this, if it's still not showing up, there is most likely an error with the model, check with the site you got it from for info. Read the Text file included with the downloaded file!
* Perhaps you are getting a NULL SKIN ERROR or similar message. This is a pretty common error. What it basically is telling you is that it doesn't understand what skin or where the skin is that goes on the model, so Q2 doesn't know what to do. This is a linking problem most likely. It is easily fixed, provided you have the tools. The best tool to correct this error is Npherno's Skin Tool (NST). This is a great program and easy to use, so don't worry. Load up NST and open the model that is giving you the error. It will ask if you want to load in some skins. Just say no. You wont see anything in the windows, and the palette will be a grayscale. This is normal. The model is there, you just can't see it yet. Go to the menu marked skins, and select open (or Shift+O). Find the skin that corresponds to the model. When you open it, the Q2 palette should replace the gray scale palette, and the model should be in the window along with the skin.
* Now open skins menu again, and select link (Shift+L). The skin is now linked to the file. Save the model out (remember to back up the original, just in case) and try running Q2 again. If it is still giving you the problem, do the same thing again, except unlink (Ctrl+L) the skin this time, and resave the model.
* This should fix it, and this has worked (sometimes linking, and sometimes unlinking) on various machines with different people I have talked to.
* This should help you out, and this does cover the most common errors mentioned. I can't stress enough about reading the text files included with the models, as well as researching modeling sites on the web before emailing authors comments like "your PPM doesn't show up, help!" If you have tried to find answers on the web, and still can't figure it out, at least type up an intelligent letter that explains the circumstances of the error, and not the one liner ambiguous help. I usually respond with as much info as a get, so the less you give to work with, the less you'll get back.
''Stecki is a pro artist who runs a very nice personal web page, [http://www.frag.com/deconstruct/ Deconstruct]. ''

OldSiteResourcesQuake2Tutorials

2006-06-09T05:45:12Z

VitoMiliano:

__NOTOC__
'''Quake2 Tutorials'''

[tutorials/Custom%20VWEP.shtml Custom VWep tutorial] by [http://www.netcom.ca/~jmoffatt Nemesis] - Shows the basics behind giving your model VWep support. If you want an instantly popular model, follow the steps within and watch the glory fall at your feet.

[http://weber.u.washington.edu/~vondoom/misc/skintut/skins.html Doctor Doom's Fun with Skins] by [mailto:vondoom@u.washington.edu Doctor Doom] - Dr. Doom has given us the basics of doing the skin mapping and painting for box of shotgun shells in NST and Paint Shop Pro. A must for anyone wanting to learn to do their own model's skins and mappings.

[tutorials/NST_Tut01/NST_Tut01.shtml NST Tutorials] - Instructs on the use of NPherno's Skin Tool. They are a little rough, but they should get you pointed in the right direction.

[http://members.xoom.com/JohnHsia/tut3/tut3.html NST Tutorial] by John Hsia - It's similar to the one above but he says it in a different way. So if others don't work for you, try this one.

[tutorials/NST_RetroMap.shtml NST Retro Mapping Tutorial] by Space Dog - shows how to use the new function in NST .09b3. It basically allows you to redo an existing skin mapping layout and then suck the pixels off the old skins and into correct arrangement in the new mapping layout. A very useful tool for saving time and effort when you need to edit your model.

[tutorials/NGLV/NGLV.shtml NPherno's GL Viewer Tutorial] by [mailto:melkior@usa.net rogue13] - A Quick and dirty primer on using NPherno's GL Viewer.

[tutorials/Weapon%20Skin%20Linking.shtml Weapon Skin Linking] by [mailto:melkior@usa.net rogue13] - If you're clueless to how to link your weapon model's skin or you're seeing the nasty nullskin warning, this is the place to go.

OldSiteResourcesQuake2WeaponSkinLinking

2006-06-09T05:43:47Z

VitoMiliano:

__NOTOC__
'''Weapon Skin Linking'''

by rogue13

A lot of beginning modelers have a problem with correctly linking the weapon model's skin to the weapon. This creates the nasty "nullskin" warning one or two of you may have seen before. So with that in mind I've written a tutorial on this arduous task. This will work for any model with the requirements listed and should be easy enough that any user can fix any model that they have problems with.

This only works for Quake2 models and will work for any model that has its skins not in a PAK file. Usually the weapon and its skin are in the player model directory and tutorial follows this assumption.

# Open the weapon model in [[q2pmp/dev central1/tools.htm|NST]], and pull down the '''Skins''' menu. From here '''D''''''elete/Close''' the current skin. You may have to do this a couple of times until the model goes black and the Skins listing is blank.
# Now under the '''File''' menu go to '''Save As''' and save on top of the weapon model under the proper directory.
# Close [[q2pmp/dev central1/tools.htm|NST]] and reopen it. [this is just to be completely sure that everything is fine]
# Manually reopen the model even if it loaded automatically, again just to be sure.
# Under the '''Skins''' menu select the weapon's skin under the '''Open''' command.
# Now you should be seeing the skin correctly. Under the '''Skins''' menu go to '''Link''' and re-pick the exact same skin. It is now linked correctly.
# Under the '''File''' menu, do another '''Save As''' on top of the model again and you should be gold. If you close [[q2pmp/dev central1/tools.htm|NST]] and reopen it, NST should automatically reload the skin.

OldSiteResourcesQuake2TutorialsNstRetroMap

2006-06-09T05:42:16Z

VitoMiliano:

__NOTOC__
Space Dog's Retro-Map Tutorial

'''Explaination of Skin Mapping for Newbies'''

Every model has a set of coordinates, usually referred to as the "skin mapping", that maps a skin to the model's surface. Since no two models have the same skin mapping, skins for one model cannot be used on another.

'''Explaination of Retro-Map'''

Simply put, Retro-Map takes your skins made for an old skin mapping and rearranges the pixels to create a new skins for a different skin mapping. There are several reasons you'd want to do this: First of all, there's the simple fact that everyone makes mistakes. You may decide after finishing a skin that the skin waste is way to high, or that the layout of the skin is less than optimal, and when that happens, you'd rather not have to completely start a skin from scratch. Another reason is that you may want to use a photograph as your skin, and you need to rearrange it to fit a pre-existing skin mapping.

'''How It Works'''

Open a copy of the model with the old skin mapping in NST. Let's assume you want to Retro-Map the entire mesh, so click "Mapping->Select All", then click "Mapping->Export". Enter a file name (in this tutorial we'll call the file "oldmapping.nmp") and save.

Now open the model with the new skin mapping. Click "Mapping->Select All" again, then click "Mapping->Retro-Map". A pop-up file dialog will appear. Find the skin you want to retro-map and double-click. Next, a second file dialog will appear, and this time you'll want to find "oldmapping.nmp" and double-click. That's it. The retro-mapped skin should appear before your very eyes.

'''"Black Edge" Phenomenon'''

As some of you already know, NST isn't exactly perfect when it comes the edges of your skin mapping, and the Retro-Map feature is no exception. When retro-mapping, NST will drop some pixels that lie on the very edges of your skin mapping. Since skinners usually us a black background for their skins, the result is usually a series of black triangles that line the edges of your model in Quake 2 software mode, and definite black seams on your model in OpenGL mode. You will have to compensate for this problem by filling in the missing pixels.

'''Double Your Skin Size, Double Your Fun'''

Retro-Map doesn't do any blending of pixels, so if a sizable area of a skin is retro-mapped to a relatively small area in the new skin, you'll get a sort of non-mipmapped glittery effect that looks especially bad if the area had a lot of detail. One way to fix this is to double the scale of everything (doubling the skin size for both skin mappings as well as doubling the size of the skin), performing the Retro-Map at the increased scale, then shrinking the resulting skin down to the original size. It should be noted, however, that this process is labor intensive and often unnecessary.

'''You Ought To Be In Pictures'''

Say you want to Retro-Map a photograph to fit the skin mapping for your model. Create a skin mapping that matches the layout on the photograph and export it to an NMP file. (DO NOT SAVE THE MODEL!) Then load up your model with the original skin mapping and Retro-Map the photograph using the NMP file you just saved. Easy as cake!

'''Showing Your True Color'''

"Oh, no!", you cry. "I work on my skins in 24-bit color and then reduce them to the Quake 2 pallette, and NST only supports 256 colors! How do I retro-map my beautiful true color images???"

Okay, so maybe you're not thinking that. However, there are some situations you'll want to do this, especially if you're developing a model for both Q2 and Quake III Arena formats at the same time. Here's the solution: First, get a copy of Paint Shop Pro 5.01. (Note: You may be able to do the following with another graphics editor, such as Photoshop. You'll have to check the features of your software.) Load up your image, break it up into Red, Green and Blue channels, and save each channel as a 256 color PCX or BMP file. Since NST supports any 256 pallette rather than just the Q2 pallette, you can retro-map the three images one at a time, then recombine the channels in Paint Shop Pro once you're done. For best results, you may want to combine this with the scale doubling technique I mentioned earlier.

OldSiteResourcesQuake2TutorialsCustomVwep

2006-06-09T05:35:40Z

VitoMiliano:

__NOTOC__
'''Custom VWEP'''

by [http://www.netcom.ca/~jmoffatt Nemesis]

'''What you will need'''

3DS MAX 1.2 or 2.
MDL model editor and asc exporter for 3DS MAX
and this handy little zip I made for you: [http://asp.planetquake.com/dl/dl.asp?q2pmp/vwepfile.zip vwepfile.zip]

'''Step One: Importing weapons into MAX'''

First open up your Model that you created in 3DS MAX. Then import all the 3ds files that I included in the zip. If you already had a weapon from before that was animated then the best thing to do is to position and scale the models you just imported at the first frame. Then link the new weapons to the old weapon. This will make them follow the movement of your old weapon. Don't know how to link them? Use the link button!

'''Step Two: Exporting weapons from MAX'''

Now you will need to go into the Utilities section of MAX and use the ascii exporter. First make sure you time frame is set for frames 0 - 172 or like I have 1 - 173 (this is cause there are no animation’s for weapons when you die). Then click ascii object output click the "pick object" button and select a weapon. You will be prompted to name the output, What I did was create a folder for each weapon and named each weapon according to its proper name. Example: w_rlauncher.asc in the w_rlauncher folder.
Your computer will now make 173 asc files of that weapon model into that folder. Repeat these steps for each of the weapons.

'''Step Three: Importing weapons into MDL'''

OK open up MDL. The open up the sshotgun.md2 that I included in the zip. Notice that there is only one frame, I deleted all the other frames for you so you better thank me. OK now click File/Import/Import append frames. You will then be prompted to select your sshotgun.asc files. It is important for you to do this right: select sshotgun173.asc first then while holding shift select sshotgun001.asc, all the sshotgun files should be highlighted now so click OK. If you don’t select the files like this then the order gets screwed up (maybe he fixed this in new version but I don't know).

Now that you have imported all these files you can delete that first frame that was there before. Don't delete this frame before you import your frames or else you will get some errors because you have 0 frames. Now click File/export/export to md2 and save you model in the same directory as you model's tris.md2 using its proper name e.g.: sshotgun.md2. You will then be asked to chose a skin, if you have unpacked the models and skins from the vwep pack file then you just have to point to them. If you haven't unpacked the vwep zip then go unpack it you fool! What? you don't have an unpacker OK go here: [http://goldrush.com/~hicks/adquedit/ Adquedit]

You should now have a nice perfect sshotgun.md2 that works perfectly with your model. Do those last steps for the rest of the weapons and frag me baby.

OldSiteResourcesQuake2TutorialsNstTut1

2006-06-09T05:31:54Z

VitoMiliano:

__NOTOC__
'''Down and Dirty Tutorials For NST'''

'''Tools needed for this tutorial'''

Npherno's Skin Tool

a model of some type in MD2 format.

'''Overview'''

These tutorials are pulled from the set of posts I put up on the Message Board. I've attempted to spell check and flesh them out a bit more, but I'm afraid they will also require a little thinking on your end as well. You may need to do a little trial and error as well. Good luck with these and your own models. - rogue13

'''Skin Mapping'''

This exercise is for when you have a completed model in MD2 format and you are ready to lay the polygons from the 3d model onto the 2d skin.

# In the 3d window, turn your model so you have a full view of one side of an hand. For the purposes of this tutorial, I'll be remaping the back of the left hand from the standard female model. It helps, but not necessary, if you've done some of your animations already so you can get into different tight areas as you cycle through the frames. You want to be looking at the set of faces you're currently interested in as perpendicular to the 3d viewing plane as possible. Obviously it's impractical to line the view up for every single face. So we make an educated guess and try to average the difference between a set of faces.

attachment:nst3.gif

2.Another tip to make your life easier: Check the color sections I've put into my presets in the lower left of the screen. The green will display as unselected polys on the model and the red will be selected. Pick your own color scheme if my Xmas theme doesn't do it for you.

Now make sure you've selected the triangle tool and have turned off the camera mode. [ The 3rd and 1st buttons respectively, check the screenshot as well. ] You can toggle between camera and edit modes by hitting the space bar.

Now select the faces you are looking at mapping by holding the cursor over the face and hitting the left mouse button. The right mouse button deselects it.

attachment:new-3b.gif

3. Now select the rectangle tool [ 8th from the left ] and click and drag a box onto the 2d skin that's vaguely the same proportions as if you put a box around your selections in the 3d view.

attachment:nst4.gif

4. Select the Rectangle pulldown menu and select the only option you have, "Map from 3D View" You'll get a dialog box up. Until you get the hang of it, select "parallel" and "no backfaces".

attachment:nst5.gif

You should almost always say no backfaces. If you know why you shouldn't select that for a particular case, you're probably not needing to be read this tutorial. The options here can help you set up your skin to map several pieces of the model to the same place of the skin. This saves space for other sections of the model and can help increase your level of detail that you can put it. Look at the dire avenger model and the terminator models for good examples of this. These are also advanced concepts and remember that although there is no undo, you can simply reselect the faces and remap them again if you bungle something.

Click ok and the faces will appear in the rectangle on the 2d skin. you'll also notice that the checkerboard pattern appears on the model. This is important. Npherno didn't pick the pattern on accident. It can help you arrange your skin so that you can paint across different sections properly without texture sheer.

attachment:nst6.gif

'''Texture Sheer'''

Texture Sheer: when a triangle is mapped to a section of the skin in such a way that it causes the texture to warp excessively across the plane of the polygon on the model.

See the first side picture of the hand that has some sheer, because of the way the initial selection was laid down on the skin. See the second pic that I've adjusted the triangles and have gotten the texture to blend better with the adjacent triangles. This tends to make for some wacky skin arrangements. Where you pull your skin off of, and how its laid out can be an art to get right, if you're so inclined. This is something that takes time to get a good feel for it and don't worry if you end up remapping a section a couple of times to get it to lay out properly. Of course "properly" is subjective, here.

attachment:nst7.gif attachment:nst8.gif

'''Sticky Mapping'''

[ this is the raw post from the message board, I'll refine it at a later date ]

This is for arranging the polygons on the 2d skin, once you've pulled them off the model.

1. after you select the faces you want to move, hit the paperclip button. this is the sticky mapping button.

# now hold your cursor over the selected faces on the 2d skin and click and hold the right mouse button, then drag the faces to where you want.:

3. thats all you have to do :) but say you like the way a set of faces are lined up but you just need to scale them to fit. no problem.: do the same as above and hold the control key down, then click and drag the right mouse button. it will scale in relation to each axis that you drag the mouse button.:

4. if you've don this on an already skinned model, you are already quite excited but I suggest that you do a quick scribble on some faces and then experiment with the above concepts. you'll see why the button is called "sticky mapping" it also works when you adjust individual vertices.

OldSiteResourcesQuake2TutorialsNstTut1

2006-06-09T05:29:07Z

VitoMiliano:

__NOTOC__
'''Down and Dirty Tutorials For NST'''

'''Tools needed for this tutorial'''

Npherno's Skin Tool

a model of some type in MD2 format.

'''Overview'''

These tutorials are pulled from the set of posts I put up on the Message Board. I've attempted to spell check and flesh them out a bit more, but I'm afraid they will also require a little thinking on your end as well. You may need to do a little trial and error as well. Good luck with these and your own models. - rogue13

'''Skin Mapping'''

This exercise is for when you have a completed model in MD2 format and you are ready to lay the polygons from the 3d model onto the 2d skin.

# In the 3d window, turn your model so you have a full view of one side of an hand. For the purposes of this tutorial, I'll be remaping the back of the left hand from the standard female model. It helps, but not necessary, if you've done some of your animations already so you can get into different tight areas as you cycle through the frames. You want to be looking at the set of faces you're currently interested in as perpendicular to the 3d viewing plane as possible. Obviously it's impractical to line the view up for every single face. So we make an educated guess and try to average the difference between a set of faces.

image!

2.Another tip to make your life easier: Check the color sections I've put into my presets in the lower left of the screen. The green will display as unselected polys on the model and the red will be selected. Pick your own color scheme if my Xmas theme doesn't do it for you.

Now make sure you've selected the triangle tool and have turned off the camera mode. [ The 3rd and 1st buttons respectively, check the screenshot as well. ] You can toggle between camera and edit modes by hitting the space bar.

Now select the faces you are looking at mapping by holding the cursor over the face and hitting the left mouse button. The right mouse button deselects it.

image!

3. Now select the rectangle tool [ 8th from the left ] and click and drag a box onto the 2d skin that's vaguely the same proportions as if you put a box around your selections in the 3d view.

image!

4. Select the Rectangle pulldown menu and select the only option you have, "Map from 3D View" You'll get a dialog box up. Until you get the hang of it, select "parallel" and "no backfaces".

image!

You should almost always say no backfaces. If you know why you shouldn't select that for a particular case, you're probably not needing to be read this tutorial. The options here can help you set up your skin to map several pieces of the model to the same place of the skin. This saves space for other sections of the model and can help increase your level of detail that you can put it. Look at the dire avenger model and the terminator models for good examples of this. These are also advanced concepts and remember that although there is no undo, you can simply reselect the faces and remap them again if you bungle something.

Click ok and the faces will appear in the rectangle on the 2d skin. you'll also notice that the checkerboard pattern appears on the model. This is important. Npherno didn't pick the pattern on accident. It can help you arrange your skin so that you can paint across different sections properly without texture sheer.

image!

'''Texture Sheer'''

Texture Sheer: when a triangle is mapped to a section of the skin in such a way that it causes the texture to warp excessively across the plane of the polygon on the model.

See the first side picture of the hand that has some sheer, because of the way the initial selection was laid down on the skin. See the second pic that I've adjusted the triangles and have gotten the texture to blend better with the adjacent triangles. This tends to make for some wacky skin arrangements. Where you pull your skin off of, and how its laid out can be an art to get right, if you're so inclined. This is something that takes time to get a good feel for it and don't worry if you end up remapping a section a couple of times to get it to lay out properly. Of course "properly" is subjective, here.

image! image!

'''Sticky Mapping'''

[ this is the raw post from the message board, I'll refine it at a later date ]

This is for arranging the polygons on the 2d skin, once you've pulled them off the model.

1. after you select the faces you want to move, hit the paperclip button. this is the sticky mapping button.

# now hold your cursor over the selected faces on the 2d skin and click and hold the right mouse button, then drag the faces to where you want.:

3. thats all you have to do :) but say you like the way a set of faces are lined up but you just need to scale them to fit. no problem.: do the same as above and hold the control key down, then click and drag the right mouse button. it will scale in relation to each axis that you drag the mouse button.:

4. if you've don this on an already skinned model, you are already quite excited but I suggest that you do a quick scribble on some faces and then experiment with the above concepts. you'll see why the button is called "sticky mapping" it also works when you adjust individual vertices.

PolycountOldTOC

2006-05-31T05:02:23Z

VitoMiliano:

__NOTOC__
<s> This was thrilling to compile. </s> This is ongoing thrills to convert to nice clean wiki formatting.

r13 has ranked pages to be converted in priority order. Pages that are crossed out and have a link next to them are ones that I have copy and pasted into the wiki. '''THEY ARE NOT DONE BEING CONVERTED YET.''' New pages should be made in a new hierarchy; "Old Site Whatever" is not where things should stay. Most are in disgusting auto-HTML-to-wiki markup, some are in a terrible wiki-but-not text format. You (whoever is doing this) must go through each page and verify each link. If a link is dead, Google search to try and find it again. If it's really gone, check the internet archive for it and make a page for it here, including salvaging any images you can. Some links go to other Polycount pages; find the wiki page that replaced that link and correct the link (unless it's a later priority, in which case leave it or make a placeholder wiki page and note that in the list). You also need to go through and clean up all the wiki formatting: it's been converted automatically from the original HTML, so it is really digusting, or it's just plain text, in which case it needs to be formatted in the first place. Some pages have duplicate information. Others are totally outdated and need to be rewritten. Still others need to be combined with existing resources on the site or with other pages. These pages should be nice and clean and mostly plain text so we can put them on the main Polycount site again. That is all.

Please keep things in the list format. Dynamic pages that will be difficult to redirect properly are in italics.

= General Links =
* Poll (poll/poll.shtml) X
* ''News archives'' (news/newsarchives.asp)
* ''News search'' (news/newsarchives.asp?function=search&advanced=1)
* <s> Contact (contacts/index.shtml) {1} </s> [[OldSiteContact]]
* Polycount for PalmOS (news/pqa.zip) X
* Links (links/index.shtml) {2}
* <s> Credits (credits/index.shtml) {1} this should be merged with the contact page </s> [[OldSiteCredits]]
= Download Database =
* ''UT2004 Models, UT2004 Vehicles, UT2003 Models, Quake 3 Models, UT Models, JKA Models, JK2 Models, GTA3 Models, Serious Sam Models, Quake 2 Models, Q3 Map Models, TA Team Models, TA Head Models, Elite Force Models, Half-Life Models, Heretic2 Models, [[CounterStrike]] Models, The Sims Models, Kingpin Models'' (downloads/ and downloads/index.asp?game=##&sort=date&order=DESC) {2}
= Other Models and Skins =
* Q3 Weapon Models (q3weapons/q3weapons-index.shtml) {3}
* HL Weapon Models (hlweapons/hlweapons-index.shtml) {3}
* UT2003 Accessories (dynamic.gamespy.com/~polycount/skins/ut2003skin-index.shtml wtf?) {3}
* Quake 2 Accessories (skins/q2skin-index.shtml) {3}
* Quake 3 Accessories (skins/q3skin-index.shtml) {3}
* Unreal T Accessories (skins/utskin-index.shtml) {3}
* Half-Life Accessories (skins/hlskin-index.shtml) {3}
* Rune Accessories (skins/runeskin-index.shtml) {3}
* Sims Accessories (skins/simskin-index.shtml) {3}
* Accessory Top-Picks (skins/top-picks/top-picks.shtml) {3} potentially X
* Top-Packs (skins/top-picks/top-packs/top-packs.shtml {3} potentially X
= Resources =
* <s> Resources (resources/index.shtml) {1} we should be able to get alot of the heavy lifting here from the community </s> [[OldSiteResources]]

Under Resources, there are these directories and significant files. Directories without any sub-content just have an index.shtml file in them listing resources elsewhere on the net. Most directories also have lots of other directories with supporting files, like images and stuff, which aren't listed for brevity.

* avp2 {3}
** index.shtml
** tutorials
*** talonengine
**** talonenginetut.shtml
* bandw {3} {i} wtf is this? Black and White
* chat-rooms {2}
** chat-index.shtml
** 2design X
*** 2design.shtml
* model_design
** model_design.shtml
* modjobs X
** modjobs.shtml
* drakan {3}
** index.shtml
** gfx
*** JSheffield.zip
* eliteforce {3}
** index.shtml
** tutorials.shtml
** tutorials
*** q3-ef
**** Q3AEF.shtml
* <s> FAQ-genera {1} probably needs reviewl </s>
** <s> faq-general-index.shtml</s> [[OldSiteResourcesFaqGeneral]]
* <s> general {1} </s> [[OldSiteResourcesGeneral]]
** misc {i} sunstorm?
*** sunstorm.shtml
* <s> tools {1} </s>
** <s> infografica.shtml </s> [[OldSiteResourcesGeneralToolsInfografica]]
** <s> polychop </s>
*** <s> gdmag.pdf </s> [[OldSiteResourcesGeneralToolsPolyChop]]
* tutorials {2}
** ALPHAWolf_Tut01
*** Low<code><nowiki></nowiki></code>Poly<code><nowiki></nowiki></code>Characters.shtml
* cswingstut
** cswingstut.shtml
* Hitman<code><nowiki></nowiki></code>Daz_Tut01
** Digital<code><nowiki></nowiki></code>Painting.shtml
* Model-unwrap
** model-unwrap.shtml
** model-unwrap-pic1.shtml
** model-unwrap-pic2.shtml
** model-unwrap-pic3.shtml
** model-unwrap-pic4.shtml
** model-unwrap-pic5.shtml
* NURBS-mapping
** Nurbs-mapping.shtml
** tutorial.html
** vrml1.html
** vrml2.html
** vrml3.html
* Shine_Tut03
** Poly<code><nowiki></nowiki></code>Reduce.shtml
* Shine_Tut04
** Making a Head.shtml
* Shine_Tut05
** Setup Bones Part1.shtml
* Surface<code><nowiki></nowiki></code>Tools
** Surface Tools for Low Poly Modeling2.doc
** Surface<code><nowiki></nowiki></code>Tools.shtml
** Surface<code><nowiki></nowiki></code>Tools-mts.shtml
* UVWunwrap
** UVWunwrap.shtml
* ASC_Export_Tut01.shtml
** Shine_Tut01.shtml
** Shine_Tut02.shtml
* <s> video_tutorials {1} </s>
** <s> video-tut-list.shtml </s> [[OldSiteResourcesGeneralVideoTutorials]]
* <s> apps.shtml {1} </s> [[OldSiteResourcesGeneralApplications]]
** <s> genmisc.shtml {1} </s> [[OldSiteResourcesGeneralMiscellaneous]]
** index.shtml
** <s> lightwave.shtml {1} </s> [[OldSiteResourcesGeneralLightwave]]
** <s> max.shtml {1} </s> [[OldSiteResourcesGeneralMax]]
** <s> maya.shtml {1} </s> [[OldSiteResourcesGeneralMaya]]
** <s> milkshape.shtml {1} </s> [[OldSiteResourcesGeneralMilkshape]]
** <s> misc.shtml {1} </s> "Sorry, I had something here, but it turned out to be illegal."
** <s> modelanim.shtml {1} </s> [[OldSiteResourcesGeneralModelingAndAnimation]]
** nst.shtml {3}
** q2m.shtml {3}
** <s> skinning.shtml {1} </s> [[OldSiteResourcesGeneralSkinning]]
** <s> tools.shtml {1} </s> [[OldSiteResourcesGeneralTools]]
** tutindex.shtml
** tutorials.shtml
* gfx (looks like game logos for pages maybe) {i} i suspect it is, thats what i think its a dup of that other directory
* <s>glossary (24 pages of definitions plus images) {1} </s> http://nathan.perilith.com/~vito/oldpolycount/glossary/
* <s> glossary2 (only one glossary page, but lots of examples files) {1} can we consolidate these? </s> http://nathan.perilith.com/~vito/oldpolycount/glossary2/glossary.html
* gta3 {3}
* halflife {2}
** index.shtml
** tools.shtml
** tutorials.shtml
** tutorials (directory with 20 pages of modeling tutorials plus example content)
* heretic2 {3}
** index.shtml
** tools.shtml
** tutorials.shtml
* jk2 {3}
** index.shtml
** tutorials
*** Model<code><nowiki></nowiki></code>Tutorial (eight files under here making this up)
*** jk2_model_construction.shtml
* kingpin {3}
** tools
*** framelist.shtml
*** tools.shtml
* index.shtml
** Kingpin-animations.html
* lithtech {3}
** tutorials
*** lithtech_primer.shtml
* index.shtml
** tools.shtml
** tutorials.shtml
* manual (how to review a model?) {i} it may go X
* nolf {3}
* quake {2}
** FAQ.shtml
** index.shtml
** tools.shtml
** tutorials.shtml
* <s> quake2 {1} </s>
** <s> tools </s>
*** <s> Prefabs </s>
**** <s> Alx_Prefabs-info.shtml </s> [[OldSiteResourcesQuake2ToolsPrefabsAlx]]
**** <s> Hunter_Prefabs-info.shtml </s> [[OldSiteResourcesQuake2ToolsPrefabsHunter]]
** <s> Testbox </s>
*** <s> testbox.shtml </s> [[OldSiteResourcesQuake2ToolsTestbox]]
* tutorials
** <s> NGLV </s> [[OldSiteResourcesQuake2TutorialsNglv]]
** NST_Tut01
** Custom VWEP.shtml
** NST_Retro<code><nowiki></nowiki></code>Map.shtml
** Weapon Skin Linking.shtml
* FAQ.shtml
** index.shtml
** md2text.txt
** q2frameslist.shtml
** tools.shtml
** tutorials.shtml
* quake3 {1}
** Model_Doc
*** Model_manual_ps.htm
* Shader_Doc
** Q3<code><nowiki></nowiki></code>Ashader_manual.htm
* tools
** tutorials (lots of files below these, ugh)
*** josh
*** max-to-q3
*** MAX-to-q3data
*** Skin-shader
*** Sound<code><nowiki></nowiki></code>Pak
*** Steed-Tut
* index.shtml
** md3text.txt
** tools.shtml
** tutorials.shtml
* rune {3}
** tutorials
*** lodsettings
**** runetut-lodsettings.shtml
* index.shtml
* sims {3}
** index.shtml
** tools.shtml
** tutorials.shtml
* ssam {3}
* thps {3} {i}
* tribes {3}
** index.shtml
** tools.shtml
** tutorials.shtml
* unreal {2}
** tools
** tutorials (lots of files in these subdirs)
*** lodsettings
*** mage
*** pix
*** sounds
*** umod
*** umod-backup
*** UTut01.shtml
*** UTut02.shtml
*** UTut03.shtml
*** UTut04.shtml
*** UTut05.shtml
*** UTut06.shtml
*** Utut07.shtml
* index.shtml
** tools.shtml
** tutorials.shtml
** UTtut-mainpage.shtml
** UTtut-part5.shtml
* ut2003 {1}
** tutorials
*** backups (this might just be backup content, not sure, something about Intertwined)
*** ut2mod
*** pushing_tutorial.shtml
* index.shtml
** tools.shtml
** tutorials.shtml
Also what I'd consider resources are:

* Good, Bad and Ugly (skins/gbu/* with eight article directories under it) {2}
* Skin news archives (skins/archived-news/* with 30 pages of news under it) {i} no idea
* Articles (ten article directories below that:) {2}
** animation-tips
** BnW<code><nowiki></nowiki></code>interview
** chiq_interview_012602
** chrisbruce_072002
** Gwot062k2
** max3preview
** q3-model-preview
** Steed-gdc99
** Steed-Interview
** Steed-Interview-2
* Subdermal (six pages and a contest) {2}

= Not Linked To =
* [[AskDev]] (ask a developer column?) X this didnt pan out. a dev house wanted to help just answer questions. But pulled out right as we set it all up.
* docs/gamespace_release.zip X
* misc
** Discreet_QCon2k1 {3} {i} needs review
** e32k4 {3} {i} needs review
** gfx {i} is this just a directory full of original polycount gfx?
** id-model-renders {3}
** pimps {3} {i} needs review
** 12-3action.htm {3} {i} needs review
** gamespy-broadcastkey.txt X
** lead_action_designer.doc X
** micro-forte-syd-jobdoc.shtml X
** stuff.htm {3} {i} needs review
** Unreal_Coach_jobpost_053104.doc X
* modeloftheweek X
* modelpacks {3}
* paintchat {2} conditional that we can get it working again, free/cheap. if not... X
* previews X
** nicknacks X
* reviewlists X
* skindom (woah nelly tons of stuff here) {3}
* cutedoll.shtml (contest?) {3} archive purposes only
* info (actual static model info files, non-db) {2} after database
* reviews (actual static model review files, non-db) {2} after database

OldSiteResourcesQuake2TutorialsNglv

2006-05-31T05:01:11Z

VitoMiliano:

__NOTOC__
'''NPherno's GL Viewer'''

by rogue13''' - [http://asp.planetquake.com/dl/dl.asp?q2pmp/nglv.zip Download it here]'''

'''Tools needed for this program'''

Npherno's GL viewer

A Quake 2 model

A video car with good Open GL support

Skins to put on the model

Time and patience

'''Overview'''

This is to be a help file / tutorial / read me text for the GL viewer. This viewer is pure GL. It will not run on sub standard cards, nor will it run on 3DFX based cards that use the proprietary Glide drivers. It needs to be the real thing.

If your running a TNT based card, you are set. That's what it was built and tested on, both in Win 98 and NT4. Other cards may or may not be able to provide the proper platform. Next is a list of cards that we know of after beta testing, if you have another type and have success or not, we'd love to hear about it to add to the list here:

{| border="1" cellpadding="2" cellspacing="0"
| '''TNT'''
|-
| '''Permedia2'''
|-
| '''i740'''
|-
| '''Voodoo 1/2'''
|-
| '''G200'''
|}
So now you're asking me "What is this thing and why should I use it?" Well that's understandable, plenty of people use Skinview and find this sort of thing useless. Fine, this app is about creating some excellent views of your model with colored lighting and a 4 pass rendering system. Yep, that means four skins per model. This is what id has say will be available to us for Quake3 models. If it doesn't happen for Q3, it is somewhat already part of Half Life, which does offer specularity texture maps for the models. So you can sort of "practice" now plus getting some superb images for your models which is always an excellent thing.

'''The Installation'''

1. Unzip the two files into a directory. How about "c:\NGLV"

2. Make an icon for yourself in the appropriate spot, I chose my desktop.

3. Double click on the icon of love and you're in.

'''Using the Viewer'''

attachment:NGLV-1.jpg

On this first edition of the readme for the viewer, I'm basically going to call out what everything is and then refine later.

I also suggest you get at least the [../../../models2/unit01.htm Unit01 model] that is shown above as it was released with all 4 skins in .bmp format already. The other two Unit models 00 and 02 were not released with the GLV skins, but they were made. Here's a link to get them separately if you already have those models and would like to test the viewer with more that just one model.

*
[http://asp.planetquake.com/dl/dl.asp?q2pmp/unit00-02-GLVskins.ZIP Unit 00/02 GL skins for the Nglv]

{| border="1" cellpadding="2" cellspacing="0"
|-
| LGT Transfer
|}
||
{| border="1" cellpadding="2" cellspacing="0"
| Exit
|-
|-
| Texture
|}
||
{| border="1" cellpadding="2" cellspacing="0"
| Multipass
|}
||
{| border="1" cellpadding="2" cellspacing="0"
| Background color
|}
||
{| border="1" cellpadding="2" cellspacing="0"
| Wireframe
|}
||
{| border="1" cellpadding="2" cellspacing="0"
| Environment Map
|}
||
{| border="1" cellpadding="2" cellspacing="0"
|-
| Help
|-
|-
| Setup
|}
||
{| border="1" cellpadding="2" cellspacing="0"
| Models
|}
||
{| border="1" cellpadding="2" cellspacing="0"
| Lights
|}
||
{| border="1" cellpadding="2" cellspacing="0"
| Texture
|}
||
{| border="1" cellpadding="2" cellspacing="0"
| Specularity
|}
||
{| border="1" cellpadding="2" cellspacing="0"
| Diffuse
|}
||
{| border="1" cellpadding="2" cellspacing="0"
| Glow
|}
||
{| border="1" cellpadding="2" cellspacing="0"
| Props
|}
||
{| border="1" cellpadding="2" cellspacing="0"
|-
| Left Mouse Button
|-
| Right Mouse Button
|-
| Shift
|-
| Crtl
|-
|-
| Left and Right Arrow Buttons
|-
|-
| Regular models and skins
|-
| Multiple Lights

OldSiteResourcesQuake2TutorialsNglv

2006-05-31T05:00:07Z

VitoMiliano:

__NOTOC__
'''NPherno's GL Viewer'''

by rogue13''' - [http://asp.planetquake.com/dl/dl.asp?q2pmp/nglv.zip Download it here]'''

'''Tools needed for this program'''

Npherno's GL viewer

A Quake 2 model

A video car with good Open GL support

Skins to put on the model

Time and patience

'''Overview'''

This is to be a help file / tutorial / read me text for the GL viewer. This viewer is pure GL. It will not run on sub standard cards, nor will it run on 3DFX based cards that use the proprietary Glide drivers. It needs to be the real thing.

If your running a TNT based card, you are set. That's what it was built and tested on, both in Win 98 and NT4. Other cards may or may not be able to provide the proper platform. Next is a list of cards that we know of after beta testing, if you have another type and have success or not, we'd love to hear about it to add to the list here:

{| border="1" cellpadding="2" cellspacing="0"
| '''TNT'''
|-
| '''Permedia2'''
|-
| '''i740'''
|-
| '''Voodoo 1/2'''
|-
| '''G200'''
|}
So now you're asking me "What is this thing and why should I use it?" Well that's understandable, plenty of people use Skinview and find this sort of thing useless. Fine, this app is about creating some excellent views of your model with colored lighting and a 4 pass rendering system. Yep, that means four skins per model. This is what id has say will be available to us for Quake3 models. If it doesn't happen for Q3, it is somewhat already part of Half Life, which does offer specularity texture maps for the models. So you can sort of "practice" now plus getting some superb images for your models which is always an excellent thing.

'''The Installation'''

1. Unzip the two files into a directory. How about "c:\NGLV"

2. Make an icon for yourself in the appropriate spot, I chose my desktop.

3. Double click on the icon of love and you're in.

'''Using the Viewer'''

On this first edition of the readme for the viewer, I'm basically going to call out what everything is and then refine later.

I also suggest you get at least the [../../../models2/unit01.htm Unit01 model] that is shown above as it was released with all 4 skins in .bmp format already. The other two Unit models 00 and 02 were not released with the GLV skins, but they were made. Here's a link to get them separately if you already have those models and would like to test the viewer with more that just one model.

*
[http://asp.planetquake.com/dl/dl.asp?q2pmp/unit00-02-GLVskins.ZIP Unit 00/02 GL skins for the Nglv]

{| border="1" cellpadding="2" cellspacing="0"
|-
| LGT Transfer
|}
||
{| border="1" cellpadding="2" cellspacing="0"
| Exit
|-
|-
| Texture
|}
||
{| border="1" cellpadding="2" cellspacing="0"
| Multipass
|}
||
{| border="1" cellpadding="2" cellspacing="0"
| Background color
|}
||
{| border="1" cellpadding="2" cellspacing="0"
| Wireframe
|}
||
{| border="1" cellpadding="2" cellspacing="0"
| Environment Map
|}
||
{| border="1" cellpadding="2" cellspacing="0"
|-
| Help
|-
|-
| Setup
|}
||
{| border="1" cellpadding="2" cellspacing="0"
| Models
|}
||
{| border="1" cellpadding="2" cellspacing="0"
| Lights
|}
||
{| border="1" cellpadding="2" cellspacing="0"
| Texture
|}
||
{| border="1" cellpadding="2" cellspacing="0"
| Specularity
|}
||
{| border="1" cellpadding="2" cellspacing="0"
| Diffuse
|}
||
{| border="1" cellpadding="2" cellspacing="0"
| Glow
|}
||
{| border="1" cellpadding="2" cellspacing="0"
| Props
|}
||
{| border="1" cellpadding="2" cellspacing="0"
|-
| Left Mouse Button
|-
| Right Mouse Button
|-
| Shift
|-
| Crtl
|-
|-
| Left and Right Arrow Buttons
|-
|-
| Regular models and skins
|-
| Multiple Lights

OldSiteResourcesQuake2TutorialsNglv

2006-05-31T04:56:52Z

VitoMiliano:

__NOTOC__
'''NPherno's GL Viewer'''

by rogue13''' - [http://asp.planetquake.com/dl/dl.asp?q2pmp/nglv.zip Download it here]'''

'''Tools needed for this program'''

Npherno's GL viewer

A Quake 2 model

A video car with good Open GL support

Skins to put on the model

Time and patience

'''Overview'''

This is to be a help file / tutorial / read me text for the GL viewer. This viewer is pure GL. It will not run on sub standard cards, nor will it run on 3DFX based cards that use the proprietary Glide drivers. It needs to be the real thing.

If your running a TNT based card, you are set. That's what it was built and tested on, both in Win 98 and NT4. Other cards may or may not be able to provide the proper platform. Next is a list of cards that we know of after beta testing, if you have another type and have success or not, we'd love to hear about it to add to the list here:

{| border="1" cellpadding="2" cellspacing="0"
|align="center" < 1 0 %>|'''TNT'''
|-
|align="center" < 1 0 %>|'''Permedia2'''
|-
|align="center" < 1 0 %>|'''i740'''
|-
|align="center" < 1 0 %>|'''Voodoo 1/2'''
|-
|align="center" < 1 0 %>|'''G200'''
|}
So now you're asking me "What is this thing and why should I use it?" Well that's understandable, plenty of people use Skinview and find this sort of thing useless. Fine, this app is about creating some excellent views of your model with colored lighting and a 4 pass rendering system. Yep, that means four skins per model. This is what id has say will be available to us for Quake3 models. If it doesn't happen for Q3, it is somewhat already part of Half Life, which does offer specularity texture maps for the models. So you can sort of "practice" now plus getting some superb images for your models which is always an excellent thing.

'''The Installation'''

1. Unzip the two files into a directory. How about "c:\NGLV"

2. Make an icon for yourself in the appropriate spot, I chose my desktop.

3. Double click on the icon of love and you're in.

'''Using the Viewer'''

On this first edition of the readme for the viewer, I'm basically going to call out what everything is and then refine later.

I also suggest you get at least the [../../../models2/unit01.htm Unit01 model] that is shown above as it was released with all 4 skins in .bmp format already. The other two Unit models 00 and 02 were not released with the GLV skins, but they were made. Here's a link to get them separately if you already have those models and would like to test the viewer with more that just one model.

*
[http://asp.planetquake.com/dl/dl.asp?q2pmp/unit00-02-GLVskins.ZIP Unit 00/02 GL skins for the Nglv]

{| border="1" cellpadding="2" cellspacing="0"
|-
|align="left" < ^ 5 0 % height="64px">|LGT Transfer
|}
||
{| border="1" cellpadding="2" cellspacing="0"
|align="left" < 5 0 % height="16px">|Exit
|-
|-
|align="left" < ^ 5 0 % height="32px">|Texture
|}
||
{| border="1" cellpadding="2" cellspacing="0"
|align="left" < ^ 5 0 % height="48px">|Multipass
|}
||
{| border="1" cellpadding="2" cellspacing="0"
|align="left" < ^ 5 0 % height="48px">|Background color
|}
||
{| border="1" cellpadding="2" cellspacing="0"
|align="left" < ^ 5 0 % height="32px">|Wireframe
|}
||
{| border="1" cellpadding="2" cellspacing="0"
|align="left" < ^ 5 0 % height="220px">|Environment Map
|}
||
{| border="1" cellpadding="2" cellspacing="0"
|-
|align="left" < | 5 0 % height="58px">Help
|-
|-
|align="left" < ^ 5 0 % height="239px">|Setup
|}
||
{| border="1" cellpadding="2" cellspacing="0"
|align="left" < ^ 5 0 % height="131px">|Models
|}
||
{| border="1" cellpadding="2" cellspacing="0"
|align="left" < ^ 5 0 % height="112px">|Lights
|}
||
{| border="1" cellpadding="2" cellspacing="0"
|align="left" < ^ 5 0 % height="99px">|Texture
|}
||
{| border="1" cellpadding="2" cellspacing="0"
|align="left" < ^ 5 0 % height="48px">|Specularity
|}
||
{| border="1" cellpadding="2" cellspacing="0"
|align="left" < ^ 5 0 % height="48px">|Diffuse
|}
||
{| border="1" cellpadding="2" cellspacing="0"
|align="left" < ^ 5 0 % height="115px">|Glow
|}
||
{| border="1" cellpadding="2" cellspacing="0"
|align="left" < | 5 0 % height="115px">Props
|}
||
{| border="1" cellpadding="2" cellspacing="0"
|-
|align="left" < | 5 0 % height="99px">Left Mouse Button
|-
|align="left" < | 5 0 % height="64px">Right Mouse Button
|-
|align="left" < | 5 0 % height="64px">Shift
|-
|align="left" < | 5 0 % height="64px">Crtl
|-
|-
|align="left" < | 5 0 % height="99px">Left and Right Arrow Buttons
|-
|-
|align="left" < | 5 0 % height="99px">Regular models and skins
|-
|align="left" < | 5 0 % height="64px">Multiple Lights

PolycountOldTOC

2006-05-31T04:51:38Z

VitoMiliano:

__NOTOC__
<s> This was thrilling to compile. </s> This is ongoing thrills to convert to nice clean wiki formatting.

r13 has ranked pages to be converted in priority order. Pages that are crossed out and have a link next to them are ones that I have copy and pasted into the wiki. '''THEY ARE NOT DONE BEING CONVERTED YET.''' New pages should be made in a new hierarchy; "Old Site Whatever" is not where things should stay. Most are in disgusting auto-HTML-to-wiki markup, some are in a terrible wiki-but-not text format. You (whoever is doing this) must go through each page and verify each link. If a link is dead, Google search to try and find it again. If it's really gone, check the internet archive for it and make a page for it here, including salvaging any images you can. Some links go to other Polycount pages; find the wiki page that replaced that link and correct the link (unless it's a later priority, in which case leave it or make a placeholder wiki page and note that in the list). You also need to go through and clean up all the wiki formatting: it's been converted automatically from the original HTML, so it is really digusting, or it's just plain text, in which case it needs to be formatted in the first place. Some pages have duplicate information. Others are totally outdated and need to be rewritten. Still others need to be combined with existing resources on the site or with other pages. These pages should be nice and clean and mostly plain text so we can put them on the main Polycount site again. That is all.

Please keep things in the list format. Dynamic pages that will be difficult to redirect properly are in italics.

= General Links =
* Poll (poll/poll.shtml) X
* ''News archives'' (news/newsarchives.asp)
* ''News search'' (news/newsarchives.asp?function=search&advanced=1)
* <s> Contact (contacts/index.shtml) {1} </s> [[OldSiteContact]]
* Polycount for PalmOS (news/pqa.zip) X
* Links (links/index.shtml) {2}
* <s> Credits (credits/index.shtml) {1} this should be merged with the contact page </s> [[OldSiteCredits]]
= Download Database =
* ''UT2004 Models, UT2004 Vehicles, UT2003 Models, Quake 3 Models, UT Models, JKA Models, JK2 Models, GTA3 Models, Serious Sam Models, Quake 2 Models, Q3 Map Models, TA Team Models, TA Head Models, Elite Force Models, Half-Life Models, Heretic2 Models, [[CounterStrike]] Models, The Sims Models, Kingpin Models'' (downloads/ and downloads/index.asp?game=##&sort=date&order=DESC) {2}
= Other Models and Skins =
* Q3 Weapon Models (q3weapons/q3weapons-index.shtml) {3}
* HL Weapon Models (hlweapons/hlweapons-index.shtml) {3}
* UT2003 Accessories (dynamic.gamespy.com/~polycount/skins/ut2003skin-index.shtml wtf?) {3}
* Quake 2 Accessories (skins/q2skin-index.shtml) {3}
* Quake 3 Accessories (skins/q3skin-index.shtml) {3}
* Unreal T Accessories (skins/utskin-index.shtml) {3}
* Half-Life Accessories (skins/hlskin-index.shtml) {3}
* Rune Accessories (skins/runeskin-index.shtml) {3}
* Sims Accessories (skins/simskin-index.shtml) {3}
* Accessory Top-Picks (skins/top-picks/top-picks.shtml) {3} potentially X
* Top-Packs (skins/top-picks/top-packs/top-packs.shtml {3} potentially X
= Resources =
* <s> Resources (resources/index.shtml) {1} we should be able to get alot of the heavy lifting here from the community </s> [[OldSiteResources]]

Under Resources, there are these directories and significant files. Directories without any sub-content just have an index.shtml file in them listing resources elsewhere on the net. Most directories also have lots of other directories with supporting files, like images and stuff, which aren't listed for brevity.

* avp2 {3}
** index.shtml
** tutorials
*** talonengine
**** talonenginetut.shtml
* bandw {3} {i} wtf is this? Black and White
* chat-rooms {2}
** chat-index.shtml
** 2design X
*** 2design.shtml
* model_design
** model_design.shtml
* modjobs X
** modjobs.shtml
* drakan {3}
** index.shtml
** gfx
*** JSheffield.zip
* eliteforce {3}
** index.shtml
** tutorials.shtml
** tutorials
*** q3-ef
**** Q3AEF.shtml
* <s> FAQ-genera {1} probably needs reviewl </s>
** <s> faq-general-index.shtml</s> [[OldSiteResourcesFaqGeneral]]
* <s> general {1} </s> [[OldSiteResourcesGeneral]]
** misc {i} sunstorm?
*** sunstorm.shtml
* <s> tools {1} </s>
** <s> infografica.shtml </s> [[OldSiteResourcesGeneralToolsInfografica]]
** <s> polychop </s>
*** <s> gdmag.pdf </s> [[OldSiteResourcesGeneralToolsPolyChop]]
* tutorials {2}
** ALPHAWolf_Tut01
*** Low<code><nowiki></nowiki></code>Poly<code><nowiki></nowiki></code>Characters.shtml
* cswingstut
** cswingstut.shtml
* Hitman<code><nowiki></nowiki></code>Daz_Tut01
** Digital<code><nowiki></nowiki></code>Painting.shtml
* Model-unwrap
** model-unwrap.shtml
** model-unwrap-pic1.shtml
** model-unwrap-pic2.shtml
** model-unwrap-pic3.shtml
** model-unwrap-pic4.shtml
** model-unwrap-pic5.shtml
* NURBS-mapping
** Nurbs-mapping.shtml
** tutorial.html
** vrml1.html
** vrml2.html
** vrml3.html
* Shine_Tut03
** Poly<code><nowiki></nowiki></code>Reduce.shtml
* Shine_Tut04
** Making a Head.shtml
* Shine_Tut05
** Setup Bones Part1.shtml
* Surface<code><nowiki></nowiki></code>Tools
** Surface Tools for Low Poly Modeling2.doc
** Surface<code><nowiki></nowiki></code>Tools.shtml
** Surface<code><nowiki></nowiki></code>Tools-mts.shtml
* UVWunwrap
** UVWunwrap.shtml
* ASC_Export_Tut01.shtml
** Shine_Tut01.shtml
** Shine_Tut02.shtml
* <s> video_tutorials {1} </s>
** <s> video-tut-list.shtml </s> [[OldSiteResourcesGeneralVideoTutorials]]
* <s> apps.shtml {1} </s> [[OldSiteResourcesGeneralApplications]]
** <s> genmisc.shtml {1} </s> [[OldSiteResourcesGeneralMiscellaneous]]
** index.shtml
** <s> lightwave.shtml {1} </s> [[OldSiteResourcesGeneralLightwave]]
** <s> max.shtml {1} </s> [[OldSiteResourcesGeneralMax]]
** <s> maya.shtml {1} </s> [[OldSiteResourcesGeneralMaya]]
** <s> milkshape.shtml {1} </s> [[OldSiteResourcesGeneralMilkshape]]
** <s> misc.shtml {1} </s> "Sorry, I had something here, but it turned out to be illegal."
** <s> modelanim.shtml {1} </s> [[OldSiteResourcesGeneralModelingAndAnimation]]
** nst.shtml {3}
** q2m.shtml {3}
** <s> skinning.shtml {1} </s> [[OldSiteResourcesGeneralSkinning]]
** <s> tools.shtml {1} </s> [[OldSiteResourcesGeneralTools]]
** tutindex.shtml
** tutorials.shtml
* gfx (looks like game logos for pages maybe) {i} i suspect it is, thats what i think its a dup of that other directory
* <s>glossary (24 pages of definitions plus images) {1} </s> http://nathan.perilith.com/~vito/oldpolycount/glossary/
* <s> glossary2 (only one glossary page, but lots of examples files) {1} can we consolidate these? </s> http://nathan.perilith.com/~vito/oldpolycount/glossary2/glossary.html
* gta3 {3}
* halflife {2}
** index.shtml
** tools.shtml
** tutorials.shtml
** tutorials (directory with 20 pages of modeling tutorials plus example content)
* heretic2 {3}
** index.shtml
** tools.shtml
** tutorials.shtml
* jk2 {3}
** index.shtml
** tutorials
*** Model<code><nowiki></nowiki></code>Tutorial (eight files under here making this up)
*** jk2_model_construction.shtml
* kingpin {3}
** tools
*** framelist.shtml
*** tools.shtml
* index.shtml
** Kingpin-animations.html
* lithtech {3}
** tutorials
*** lithtech_primer.shtml
* index.shtml
** tools.shtml
** tutorials.shtml
* manual (how to review a model?) {i} it may go X
* nolf {3}
* quake {2}
** FAQ.shtml
** index.shtml
** tools.shtml
** tutorials.shtml
* <s> quake2 {1} </s>
** <s> tools </s>
*** <s> Prefabs </s>
**** <s> Alx_Prefabs-info.shtml </s> [[OldSiteResourcesQuake2ToolsPrefabsAlx]]
**** <s> Hunter_Prefabs-info.shtml </s> [[OldSiteResourcesQuake2ToolsPrefabsHunter]]
** <s> Testbox </s>
*** <s> testbox.shtml </s> [[OldSiteResourcesQuake2ToolsTestbox]]
* tutorials
** NGLV
** NST_Tut01
** Custom VWEP.shtml
** NST_Retro<code><nowiki></nowiki></code>Map.shtml
** Weapon Skin Linking.shtml
* FAQ.shtml
** index.shtml
** md2text.txt
** q2frameslist.shtml
** tools.shtml
** tutorials.shtml
* quake3 {1}
** Model_Doc
*** Model_manual_ps.htm
* Shader_Doc
** Q3<code><nowiki></nowiki></code>Ashader_manual.htm
* tools
** tutorials (lots of files below these, ugh)
*** josh
*** max-to-q3
*** MAX-to-q3data
*** Skin-shader
*** Sound<code><nowiki></nowiki></code>Pak
*** Steed-Tut
* index.shtml
** md3text.txt
** tools.shtml
** tutorials.shtml
* rune {3}
** tutorials
*** lodsettings
**** runetut-lodsettings.shtml
* index.shtml
* sims {3}
** index.shtml
** tools.shtml
** tutorials.shtml
* ssam {3}
* thps {3} {i}
* tribes {3}
** index.shtml
** tools.shtml
** tutorials.shtml
* unreal {2}
** tools
** tutorials (lots of files in these subdirs)
*** lodsettings
*** mage
*** pix
*** sounds
*** umod
*** umod-backup
*** UTut01.shtml
*** UTut02.shtml
*** UTut03.shtml
*** UTut04.shtml
*** UTut05.shtml
*** UTut06.shtml
*** Utut07.shtml
* index.shtml
** tools.shtml
** tutorials.shtml
** UTtut-mainpage.shtml
** UTtut-part5.shtml
* ut2003 {1}
** tutorials
*** backups (this might just be backup content, not sure, something about Intertwined)
*** ut2mod
*** pushing_tutorial.shtml
* index.shtml
** tools.shtml
** tutorials.shtml
Also what I'd consider resources are:

* Good, Bad and Ugly (skins/gbu/* with eight article directories under it) {2}
* Skin news archives (skins/archived-news/* with 30 pages of news under it) {i} no idea
* Articles (ten article directories below that:) {2}
** animation-tips
** BnW<code><nowiki></nowiki></code>interview
** chiq_interview_012602
** chrisbruce_072002
** Gwot062k2
** max3preview
** q3-model-preview
** Steed-gdc99
** Steed-Interview
** Steed-Interview-2
* Subdermal (six pages and a contest) {2}

= Not Linked To =
* [[AskDev]] (ask a developer column?) X this didnt pan out. a dev house wanted to help just answer questions. But pulled out right as we set it all up.
* docs/gamespace_release.zip X
* misc
** Discreet_QCon2k1 {3} {i} needs review
** e32k4 {3} {i} needs review
** gfx {i} is this just a directory full of original polycount gfx?
** id-model-renders {3}
** pimps {3} {i} needs review
** 12-3action.htm {3} {i} needs review
** gamespy-broadcastkey.txt X
** lead_action_designer.doc X
** micro-forte-syd-jobdoc.shtml X
** stuff.htm {3} {i} needs review
** Unreal_Coach_jobpost_053104.doc X
* modeloftheweek X
* modelpacks {3}
* paintchat {2} conditional that we can get it working again, free/cheap. if not... X
* previews X
** nicknacks X
* reviewlists X
* skindom (woah nelly tons of stuff here) {3}
* cutedoll.shtml (contest?) {3} archive purposes only
* info (actual static model info files, non-db) {2} after database
* reviews (actual static model review files, non-db) {2} after database

OldSiteResourcesQuake2ToolsPrefabsHunter

2006-05-31T04:46:49Z

VitoMiliano:

__NOTOC__
{| border="1" cellpadding="2" cellspacing="0"
| '''[[PreFabs]] model'''
|-
| baseq2/players/Hunter_PreFabs
|}
Similar to the "Alx_Prefabs" these are a small collection of Primative shapes for use in creating various model meshes. It is not a model in the sense that you can play with them in game, but more for the purpose of learning to create basic shapes when learning to model. These shapes are somewhat more complex then they need to be (I will probably put together another set with others and maybe basic body parts too, arms, hands, torsos, etc) and can be optimized for your wn specific uses. The "spheres" are not Geo-spheres so they have a higher polycount than they should (Geo-spheres are much more efficient and I guess I just didnt think of including one (all the more reason for me to create another group too)) Basically there are two files. One file comes as one .md2 file with all the shapes included and the other is in .AQM ([[Q2Modeler]]) format. All you need to do is open or import the file to your modeling program and utilize the shapes you need, or cut, paste and save each to its own file.

Other Info : Technically these primatives were created in Qme and exported to .md2 format and converted to .AQM format too, but if you happen to use these in creating your own model, a nice mention in a read-me is sorta cool.. If you can think of other useful prefab shapes, send an e-mail to '''[mailto:Hunter@Polycount.com Hunter]''', and don't forget to check out [http://www.planetquake.com/polycount/resources/quake2/tools/Prefabs/Alx_Prefabs-info.shtml Big Rockets prefabs] too..

Stay tuned for more Prefabs.. soon... such as various body parts and generic forms for use in humanoid models.. any suggestions ????

Enjoy the Pre-fabs, they should be very useful for those using bare bones programs that don't offer primitive shape creation automatically.

attachment:Primatives.jpg

OldSiteResourcesQuake2ToolsPrefabsHunter

2006-05-31T04:46:01Z

VitoMiliano:

__NOTOC__
{| border="1" cellpadding="2" cellspacing="0"
|< 5 0 %>|'''[[PreFabs]] model'''
|-
|<5 0 %>|baseq2/players/Hunter_PreFabs
|}
Similar to the "Alx_Prefabs" these are a small collection of Primative shapes for use in creating various model meshes. It is not a model in the sense that you can play with them in game, but more for the purpose of learning to create basic shapes when learning to model. These shapes are somewhat more complex then they need to be (I will probably put together another set with others and maybe basic body parts too, arms, hands, torsos, etc) and can be optimized for your wn specific uses. The "spheres" are not Geo-spheres so they have a higher polycount than they should (Geo-spheres are much more efficient and I guess I just didnt think of including one (all the more reason for me to create another group too)) Basically there are two files. One file comes as one .md2 file with all the shapes included and the other is in .AQM ([[Q2Modeler]]) format. All you need to do is open or import the file to your modeling program and utilize the shapes you need, or cut, paste and save each to its own file.

Other Info : Technically these primatives were created in Qme and exported to .md2 format and converted to .AQM format too, but if you happen to use these in creating your own model, a nice mention in a read-me is sorta cool.. If you can think of other useful prefab shapes, send an e-mail to '''[mailto:Hunter@Polycount.com Hunter]''', and don't forget to check out [http://www.planetquake.com/polycount/resources/quake2/tools/Prefabs/Alx_Prefabs-info.shtml Big Rockets prefabs] too..

Stay tuned for more Prefabs.. soon... such as various body parts and generic forms for use in humanoid models.. any suggestions ????

Enjoy the Pre-fabs, they should be very useful for those using bare bones programs that don't offer primitive shape creation automatically.

OldSiteResourcesGeneralModelingAndAnimation

2006-05-31T04:23:25Z

VitoMiliano:

__NOTOC__
'''Modeling and Animation'''

[http://www.machinima.com/articles/modeling_intro_index/ KOWBOY's kickass 3D Studio Max r3 tutorial ]''' - [http://www.cfxweb.net/articles/hugi21/gf3ds01.shtml part 1]''', '''[http://www.cfxweb.net/articles/hugi21/gf3ds02.shtml part 2]''', '''[http://www.cfxweb.net/articles/hugi21/gf3ds03.shtml part 3]''', '''[http://www.cfxweb.net/articles/hugi21/gf3ds04.shtml part 4]''', '''[http://www.cfxweb.net/articles/hugi21/gf3ds05.shtml part 5]''', by [mailto:kowboy@nextempire.com Kowboy/Nextempire]
Some 3D Studio Max tutorials that are very good. The first one is targeted toward the beginner and is about the interface. The second is on basic model creation and getting started. Then in the third one we put in textures, then on to dealing with lighting, and finishing up with makin the suckah move. A fairly nice little set. Head over and look.

'''[http://www.planetquake.com/q3manga/modelling_tut1.htm ZeroCartin's Q3 Modelling tutorial in 3ds Max]''' by [mailto:zero_cartin@hotmail.com Zero Cartin]
A quick and dirty tutorial for modeling a torso, arms and head in 3DSMax. Brought to you by the [http://www.planetquake.com/q3manga/ Q3 Manga Mod] folks.

[http://www.users.qwest.net/~hayesbrian/modeling/modeling.htm Milkshape Tutorials] by [http://www.users.qwest.net/~hayesbrian/ Brian "-Iso-" Hayes]
A whole bunch of really good tutorials dealing with modeling in Milkshape. If you're a casual game artist without much dough and a good conscience this is probably the best modeling software available. If you're not sure how to use it, turn here. As with all tutorials in this section, many of the ideas presented can be carried to other software packages.

[http://www.gamasutra.com/features/visual_arts/19981113/charmod_01.htm Anatomically Correct Character Modeling] by Stefan Henry-Biskup (courtesy of [http://www.gamasutra.com/ Gamasutra])
A really nice tutorial/discussion on the finer points of modeling. Very useful if you're having trouble setting up bones in your bipedal creatures, and just a good resource in general.

[http://www.planetquake.com/polycount/resources/general/tutorials/SurfaceTools/SurfaceTools.shtml Surface Tools] by Scott A. H. Ruggels
This method of construction uses the native splines in Max, for the construction of "cages" that define the shape and volume of an object, and then use those splines to generate a surface, which is then converted to a polygonal mesh. Sound complicated? Well it's quickly becoming one of the most popular methods for constructing models.

[http://machinima.com/articles/modelling_intro_1/ Machinima Modeling Tutorials]''' - [http://machinima.com/articles/modelling_intro_1/ part 1]''', '''[http://machinima.com/articles/modelling_intro_2/ part 2]''', '''[http://machinima.com/articles/modelling_intro_3/ part 3]''', '''[http://machinima.com/articles/modelling_intro_4/ part 4]''', '''[http://machinima.com/articles/modelling_intro_5/ part 5]''', '''[http://machinima.com/articles/modelling_intro_6/ part 6]'''[http://machinima.com/articles/modelling_intro_6/ ] by [http://machinima.com/ Machinima.com]
A multi-part article and tutorial on making 3D characters and animations, speifically for use in real-time 3D engines such as the Quake series of engines. These tutorials are based in Milkshape, but the principles can be applied to many modeling packages. The last two installments get kind of game specific.

[http://www.planetquake.com/caphold/tutorials.html Modeling a Weapon with 3D Studio Max 3.0] by [http://www.planetquake.com/caphold/news.html Capture 'n Hold]
A tutorial for modeling weapons and creating mapping coordinates for them.

[http://www.planetquake.com/polycount/cottages/alcor/Truc/Truc.htm Alcor's Clever Ways] by [http://www.planetquake.com/polycount/cottages/alcor/ Alcor]
Some great tips from one of our very own, the author of Hellspawn, Witchblade, and the Mask. An absolute plethora of information on all manner of stuff, from skinning, to modeling to animating. Highly recommended.

[http://sgs.newsninja.com/Amazon/gwot/ GWOT's Tutorials and Links]
The author of the [../../../myweb/models/terminator.htm Terminator] model has compiled a set of tutorials that he's made as well as a set of link to different links around the community. Definitely worth a look around if you're looking for info on getting started. He's also pretty competent in 3D Studio MAX and can answer questions from newbies on that program

[http://max3d.3dluvr.com/tutorials/mms/ Mesh Modeling All the Way] by [mailto:strat@mail.bip.net Claes Wikdahl]
This tutorial explains the techniques and concepts behind mesh modeling as the author does it. It covers the basics and up, so that even beginners can get the hang of it. At the same time, this is all you need to know to create some really advanced models. This is really good stuff and almost required reading.

[http://www.roguespeardatabase.com/_tutorial/3dmax1.shtml How to Make 3D Weapon Models] by [http://www.roguespeardatabase.com/ The Rogue Spear Database]
How to model a gun in Max, pretty much. The concepts discussed in this tutorial can be applied to almost anything, so extrapolate what you may.

[http://www.planethalflife.com/coldfusion/tutorials/intro.htm ColdFusion's Modeling Tutorials] by [mailto:scarecrow@dial.pipex.com Scarecrow] of [http://www.planethalflife.com/coldfusion/ Cold Fusion]
Some absolutely wonderful tutorials for modeling, skinning and animating in Max or Milkshape.

[http://www.quake3mods.net/darkstar/tutorials.htm Modeling in Milkshape] by [http://www.quake3mods.net/darkstar/ Darkstar Entertainment]
Several tutorials, in .avi format, about modeling in a nice free program that's a viable alternative if you don't have the cash to shell out for the big boys.

[http://www.planetquake.com/polycount/cottages/shadokat/q2mtut.html ShadoKat's Q2Modeler Tutorial] by [mailto:shadokat@polycount.com ShadoKat]
Building a box using [[Q2Modeler]], a nice freeware modeling program. More installments are planned, but I wouldn't hold my breath. These are considered to be for the ABSOLUTE beginner.

[http://www.loonygames.com/content/1.13/totb/ Character Modeling] by [mailto:psteed@idsoftware.com Paul Steed]
Mr. Steed does a very nice tutorial on basic model creation in MAX. He shows us step by step creation of a character model including a few redos of some sections of the model. The model his called Sleeg, but it very well could be the start of the Sorlag model for Q3A. Comes in 3 parts: http://www.loonygames.com/content/1.14/totb/ part2]] [[http://www.loonygames.com/content/1.16/totb/ part3

[http://members.xoom.com/JohnHsia/tut1/edgeturn.html Edge Turn - Inside 3D MAX / volume 1] by John Hsia
Author's Note: Edge turn affects a single, shared edge by redirecting the edge to the other vertices of the two faces.

[http://members.xoom.com/JohnHsia/tut2/extrudearm.html Lets'Grow'Them'Arms - Inside 3D MAX / volume 1] by John Hsia
Author's Note: These next few pics will show you how I use extrude in some instances to grow arms. You can basically model your whole character this way, by selecting key faces where the head, arms and legs should be and extrude them out.

[http://www.planetquake.com/polycount/resources/general/tutorials/alphawolf_tut01/lowpolycharacters.shtml Low Polygon Character Generation using 3DSMAX 1.x or 2.0] by [mailto:Alphawolf@planetquake.com Andrew "ALPHAwolf" Gilmour]
This tutorial will guide you to build a low poly single mesh character starting with a box. There are various ways of building LPCs and this is just one method.
It's gotta be a good place to start if it's coming from ALPHAwolf's brain.

[http://www.3dcafe.com/tuts/shark/shark.htm Low Polygon Modeling In MAX R2.5]
Located in the [http://www.3dcafe.com 3D Cafe] by [http://www.platinumpictures.com Platinum Pictures] this modeling tutorial guides users step by step through the process of creating a low polygon shark. To all you budding MAX modelers out there, this could give you a few handy pointers.

[tutorials/Shine_Tut03/PolyReduce.shtml Polygon Reduction] by [mailto:vertmanip@cander.net Jon "shine" Jones]
This one goes through a high polygon count gun and shows some basic ideas and steps on deleting completely unused polygons and reducing polygon detail in areas that its just not needed. A nice tutorial for all new modelers for the concepts, not just for Lightwave users anymore.

[tutorials/Shine_Tut04/Making%20a%20Head.shtml Modeling A Head] by [mailto:vertmanip@cander.net Jon "shine" Jones]
Just when you thought you were about to bust from all the LW knowledge you now have, Shine come along with a pin to pop ya with another nice tutorial for you. The title pretty much says it all.

[http://www.loonygames.com/content/1.28/totb/ Character Studio basics] by [mailto:psteed@idsoftware.com Paul Steed]
This is a pair of tutorials on the basics of Character Studio's two parts, Biped and Physique. If you're looking to learn this plugin for MAX and don't have the manual [cough] for some reason, this is going to be your single best source tutorial for using it in the realm of player models. http://www.loonygames.com/content/1.30/totb/ part two

[http://www.planetquake.com/q2pmp/hostings/zedaxis/ Character Studio Tutorials]
For those looking to do a little Character Studio-ing, Nemesis has bitch slapped together many incredible Character Studio tutorials. Very useful lessons are going on at his home, [http://www.planetquake.com/q2pmp/hostings/zedaxis/ Zed-Axis], so get a move on!

'''[http://www.loonygames.com/content/1.22/totb/index2.shtml Walk cycle animation basics]''' by [mailto:psteed@idsoftware.com Paul Steed]
A basic and succinct tutorial on making a walk cycle for a character.

[tutorials/Shine_Tut05/Setup%20Bones%20Part1.shtml Setting up bones and IK in Lightwave, Part 1] by [mailto:vertmanip@cander.net Jon "shine" Jones]
IK isn't covered in this first part, but setting up a character with bones is. So if you're lookin' for Lightwave help, then check this one out and don't hesitate to check out all of shine's previous tutorials while you're at it!

PolycountOldTOC

2006-05-31T04:19:26Z

VitoMiliano:

__NOTOC__
<s> This was thrilling to compile. </s> This is ongoing thrills to convert to nice clean wiki formatting.

r13 has ranked pages to be converted in priority order. Pages that are crossed out and have a link next to them are ones that I have copy and pasted into the wiki. '''THEY ARE NOT DONE BEING CONVERTED YET.''' You (whoever is doing this) must go through each page and verify each link. If a link is dead, Google search to try and find it again. If it's really gone, check the internet archive for it and make a page for it here, including salvaging any images you can. You also need to go through and clean up all the wiki formatting: it's been converted automatically from the original HTML, so it is really digusting. These pages should be nice and clean and mostly plain text so we can put them on the main Polycount site again. That is all.

Please keep things in the list format. Dynamic pages that will be difficult to redirect properly are in italics.

= General Links =
* Poll (poll/poll.shtml) X
* ''News archives'' (news/newsarchives.asp)
* ''News search'' (news/newsarchives.asp?function=search&advanced=1)
* <s> Contact (contacts/index.shtml) {1} </s> [[OldSiteContact]]
* Polycount for PalmOS (news/pqa.zip) X
* Links (links/index.shtml) {2}
* <s> Credits (credits/index.shtml) {1} this should be merged with the contact page </s> [[OldSiteCredits]]
= Download Database =
* ''UT2004 Models, UT2004 Vehicles, UT2003 Models, Quake 3 Models, UT Models, JKA Models, JK2 Models, GTA3 Models, Serious Sam Models, Quake 2 Models, Q3 Map Models, TA Team Models, TA Head Models, Elite Force Models, Half-Life Models, Heretic2 Models, [[CounterStrike]] Models, The Sims Models, Kingpin Models'' (downloads/ and downloads/index.asp?game=##&sort=date&order=DESC) {2}
= Other Models and Skins =
* Q3 Weapon Models (q3weapons/q3weapons-index.shtml) {3}
* HL Weapon Models (hlweapons/hlweapons-index.shtml) {3}
* UT2003 Accessories (dynamic.gamespy.com/~polycount/skins/ut2003skin-index.shtml wtf?) {3}
* Quake 2 Accessories (skins/q2skin-index.shtml) {3}
* Quake 3 Accessories (skins/q3skin-index.shtml) {3}
* Unreal T Accessories (skins/utskin-index.shtml) {3}
* Half-Life Accessories (skins/hlskin-index.shtml) {3}
* Rune Accessories (skins/runeskin-index.shtml) {3}
* Sims Accessories (skins/simskin-index.shtml) {3}
* Accessory Top-Picks (skins/top-picks/top-picks.shtml) {3} potentially X
* Top-Packs (skins/top-picks/top-packs/top-packs.shtml {3} potentially X
= Resources =
* <s> Resources (resources/index.shtml) {1} we should be able to get alot of the heavy lifting here from the community </s> [[OldSiteResources]]

Under Resources, there are these directories and significant files. Directories without any sub-content just have an index.shtml file in them listing resources elsewhere on the net. Most directories also have lots of other directories with supporting files, like images and stuff, which aren't listed for brevity.

* avp2 {3}
** index.shtml
** tutorials
*** talonengine
**** talonenginetut.shtml
* bandw {3} {i} wtf is this? Black and White
* chat-rooms {2}
** chat-index.shtml
** 2design X
*** 2design.shtml
* model_design
** model_design.shtml
* modjobs X
** modjobs.shtml
* drakan {3}
** index.shtml
** gfx
*** JSheffield.zip
* eliteforce {3}
** index.shtml
** tutorials.shtml
** tutorials
*** q3-ef
**** Q3AEF.shtml
* <s> FAQ-genera {1} probably needs reviewl </s>
** <s> faq-general-index.shtml</s> [[OldSiteResourcesFaqGeneral]]
* <s> general {1} </s> [[OldSiteResourcesGeneral]]
** misc {i} sunstorm?
*** sunstorm.shtml
* <s> tools {1} </s> [[OldSiteResourcesGeneralTools]]
** <s> infografica.shtml </s> [[OldSiteResourcesGeneralToolsInfografica]]
** <s> polychop </s>
*** <s> gdmag.pdf </s> [[OldSiteResourcesGeneralToolsPolyChop]]
* tutorials {2}
** ALPHAWolf_Tut01
*** Low<code><nowiki></nowiki></code>Poly<code><nowiki></nowiki></code>Characters.shtml
* cswingstut
** cswingstut.shtml
* Hitman<code><nowiki></nowiki></code>Daz_Tut01
** Digital<code><nowiki></nowiki></code>Painting.shtml
* Model-unwrap
** model-unwrap.shtml
** model-unwrap-pic1.shtml
** model-unwrap-pic2.shtml
** model-unwrap-pic3.shtml
** model-unwrap-pic4.shtml
** model-unwrap-pic5.shtml
* NURBS-mapping
** Nurbs-mapping.shtml
** tutorial.html
** vrml1.html
** vrml2.html
** vrml3.html
* Shine_Tut03
** Poly<code><nowiki></nowiki></code>Reduce.shtml
* Shine_Tut04
** Making a Head.shtml
* Shine_Tut05
** Setup Bones Part1.shtml
* Surface<code><nowiki></nowiki></code>Tools
** Surface Tools for Low Poly Modeling2.doc
** Surface<code><nowiki></nowiki></code>Tools.shtml
** Surface<code><nowiki></nowiki></code>Tools-mts.shtml
* UVWunwrap
** UVWunwrap.shtml
* ASC_Export_Tut01.shtml
** Shine_Tut01.shtml
** Shine_Tut02.shtml
* <s> video_tutorials {1} </s>
** <s> video-tut-list.shtml </s> [[OldSiteResourcesGeneralVideoTutorials]]
* <s> apps.shtml {1} </s> [[OldSiteResourcesGeneralApplications]]
** <s> genmisc.shtml {1} </s> [[OldSiteResourcesGeneralMiscellaneous]]
** index.shtml
** <s> lightwave.shtml {1} </s> [[OldSiteResourcesGeneralLightwave]]
** <s> max.shtml {1} </s> [[OldSiteResourcesGeneralMax]]
** <s> maya.shtml {1} </s> [[OldSiteResourcesGeneralMaya]]
** <s> milkshape.shtml {1} </s> [[OldSiteResourcesGeneralMilkshape]]
** misc.shtml {1}
** modelanim.shtml {1}
** nst.shtml {3}
** q2m.shtml {3}
** skinning.shtml {1}
** tools.shtml {1}
** tutindex.shtml
** tutorials.shtml
* gfx (looks like game logos for pages maybe) {i} i suspect it is, thats what i think its a dup of that other directory
* glossary (24 pages of definitions plus images) {1}
* glossary2 (only one glossary page, but lots of examples files) {1} can we consolidate these?
* gta3 {3}
* halflife {2}
** index.shtml
** tools.shtml
** tutorials.shtml
** tutorials (directory with 20 pages of modeling tutorials plus example content)
* heretic2 {3}
** index.shtml
** tools.shtml
** tutorials.shtml
* jk2 {3}
** index.shtml
** tutorials
*** Model<code><nowiki></nowiki></code>Tutorial (eight files under here making this up)
*** jk2_model_construction.shtml
* kingpin {3}
** tools
*** framelist.shtml
*** tools.shtml
* index.shtml
** Kingpin-animations.html
* lithtech {3}
** tutorials
*** lithtech_primer.shtml
* index.shtml
** tools.shtml
** tutorials.shtml
* manual (how to review a model?) {i} it may go X
* nolf {3}
* quake {2}
** FAQ.shtml
** index.shtml
** tools.shtml
** tutorials.shtml
* quake2 {1}
** tools
*** Prefabs
**** Alx_Prefabs-info.shtml
**** Hunter_Prefabs-info.shtml
** Testbox
*** testbox.shtml
* tutorials
** NGLV
** NST_Tut01
** Custom VWEP.shtml
** NST_Retro<code><nowiki></nowiki></code>Map.shtml
** Weapon Skin Linking.shtml
* FAQ.shtml
** index.shtml
** md2text.txt
** q2frameslist.shtml
** tools.shtml
** tutorials.shtml
* quake3 {1}
** Model_Doc
*** Model_manual_ps.htm
* Shader_Doc
** Q3<code><nowiki></nowiki></code>Ashader_manual.htm
* tools
** tutorials (lots of files below these, ugh)
*** josh
*** max-to-q3
*** MAX-to-q3data
*** Skin-shader
*** Sound<code><nowiki></nowiki></code>Pak
*** Steed-Tut
* index.shtml
** md3text.txt
** tools.shtml
** tutorials.shtml
* rune {3}
** tutorials
*** lodsettings
**** runetut-lodsettings.shtml
* index.shtml
* sims {3}
** index.shtml
** tools.shtml
** tutorials.shtml
* ssam {3}
* thps {3} {i}
* tribes {3}
** index.shtml
** tools.shtml
** tutorials.shtml
* unreal {2}
** tools
** tutorials (lots of files in these subdirs)
*** lodsettings
*** mage
*** pix
*** sounds
*** umod
*** umod-backup
*** UTut01.shtml
*** UTut02.shtml
*** UTut03.shtml
*** UTut04.shtml
*** UTut05.shtml
*** UTut06.shtml
*** Utut07.shtml
* index.shtml
** tools.shtml
** tutorials.shtml
** UTtut-mainpage.shtml
** UTtut-part5.shtml
* ut2003 {1}
** tutorials
*** backups (this might just be backup content, not sure, something about Intertwined)
*** ut2mod
*** pushing_tutorial.shtml
* index.shtml
** tools.shtml
** tutorials.shtml
Also what I'd consider resources are:

* Good, Bad and Ugly (skins/gbu/* with eight article directories under it) {2}
* Skin news archives (skins/archived-news/* with 30 pages of news under it) {i} no idea
* Articles (ten article directories below that:) {2}
** animation-tips
** BnW<code><nowiki></nowiki></code>interview
** chiq_interview_012602
** chrisbruce_072002
** Gwot062k2
** max3preview
** q3-model-preview
** Steed-gdc99
** Steed-Interview
** Steed-Interview-2
* Subdermal (six pages and a contest) {2}

= Not Linked To =
* [[AskDev]] (ask a developer column?) X this didnt pan out. a dev house wanted to help just answer questions. But pulled out right as we set it all up.
* docs/gamespace_release.zip X
* misc
** Discreet_QCon2k1 {3} {i} needs review
** e32k4 {3} {i} needs review
** gfx {i} is this just a directory full of original polycount gfx?
** id-model-renders {3}
** pimps {3} {i} needs review
** 12-3action.htm {3} {i} needs review
** gamespy-broadcastkey.txt X
** lead_action_designer.doc X
** micro-forte-syd-jobdoc.shtml X
** stuff.htm {3} {i} needs review
** Unreal_Coach_jobpost_053104.doc X
* modeloftheweek X
* modelpacks {3}
* paintchat {2} conditional that we can get it working again, free/cheap. if not... X
* previews X
** nicknacks X
* reviewlists X
* skindom (woah nelly tons of stuff here) {3}
* cutedoll.shtml (contest?) {3} archive purposes only
* info (actual static model info files, non-db) {2} after database
* reviews (actual static model review files, non-db) {2} after database

OldSiteResourcesGeneralMilkshape

2006-05-31T04:16:11Z

VitoMiliano:

__NOTOC__
'''Milkshape Tutorials'''

[http://www.users.qwest.net/~hayesbrian/modeling/modeling.htm Milkshape Tutorials] by [http://www.users.qwest.net/~hayesbrian/ Brian "-Iso-" Hayes]
A whole bunch of really good tutorials dealing with modeling in Milkshape. If you're a casual game artist without much dough and a good conscience this is probably the best modeling software available. If you're not sure how to use it, turn here.

[http://www.planethalflife.com/coldfusion/tutorials/intro.htm ColdFusion's Modeling Tutorials] by [mailto:scarecrow@dial.pipex.com Scarecrow] of [http://www.planethalflife.com/coldfusion/ Cold Fusion]
Some absolutely wonderful tutorials for modeling, skinning and animating in Max or Milkshape.

[http://www.quake3mods.net/darkstar/tutorials.htm Modeling in Milkshape] by [http://www.quake3mods.net/darkstar/ Darkstar Entertainment]
Several tutorials, in .avi format, about modeling in a nice free program that's a viable alternative if you don't have the cash to shell out for the big boys.

[http://www.machinima.com/articles/modeling_intro_index/ Machinima Modeling Tutorials]''' - [http://machinima.com/articles/modelling_intro_1/ part 1]''', '''[http://machinima.com/articles/modelling_intro_2/ part 2]''', '''[http://machinima.com/articles/modelling_intro_3/ part 3]''', '''[http://machinima.com/articles/modelling_intro_4/ part 4]''', '''[http://machinima.com/articles/modelling_intro_5/ part 5]''', '''[http://machinima.com/articles/modelling_intro_6/ part 6]'''[http://machinima.com/articles/modelling_intro_6/ ] by [http://machinima.com/ Machinima.com]
A multi-part article and tutorial on making 3D characters and animations, speifically for use in real-time 3D engines such as the Quake series of engines. These tutorials are based in Milkshape, but the principles can be applied to many modeling packages. The last two installments get kind of game specific.

OldSiteResourcesGeneralMaya

2006-05-31T04:15:12Z

VitoMiliano:

__NOTOC__
'''Maya and Maya PLE Tutorials'''

'''[http://www.planetquake.com/sin2q3/tutpart1.htm Modeling a Simple Low-Poly Human with Maya] - [http://www.planetquake.com/sin2q3/tutpart1.htm Part 1], [http://www.planetquake.com/sin2q3/tutpart2.htm Part 2]''' by Undertow of [http://www.planetquake.com/sin2q3/ Sin Arena]
A very nice and detailed tutorial on modeling a low-polygon humanoid figure using Alias|Wavefront's Maya.

OldSiteResourcesGeneralMax

2006-05-31T04:13:55Z

VitoMiliano:

__NOTOC__
'''3D Studio MAX and gmax Tutorials'''

'''[http://gmax.digitalarenas.com/modules.php?op=modload&name=Sections&file=index&req=viewarticle&artid=7 Beginning gmax - How to Model a Cart]''' by Paul Beattie
Just what it says. A tutorial for modeling a cart with gmax.

'''[http://www.flipcode.com/tutorials/spaceship/ Modeling a Simple Spaceship]''' by [http://ghoul.flipcode.com/ Max Shelekhov]
Just what it says. A tutorial for modeling a simple spaceship with either Max or gmax.

[http://www.machinima.com/articles/modeling_intro_index/ KOWBOY's kickass 3D Studio Max r3 tutorial ]''' - [http://www.cfxweb.net/articles/hugi21/gf3ds01.shtml part 1]''', '''[http://www.cfxweb.net/articles/hugi21/gf3ds02.shtml part 2]''', '''[http://www.cfxweb.net/articles/hugi21/gf3ds03.shtml part 3]''', '''[http://www.cfxweb.net/articles/hugi21/gf3ds04.shtml part 4]''', '''[http://www.cfxweb.net/articles/hugi21/gf3ds05.shtml part 5]''', by [mailto:kowboy@nextempire.com Kowboy/Nextempire]
Some 3D Studio Max tutorials that are very good. The first one is targeted toward the beginner and is about the interface. The second is on basic model creation and getting started. Then in the third one we put in textures, then on to dealing with lighting, and finishing up with makin the suckah move. A fairly nice little set. Head over and look.

'''[http://www.planetquake.com/q3manga/modelling_tut1.htm ZeroCartin's Q3 Modelling tutorial in 3ds Max]''' by [mailto:zero_cartin@hotmail.com Zero Cartin]
A quick and dirty tutorial for modeling a torso, arms and head in 3DSMax. Brought to you by the [http://www.planetquake.com/q3manga/ Q3 Manga Mod] folks.

[http://www.planetquake.com/polycount/resources/general/tutorials/cswingstut/cswingstut.shtml Tutorial on how to animate wings using Character Studio] by [mailto:SkullboX@planetquake.com Bastiaan "SkullboX" Schravendeel]
Just what it says. A nicely detailed tutorial on how to add bones to a Biped object in Max so you can animate all those extra bits. You'll definitely find this one useful if your imagination tends to extend beyond the standard "two-legged-humanoid" characters.

[http://www.maxforums.org/ MaxForums]
Your one stop source for all the 3D Studio MAX tutorials you could ever want or need. Seriously, if you’re a MAX user, you NEED this place, and should go here often. Just click on the Tutorials link in the nav-bar. While you’re there, be sure to browse around, as they also have message boards.

[http://www.planetquake.com/polycount/cottages/zedaxis/ Zed-Axis Tutorials] by [mailto:nemesis@lightwolf.com Nemesis]
Some nice 3DStudioMax tutorials. But these are no regular ones. These are full video with sound captures of him actually going through the procedures of making the models. These really big (100+ MB) downloads but, if you email him with 20$ for shipping and the cost of the CD, he will burn it to disc and send it to you.

[http://max3d.3dluvr.com/tutorials/mms/ Mesh Modeling All the Way] by [mailto:strat@mail.bip.net Claes Wikdahl]
This tutorial explains the techniques and concepts behind mesh modeling as the author does it. It covers the basics and up, so that even beginners can get the hang of it. At the same time, this is all you need to know to create some really advanced models. This is really good stuff and almost required reading.

[http://jurassic.mpog.com Unwrapping tutorials] by [http://jurassic.mpog.com/ Vision Studios]
A fabulous tutorial explaining how to generate texture co-ordinates for 3d models (unwrapping), from one bitmap to multiple bitmaps on a single mesh. This is some pretty handy stuff when you are knee-deep in the model-making process. Click the portfolio link in the nav-bar and you’ll see it in there.

[http://welbot.8m.com/UVtut/ UV Unwrapping] by [mailto:webmaster@welbot.8m.com Welbot]
A very nice tutorial explaining how to lay out a texture map for your 3d models using 3DSMax. This tutorial also makes use of the [http://www.cuneytozdas.com/software/max/texporter/ Texporter] plugin, so go get that before you start. It assumes you have a completed mesh, ready to be skinned, so be sure you have one of those.

[tutorials/ASC_Export_Tut01.shtml ASC Exporter Plugin] by [mailto:melkior@usa.net rogue13]
Instructs on the use of the ASC exporter for getting Max models into Q2 Modeler for skin generation and compiling to MD2 format.

[http://www.planetquake.com/polycount/cottages/alcor/Truc/Truc.htm Alcor's Clever Ways] by [http://www.planetquake.com/polycount/cottages/alcor/ Alcor]
Some great tips from one of our very own, the author of Hellspawn, Witchblade, and the Mask. An absolute plethora of information on all manner of stuff, from skinning, to modeling to animating. Highly recommended.

'''[http://epicknights.com/tutorials/multiple_materials_max.shtml Applying Multiple Materials to an Object in Max]''' by [jgreen@epicgames.com James Green]
Epic's very own James Green has graced us with this tutorial on setting up multiple materials to apply to a single object in Max. Very useful even if your model's not for Unreal Tournament.

[http://www.3d-editing.com/coldfusion/tutorials.htm ColdFusion's Modeling Tutorials] by [mailto:scarecrow@dial.pipex.com Scarecrow] of [http://www.3d-editing.com/coldfusion/ Cold Fusion]
Some absolutely wonderful tutorials for modeling, skinning and animating in Max or Milkshape.

[http://sgs.newsninja.com/Amazon/gwot/ GWOT's Tutorials and Links]
The author of the [../../../myweb/models/terminator.htm Terminator] model has compiled a set of tutorials that he's made as well as a set of link to different links around the community. Definitely worth a look around if you're looking for info on getting started. He's also pretty competent in 3D Studio MAX and can answer questions from newbies on that program

[http://www.converted2.com/dev/index.php3?issue=7 Basic Texture Mapping in MAX 2.x] by [mailto:shockman/@converted2.com Shockman] from the [http:\\chemical.valveworld.com Chemical Existence] TC
discuss basic issues of texture mapping using the standard UV tools inside of MAX.

[http://www.loonygames.com/content/1.28/totb/ Character Studio basics] by [mailto:psteed@idsoftware.com Paul Steed]
This is a pair of tutorials on the basics of Character Studio's two parts, Biped and Physique. If you're looking to learn this plugin for MAX and don't have the manual [cough] for some reason, this is going to be your single best source tutorial for using it in the realm of player models. http://www.loonygames.com/content/1.30/totb/ part two

[http://www.planetquake.com/q2pmp/hostings/zedaxis/ Character Studio Tutorials]
For those looking to do a little Character Studio-ing, Nemesis has bitch slapped together many incredible Character Studio tutorials. Very useful lessons are going on at his home, [http://www.planetquake.com/q2pmp/hostings/zedaxis/ Zed-Axis], so get a move on!

[http://www.fvfworld.com/features/q3a_mod_02/ FvFWorld's MAX Skinning Tutorial] by [http://www.fvfworld.com FvFWorld]
Those of you messing around with Max and need to learn how to get those lovely texture maps on your model properly will want to check this out. The tutorial isn't the end all of skinning methods, but this will get you there nicely if you have no clue to any other way.

[http://www.loonygames.com/content/1.13/totb/ Character Modeling] by [mailto:psteed@idsoftware.com Paul Steed]
Mr. Steed does a very nice tutorial on basic model creation in MAX. He shows us step by step creation of a character model including a few redos of some sections of the model. The model his called Sleeg, but it very well could be the start of the Sorlag model for Q3A. Comes in 3 parts: http://www.loonygames.com/content/1.14/totb/ part2]] [[http://www.loonygames.com/content/1.16/totb/ part3

[tutorials/NURBS-mapping/Nurbs-mapping.shtml Character Texture Mapping Via NURBS projection] by [mailto:benny@kainai.de Benny Edlund]
A very interesting approach to doing texture mapping with NURBS and primitives as projection items to help minimize texture stretching and speed mapping.

[http://members.xoom.com/JohnHsia/tut1/edgeturn.html Edge Turn - Inside 3D MAX / volume 1] by John Hsia
Author's Note: Edge turn affects a single, shared edge by redirecting the edge to the other vertices of the two faces.

[http://members.xoom.com/JohnHsia/tut2/extrudearm.html Lets'Grow'Them'Arms - Inside 3D MAX / volume 1] by John Hsia
Author's Note: These next few pics will show you how I use extrude in some instances to grow arms. You can basically model your whole character this way, by selecting key faces where the head, arms and legs should be and extrude them out.

[../../../myweb/dev_central1/tutorials/ALPHAtut/tut_01.htm Low Polygon Character Generation using 3DSMAX 1.x or 2.0] by [mailto:Alphawolf@planetquake.com Andrew "ALPHAwolf" Gilmour]
This tutorial will guide you to build a low poly single mesh character starting with a box. There are various ways of building LPCs and this is just one method.
It's gotta be a good place to start if it's coming from ALPHAwolf's brain.

[http://www.3dcafe.com/tuts/shark/shark.htm Low Polygon Modeling In MAX R2.5]
Located in the [http://www.3dcafe.com 3D Cafe] by [http://www.platinumpictures.com Platinum Pictures] this modeling tutorial guides users step by step through the process of creating a low polygon shark. To all you budding MAX modelers out there, this could give you a few handy pointers.

[http://www.cschell.com/skinmaxtut.html Model Skinning in Max 2.x] by [http://www.cschell.com/ casManG]
A pretty straightforward tutorial on skinning a model in MAX. This is sort of outdated by MAX 3, but the principles still work if you find you like this better.

[http://www.planetquake.com/caphold/tutorials.html Modeling a Weapon with 3D Studio Max 3.0] by [http://www.planetquake.com/caphold/news.html Capture 'n Hold]
A tutorial for modeling weapons and creating mapping coordinates for them.

[http://www.planetquake.com/polycount/resources/general/tutorials/SurfaceTools/SurfaceTools.shtml Surface Tools] by Scott A. H. Ruggels
This method of construction uses the native splines in Max, for the construction of "cages" that define the shape and volume of an object, and then use those splines to generate a surface, which is then converted to a polygonal mesh. Sound complicated? Well it's quickly becoming one of the most popular methods for constructing models.

[tutorials/UVWunwrap/UVWunwrap.shtml Using the UVWunwrap+ modifer] by [mailto:Daz@cybermodels.co.uk Darren "Hitman Daz' Pattenden]
A quick how-to on the basics of using this custom modifier by [mailto:Speuger@home.com Spuege]r and [mailto:Gwot@planetquake.com Gwot] to help texture map your models in MAX.

'''[http://www.loonygames.com/content/1.22/totb/index2.shtml Walk cycle animation basics]''' by [mailto:psteed@idsoftware.com Paul Steed]
A basic and succinct tutorial on making a walk cycle for a character.

OldSiteResourcesGeneralLightwave

2006-05-31T04:12:22Z

VitoMiliano:

__NOTOC__
'''Lightwave Tutorials'''

[tutorials/Shine_Tut01.shtml Exporting the Model] by [mailto:vertmanip@cander.net Jon "shine" Jones]
A quick description to get your model from the 3D environment into..er.. another 3D environment, but in the second one you can kill it so it's much higher in the cool points.

[tutorials/Shine_Tut02.shtml Introduction to Lightwave] by [mailto:vertmanip@cander.net Jon "shine" Jones]
A very direct tutorial relating to Lightwave. Lots of tips and information...nothing all that complex or involved, but still a pile of valuable information.

[tutorials/Shine_Tut03/PolyReduce.shtml Polygon Reduction] by [mailto:vertmanip@cander.net Jon "shine" Jones]
This one goes through a high polygon count gun and shows some basic ideas and steps on deleting completely unused polygons and reducing polygon detail in areas that its just not needed. A nice tutorial for all new modelers for the concepts, not just for Lightwave users anymore.

[tutorials/Shine_Tut04/Making%20a%20Head.shtml Modeling A Head] by [mailto:vertmanip@cander.net Jon "shine" Jones]
Just when you thought you were about to bust from all the LW knowledge you now have, Shine come along with a pin to pop ya with another nice tutorial for you. The title pretty much says it all.

[tutorials/Shine_Tut05/Setup%20Bones%20Part1.shtml Setting up bones and IK in Lightwave, Part 1] by [mailto:vertmanip@cander.net Jon "shine" Jones]
IK isn't covered in this first part, but setting up a character with bones is. So if you're lookin' for Lightwave help, then check this one out and don't hesitate to check out all of shine's previous tutorials while you're at it!

OldSiteResourcesGeneralMiscellaneous

2006-05-31T04:10:24Z

VitoMiliano:

__NOTOC__
'''General Tutorials'''

[tutorials/ASC_Export_Tut01.shtml 3D Exploration: How to Display Textures] by [http://www.planetquake.com/skindom Skindom]
The subject of this baby is the [http://www.us.righthemisphere.com/products/3dexplore/index.htm 3D Exploration] program and its use when displaying textures. Also included are some tips on showing models that don't have textures to display.

[tutorials/ASC_Export_Tut01.shtml ASC Exporter Plugin] by [mailto:melkior@usa.net rogue13]
Instructs on the use of the ASC exporter for getting Max models into Q2 Modeler for skin generation and compiling to MD2 format.

[http://www.sijun.com/dhabih/mainscreen.html dhabih eng's tutorials] by [http://www.sijun.com/dhabih/mainscreen.html dhabih eng]
He's got a few nice trips down through his process for producing computer art with a Wacom tablet and Photoshop. I'd link it directly but he's running frames. look around, you'll find lots of good stuff anyways.

[http://www.planetquake.com/polycount/cottages/alcor/Truc/Truc.htm Alcor's Clever Ways] by [http://www.planetquake.com/polycount/cottages/alcor/ Alcor]
Some great tips from one of our very own, the author of Hellspawn, Witchblade, and the Mask. An absolute plethora of information on all manner of stuff, from skinning, to modeling to animating. Highly recommended.

[http://sgs.newsninja.com/Amazon/gwot/ GWOT's Tutorials and Links]
The author of the [../../../myweb/models/terminator.htm Terminator] model has compiled a set of tutorials that he's made as well as a set of link to different links around the community. Definitely worth a look around if you're looking for info on getting started. He's also pretty competent in 3D Studio MAX and can answer questions from newbies on that program

[http://www.converted2.com/dev/index.php3?issue=7 Basic Texture Mapping in MAX 2.x] by [mailto:shockman/@converted2.com Shockman] from the [http:\\chemical.valveworld.com Chemical Existence] TC
discuss basic issues of texture mapping using the standard UV tools inside of MAX.

[http://www.loonygames.com/content/1.28/totb/ Character Studio basics] by [mailto:psteed@idsoftware.com Paul Steed]
This is a pair of tutorials on the basics of Character Studio's two parts, Biped and Physique. If you're looking to learn this plugin for MAX and don't have the manual [cough] for some reason, this is going to be your single best source tutorial for using it in the realm of player models. http://www.loonygames.com/content/1.30/totb/ part two

[http://www.fvfworld.com/features/q3a_mod_02/ FvFWorld's MAX Skinning Tutorial] by [http://www.fvfworld.com FvFWorld]
Those of you messing around with Max and need to learn how to get those lovely texture maps on your model properly will want to check this out. The tutorial isn't the end all of skinning methods, but this will get you there nicely if you have no clue to any other way.

[http://www.cschell.com/skinmaxtut.html Model Skinning in Max 2.x] by [http://www.cschell.com/ casManG]
A pretty straightforward tutorial on skinning a model in MAX. This is sort of outdated by MAX 3, but the principles still work if you find you like this better.

'''[http://www.loonygames.com/content/1.22/totb/index2.shtml Walk cycle animation basics]''' by [mailto:psteed@idsoftware.com Paul Steed]
A basic and succinct tutorial on making a walk cycle for a character.

[tutorials/Shine_Tut01.shtml Exporting the Model] by [mailto:vertmanip@cander.net Jon "shine" Jones]
A quick description to get your model from the 3D environment into..er.. another 3D environment, but in the second one you can kill it so it's much higher in the cool points.

[tutorials/Shine_Tut02.shtml Introduction to Lightwave] by [mailto:vertmanip@cander.net Jon "shine" Jones]
A very direct tutorial relating to Lightwave. Lots of tips and information...nothing all that complex or involved, but still a pile of valuable information.

[tutorials/Shine_Tut03/PolyReduce.shtml Polygon Reduction] by [mailto:vertmanip@cander.net Jon "shine" Jones]
This one goes through a high polygon count gun and shows some basic ideas and steps on deleting completely unused polygons and reducing polygon detail in areas that its just not needed. A nice tutorial for all new modelers for the concepts, not just for Lightwave users anymore.

[tutorials/Shine_Tut05/Setup%20Bones%20Part1.shtml Setting up bones and IK in Lightwave, Part 1] by [mailto:vertmanip@cander.net Jon "shine" Jones]
IK isn't covered in this first part, but setting up a character with bones is. So if you're lookin' for Lightwave help, then check this one out and don't hesitate to check out all of shine's previous tutorials while you're at it!

OldSiteResourcesGeneralApplications

2006-05-31T04:08:39Z

VitoMiliano:

__NOTOC__
'''Tutorials'''

'''[max.shtml 3D Studio MAX]'''

'''[lightwave.shtml Lightwave]'''

'''[milkshape.shtml Milkshape]'''

'''[q2m.shtml Quake 2 Modeler]'''

'''[nst.shtml NPherno's Skin Tool (NST)]'''

'''[[resources/general/tutorials/ASC Export Tut01.shtml|ASC Importer Plugin*]]'''

PolycountOldTOC

2006-05-31T03:59:00Z

VitoMiliano:

__NOTOC__
This was thrilling to compile. Please keep things in the list format. Dynamic pages that will be difficult to redirect properly are in italics.

= General Links =
* Poll (poll/poll.shtml) X
* ''News archives'' (news/newsarchives.asp)
* ''News search'' (news/newsarchives.asp?function=search&advanced=1)
* <s> Contact (contacts/index.shtml) {1} </s> [[OldSiteContact]]
* Polycount for PalmOS (news/pqa.zip) X
* Links (links/index.shtml) {2}
* <s> Credits (credits/index.shtml) {1} this should be merged with the contact page </s> [[OldSiteCredits]]
= Download Database =
* ''UT2004 Models, UT2004 Vehicles, UT2003 Models, Quake 3 Models, UT Models, JKA Models, JK2 Models, GTA3 Models, Serious Sam Models, Quake 2 Models, Q3 Map Models, TA Team Models, TA Head Models, Elite Force Models, Half-Life Models, Heretic2 Models, [[CounterStrike]] Models, The Sims Models, Kingpin Models'' (downloads/ and downloads/index.asp?game=##&sort=date&order=DESC) {2}
= Other Models and Skins =
* Q3 Weapon Models (q3weapons/q3weapons-index.shtml) {3}
* HL Weapon Models (hlweapons/hlweapons-index.shtml) {3}
* UT2003 Accessories (dynamic.gamespy.com/~polycount/skins/ut2003skin-index.shtml wtf?) {3}
* Quake 2 Accessories (skins/q2skin-index.shtml) {3}
* Quake 3 Accessories (skins/q3skin-index.shtml) {3}
* Unreal T Accessories (skins/utskin-index.shtml) {3}
* Half-Life Accessories (skins/hlskin-index.shtml) {3}
* Rune Accessories (skins/runeskin-index.shtml) {3}
* Sims Accessories (skins/simskin-index.shtml) {3}
* Accessory Top-Picks (skins/top-picks/top-picks.shtml) {3} potentially X
* Top-Packs (skins/top-picks/top-packs/top-packs.shtml {3} potentially X
= Resources =
* <s> Resources (resources/index.shtml) {1} we should be able to get alot of the heavy lifting here from the community </s> [[OldSiteResources]]

Under Resources, there are these directories and significant files. Directories without any sub-content just have an index.shtml file in them listing resources elsewhere on the net. Most directories also have lots of other directories with supporting files, like images and stuff, which aren't listed for brevity.

* avp2 {3}
** index.shtml
** tutorials
*** talonengine
**** talonenginetut.shtml
* bandw {3} {i} wtf is this? Black and White
* chat-rooms {2}
** chat-index.shtml
** 2design X
*** 2design.shtml
* model_design
** model_design.shtml
* modjobs X
** modjobs.shtml
* drakan {3}
** index.shtml
** gfx
*** JSheffield.zip
* eliteforce {3}
** index.shtml
** tutorials.shtml
** tutorials
*** q3-ef
**** Q3AEF.shtml
* <s> FAQ-genera {1} probably needs reviewl </s>
** <s> faq-general-index.shtml</s> [[OldSiteResourcesFaqGeneral]]
* <s> general {1} </s> [[OldSiteResourcesGeneral]]
** misc {i} sunstorm?
*** sunstorm.shtml
* <s> tools {1} </s> [[OldSiteResourcesGeneralTools]]
** <s> infografica.shtml </s> [[OldSiteResourcesGeneralToolsInfografica]]
** <s> polychop </s> [[OldSiteResourcesGeneralToolsPolyChop]]
*** <s> gdmag.pdf </s> attached to the above
* tutorials {2}
** ALPHAWolf_Tut01
*** Low<code><nowiki></nowiki></code>Poly<code><nowiki></nowiki></code>Characters.shtml
* cswingstut
** cswingstut.shtml
* Hitman<code><nowiki></nowiki></code>Daz_Tut01
** Digital<code><nowiki></nowiki></code>Painting.shtml
* Model-unwrap
** model-unwrap.shtml
** model-unwrap-pic1.shtml
** model-unwrap-pic2.shtml
** model-unwrap-pic3.shtml
** model-unwrap-pic4.shtml
** model-unwrap-pic5.shtml
* NURBS-mapping
** Nurbs-mapping.shtml
** tutorial.html
** vrml1.html
** vrml2.html
** vrml3.html
* Shine_Tut03
** Poly<code><nowiki></nowiki></code>Reduce.shtml
* Shine_Tut04
** Making a Head.shtml
* Shine_Tut05
** Setup Bones Part1.shtml
* Surface<code><nowiki></nowiki></code>Tools
** Surface Tools for Low Poly Modeling2.doc
** Surface<code><nowiki></nowiki></code>Tools.shtml
** Surface<code><nowiki></nowiki></code>Tools-mts.shtml
* UVWunwrap
** UVWunwrap.shtml
* ASC_Export_Tut01.shtml
** Shine_Tut01.shtml
** Shine_Tut02.shtml
* video_tutorials {1}
** video-tut-list.shtml
* apps.shtml {1}
** genmisc.shtml {1}
** index.shtml
** lightwave.shtml {1}
** max.shtml {1}
** maya.shtml {1}
** milkshape.shtml {1}
** misc.shtml {1}
** modelanim.shtml {1}
** nst.shtml {3}
** q2m.shtml {3}
** skinning.shtml {1}
** tools.shtml {1}
** tutindex.shtml
** tutorials.shtml
* gfx (looks like game logos for pages maybe) {i} i suspect it is, thats what i think its a dup of that other directory
* glossary (24 pages of definitions plus images) {1}
* glossary2 (only one glossary page, but lots of examples files) {1} can we consolidate these?
* gta3 {3}
* halflife {2}
** index.shtml
** tools.shtml
** tutorials.shtml
** tutorials (directory with 20 pages of modeling tutorials plus example content)
* heretic2 {3}
** index.shtml
** tools.shtml
** tutorials.shtml
* jk2 {3}
** index.shtml
** tutorials
*** Model<code><nowiki></nowiki></code>Tutorial (eight files under here making this up)
*** jk2_model_construction.shtml
* kingpin {3}
** tools
*** framelist.shtml
*** tools.shtml
* index.shtml
** Kingpin-animations.html
* lithtech {3}
** tutorials
*** lithtech_primer.shtml
* index.shtml
** tools.shtml
** tutorials.shtml
* manual (how to review a model?) {i} it may go X
* nolf {3}
* quake {2}
** FAQ.shtml
** index.shtml
** tools.shtml
** tutorials.shtml
* quake2 {1}
** tools
*** Prefabs
**** Alx_Prefabs-info.shtml
**** Hunter_Prefabs-info.shtml
** Testbox
*** testbox.shtml
* tutorials
** NGLV
** NST_Tut01
** Custom VWEP.shtml
** NST_Retro<code><nowiki></nowiki></code>Map.shtml
** Weapon Skin Linking.shtml
* FAQ.shtml
** index.shtml
** md2text.txt
** q2frameslist.shtml
** tools.shtml
** tutorials.shtml
* quake3 {1}
** Model_Doc
*** Model_manual_ps.htm
* Shader_Doc
** Q3<code><nowiki></nowiki></code>Ashader_manual.htm
* tools
** tutorials (lots of files below these, ugh)
*** josh
*** max-to-q3
*** MAX-to-q3data
*** Skin-shader
*** Sound<code><nowiki></nowiki></code>Pak
*** Steed-Tut
* index.shtml
** md3text.txt
** tools.shtml
** tutorials.shtml
* rune {3}
** tutorials
*** lodsettings
**** runetut-lodsettings.shtml
* index.shtml
* sims {3}
** index.shtml
** tools.shtml
** tutorials.shtml
* ssam {3}
* thps {3} {i}
* tribes {3}
** index.shtml
** tools.shtml
** tutorials.shtml
* unreal {2}
** tools
** tutorials (lots of files in these subdirs)
*** lodsettings
*** mage
*** pix
*** sounds
*** umod
*** umod-backup
*** UTut01.shtml
*** UTut02.shtml
*** UTut03.shtml
*** UTut04.shtml
*** UTut05.shtml
*** UTut06.shtml
*** Utut07.shtml
* index.shtml
** tools.shtml
** tutorials.shtml
** UTtut-mainpage.shtml
** UTtut-part5.shtml
* ut2003 {1}
** tutorials
*** backups (this might just be backup content, not sure, something about Intertwined)
*** ut2mod
*** pushing_tutorial.shtml
* index.shtml
** tools.shtml
** tutorials.shtml
Also what I'd consider resources are:

* Good, Bad and Ugly (skins/gbu/* with eight article directories under it) {2}
* Skin news archives (skins/archived-news/* with 30 pages of news under it) {i} no idea
* Articles (ten article directories below that:) {2}
** animation-tips
** BnW<code><nowiki></nowiki></code>interview
** chiq_interview_012602
** chrisbruce_072002
** Gwot062k2
** max3preview
** q3-model-preview
** Steed-gdc99
** Steed-Interview
** Steed-Interview-2
* Subdermal (six pages and a contest) {2}

= Not Linked To =
* [[AskDev]] (ask a developer column?) X this didnt pan out. a dev house wanted to help just answer questions. But pulled out right as we set it all up.
* docs/gamespace_release.zip X
* misc
** Discreet_QCon2k1 {3} {i} needs review
** e32k4 {3} {i} needs review
** gfx {i} is this just a directory full of original polycount gfx?
** id-model-renders {3}
** pimps {3} {i} needs review
** 12-3action.htm {3} {i} needs review
** gamespy-broadcastkey.txt X
** lead_action_designer.doc X
** micro-forte-syd-jobdoc.shtml X
** stuff.htm {3} {i} needs review
** Unreal_Coach_jobpost_053104.doc X
* modeloftheweek X
* modelpacks {3}
* paintchat {2} conditional that we can get it working again, free/cheap. if not... X
* previews X
** nicknacks X
* reviewlists X
* skindom (woah nelly tons of stuff here) {3}
* cutedoll.shtml (contest?) {3} archive purposes only
* info (actual static model info files, non-db) {2} after database
* reviews (actual static model review files, non-db) {2} after database

OldSiteResourcesGeneralToolsPolyChop

2006-05-31T03:57:04Z

VitoMiliano:

__NOTOC__
attachment:gdmag.pdf
Some Game Developer magazine article.

OldSiteResourcesGeneralToolsInfografica

2006-05-31T03:47:38Z

VitoMiliano:

__NOTOC__
'''REYES Infografica Plugins for MAX 3''' by [http://www.reyes-infografica.com/index.php REYES Infografica]

'''[[CartoonReyes]]''' - A very nice "cartoon-style" rendering plugin to gives your scenes that nice cel shaded look.
[http://www.fileplanet.com/dl/dl.asp?/polycount/tools/discreet/infografica/cartoonreyes/plugin.zip Plugin] (145KB) - The actual plugin files.
[http://www.fileplanet.com/dl/dl.asp?/polycount/tools/discreet/infografica/cartoonreyes/help.zip Help] (402KB) - Help documentation.
[http://www.fileplanet.com/dl/dl.asp?/polycount/tools/discreet/infografica/cartoonreyes/scenes.zip Scenes] (1,004KB) - Sample scenes for reference and tutorials.
[http://www.fileplanet.com/dl/dl.asp?/polycount/tools/discreet/infografica/cartoonreyes/images.zip Images] (1,335KB) - Sample shots of the plugin in action.

'''[[ClothReyes]]''' - This is one of the finest cloth simulation/collision detection systems available.
[http://www.fileplanet.com/dl/dl.asp?/polycount/tools/discreet/infografica/clothreyes/plugin.zip Plugin] (372KB) - The actual plugin files.
[http://www.fileplanet.com/dl/dl.asp?/polycount/tools/discreet/infografica/clothreyes/manual.zip Manual] (9,625KB) - The user manual for the plugin.
[http://www.fileplanet.com/dl/dl.asp?/polycount/tools/discreet/infografica/clothreyes/help.zip Help] (21,491KB) - Help documentation.
[http://www.fileplanet.com/dl/dl.asp?/polycount/tools/discreet/infografica/clothreyes/scenes.zip Scenes] (703KB) - Sample scenes for reference and tutorials.
[http://www.fileplanet.com/dl/dl.asp?/polycount/tools/discreet/infografica/clothreyes/images.zip Images] (30,285KB) - Sample shots of the plugin in action.

'''[[DirtyReyes]]''' - A "wear and tear" plugin that automatically ages or weathers objects in your scene without relying on textures.
[http://www.fileplanet.com/dl/dl.asp?/polycount/tools/discreet/infografica/dirtyreyes/plugin.zip Plugin] (300KB) - The actual plugin files.
[http://www.fileplanet.com/dl/dl.asp?/polycount/tools/discreet/infografica/dirtyreyes/help.zip Help] (21,491KB) - Help documentation.
[http://www.fileplanet.com/dl/dl.asp?/polycount/tools/discreet/infografica/dirtyreyes/scenes.zip Scenes] (1,857KB) - Sample scenes for reference and tutorials.
[http://www.fileplanet.com/dl/dl.asp?/polycount/tools/discreet/infografica/dirtyreyes/images.zip Images] (144KB) - Sample shots of the plugin in action.

'''[[JetaReyes]]''' - This is a fantastic plugin designed to easily duplicate gestures, facial expressions, and speech.
[http://www.fileplanet.com/dl/dl.asp?/polycount/tools/discreet/infografica/jetareyes/plugin.zip Plugin] (188KB) - The actual plugin files.
[http://www.fileplanet.com/dl/dl.asp?/polycount/tools/discreet/infografica/jetareyes/jeta.zip Jeta] (1,040KB) - The stand-alone portion of this plugin.
[http://www.fileplanet.com/dl/dl.asp?/polycount/tools/discreet/infografica/jetareyes/help.zip Help] (404KB) - Help documentation.
[http://www.fileplanet.com/dl/dl.asp?/polycount/tools/discreet/infografica/jetareyes/scenes.zip Scenes] (169KB) - Sample scenes for reference and tutorials.
[http://www.fileplanet.com/dl/dl.asp?/polycount/tools/discreet/infografica/jetareyes/images.zip Images] (2,690KB) - Sample shots of the plugin in action.

'''[[MetaReyes]]''' - A "natural modeling system" that uses meta-objects to define mass.
[http://www.fileplanet.com/dl/dl.asp?/polycount/tools/discreet/infografica/metareyes/plugin.zip Plugin] (387KB) - The actual plugin files.
[http://www.fileplanet.com/dl/dl.asp?/polycount/tools/discreet/infografica/metareyes/manual.zip Manual] (11,474KB) - The user manual for the plugin.
[http://www.fileplanet.com/dl/dl.asp?/polycount/tools/discreet/infografica/metareyes/scenes.zip Scenes] (276KB) - Sample scenes for reference and tutorials.
[http://www.fileplanet.com/dl/dl.asp?/polycount/tools/discreet/infografica/metareyes/images.zip Images] (11,248KB) - Sample shots of the plugin in action.

'''[[SurfReyes]]''' - Based on subdivision surfaces, this plugin allows you to generate complex surfaces of varying curvature from a base mesh.
[http://www.fileplanet.com/dl/dl.asp?/polycount/tools/discreet/infografica/surfreyes/plugin.zip Plugin] (155KB) - The actual plugin files.
[http://www.fileplanet.com/dl/dl.asp?/polycount/tools/discreet/infografica/surfreyes/help.zip Help] (1,019KB) - Help documentation.
[http://www.fileplanet.com/dl/dl.asp?/polycount/tools/discreet/infografica/surfreyes/scenes.zip Scenes] (134KB) - Sample scenes for reference and tutorials.
[http://www.fileplanet.com/dl/dl.asp?/polycount/tools/discreet/infografica/surfreyes/images.zip Images] (265KB) - Sample shots of the plugin in action.

OldSiteResourcesGeneralTools

2006-05-31T03:44:59Z

VitoMiliano:

__NOTOC__
General Tools

[http://www.xdsoft.com/explorer/ 3D Exploration] by [http://www.xdsoft.com/ X Dimension Software]
A 3D viewer for most Windows versions with an Explorer-like interface and Open GL hardware accelerator support. Lets you view all popular 3D and 2D file formats. Click-to-zoom and drag-zoom let you explore 3D objects from any angle and with any light source. The latest update gives you the option to export animation to 3D Studio Max and adds bump, opacity, reflection, refraction, specular, ambient, emission, specular level, and glossiness maps.

[http://tdp.nu/cgi-bin/plugsearch_r4.pl?search=gmax 3DS Importer Script for gmax] by [http://gmax.digitalarenas.com/ Chris Cookson]
A 3D viewer for most Windows versions with an Explorer-like interface and Open GL hardware accelerator support. Lets you view all popular 3D and 2D file formats. Click-to-zoom and drag-zoom let you explore 3D objects from any angle and with any light source. The latest update gives you the option to export animation to 3D Studio Max and adds bump, opacity, reflection, refraction, specular, ambient, emission, specular level, and glossiness maps.

[http://www.lighttek.com/alteros/index.htm Alteros 3D Viewer] by [http://www.lighttek.com/ Lighttek Software]
Alteros 3D is a universal file viewer with a fully customizable interface. The program allows viewing any 3D files, as well as 2D graphical files. It can also view HTML, TXT, and other document formats.

[http://www.planetquake.com/polycount/resources/glossary2/index.shtml An Artist's Real-Time 3D Glossary] by [http://www.planetquake.com/polycount/resources/glossary2/author.html Eric Chadwick]
This is the mother of all resources we could possibly have on polycount. This really lays it all out for you in layman's terms. If you want to get into professional 3D work, you have to be able to throw these terms around. HIGHLY RECOMMENDED

[http://diginux.net/aztec/index.html Aztec] by [mailto:pmartin@users.sourceforge.net Phillip Martin]
A new 3d modeler/editor by [mailto:phillip_martin@optusnet.com.au Phillip Martin], author of the original Q2 modeler. This one is still in alpha stages, but it should prove to be a large tool in the game editing scene if the programmer's past record is any indication. UPDATE: Mr. Martin has made Aztec open source. You can [http://sourceforge.net/projects/aztec/ download the sourcecode from here].

[http://www.blender.nl/ Blender] by NaN
There is currently some question as to the applicability of this free product, but that's only because no one's used it much yet. Blender is a free and fully functional 3D modeling/rendering/animation package for Unix/Windows/BeOS systems. Blender is distributed without sources, it is exclusively developed and maintained by the Dutch company NaN

[http://www.splutterfish.com/sf/ Brazil Rendering System] by [[SplutterFish]]
Want your rendered images to be as realistic as possible? Say hello to Brazil, a very nice rederer that has gotten some attention lately due to its radiosity and global illumination capabilities. It's touted as a new advanced rendering system developed within a production environment to meet the demanding, exacting, and varied requirements of professional artists. In its alpha stage it's a free download.

[http://dl.fileplanet.com/dl/dl.asp?polycount/tools/discreet/removeuvs_v3.zip Calpha 1.0 for Max3.0] by [mailto:watjep@mindspring.com Peter Watje ]This is a simple modifier that strips unused texture vertices from a mesh or patch. It is a temporary fix to a bug in UVW Unwrap that causes file sizes to explode. You need to place this at the top of the stack and then collapse to remove the unused texture vertices. This can dramatically lower the size of your MAX file if you have been doing a lot of texture UV work on it.

[http://www.planetquake.com/gg/tutorial/toon/index.html Cartoon Outline Generator] by [mailto:sgalbrai@krl.org Seth Galbraith]This utility adds extra polygons to a model to make it look like it has a cartoon outline. It currently only works on [[MilkShape]] 3D models exported in [[MilkShape]] 3D ASCII format. These models can be imported into [[MilkShape]] 3D and then exported as models for many popular 3D games.

[http://www.insanesoftware.de/ CharacterFX] by [http://www.insanesoftware.de/index.htm Insane Software]
CharacterFX is a shareware character animation package, created for game developers. It allows you to animate meshes with a skeleton and keyframes. Its integrated scripting language makes it extremely easy to extend. It's not a modeler, so you will need a modelling package to make the meshes with.

[http://dl.fileplanet.com/dl/dl.asp?q2pmp/tools/Chilliskinner.zip ChilliSkinner] by [mailto:Chilli@chilliweb.co.uk Chilli]
A skinmapping plugin for 3DStudio MAX. [[ChilliSkinner]] attempts to automatically go through the steps involved in preparing a 3D model for skinning. It breaks the object down into polys that can be flat planar mapped. It aligns them all into a single plane so they are all facing the same way. It arranges all these pieces so that they don't overlap and forms them into the shape of a square... giving you a nice neat group of flat objects to apply your planar map too. Not only all this but it also has quick step buttons that perform all the in-between steps for you too i.e. cloning and hiding the model, attaching pieces, applying the planar map, compound morphing the object back together and welding vertices. There are a couple of tutorials for this valuable tool available at [http://www.chilliweb.co.uk/ChilliSkinner/ the ChilliSkinner site].

[http://amber.rc.arizona.edu/lw/decimate2.html Decimate]
Lightwave version of the Polychop plug-in. See below for full details and [http://www.cs.ualberta.ca/~melax/polychop/ the main site].

[http://dl.fileplanet.com/dl/dl.asp?q2pmp/tools/DejaView.zip DejaView] by [http://www.discreet.com/ Discreet]
An open source OpenGL model viewer that displays skeletal animation. It consists of two 3D Studio MAX R3.1 poly-based exporters (including physique and skin bone-to-mesh bindings and support for Biped), along with a stand-alone real-time OpenGL viewer that reads and displays the 3D data in a variety of ways. Fully skinned and animated characters can be exported to this file format and then read and displayed for pre-game preview. The source code is available [http://support.discreet.com/~maxopensource from this link].

[http://www.geocities.com/squirreldome/cyberop.htm Project Dogwaffle] by [mailto:dan_ritchie@hotmail.com Daniel Ritchie]
Project dogwaffle is a free paint program, though the author contends that it is not an image editor. If you like creating original pretty pictures, then dogwaffle should do well. If you want to scan images and put them on your web page, (not that there's anything wrong with that) then dogwaffle may not be the best tool.

[http://www.fileplanet.com/dl/dl.asp?/planetquake/polycount/Tools/frameranger.zip FrameRanger] by [http://www.liquidanimation.com Andrew "Betlog" Eglington], originally by [http://mondomed.com/ Mondo Media]
A nice MAX script that allows you to select different active ranges in an single MAX file. An application of this is to only work and view a select number of frames in a long animation, say like the Q2 model format. The zip comes with pre-made ranges for the Q2 frame list. Check Mondo's site for a ton of nice helper tools like this. UPDATE: This tool has been updated and now works with Max 2, 3 and 4. It also now has some new features along with some bug fixes.

[http://www.chez.com/stephdesign/free_frame.htm Free 3D Studio Max Plugins] compiled list by [%20mailto:stephdesign@caramail.com StephDesign]
Here is a not full but very complete list of Plug-ins free or shareware for 3D Studio MAX 3.0, with for the first time the date and the number of the last version available. Some plug-ins are now not indispensable because same functionality are already in MAX release 3.0. I put nevertheless in the list for the backward compatibility with old project. There is for a good part, a copy of each plug-ins in this site, or by default a link, so you can download all of them! .

[http://www.planetquake.com/polycount/resources/general/tools/infografica.shtml Free "Reyes" Plugins for MAX 3] by [http://www.reyes-infografica.com/index.php REYES Infografica]
Most folks that use MAX will be pretty interested in this next bit. It seems that Reyes Infografica is giving away free copies of their uber popular MAX3 plugins, and they have graciously allowed us to mirror those plugins here on polycount. Here's the clip explaining what they are doing and why on their site:

''As pioneers in the field of innovative software we are as crazy about 3D as you are, and because we are excited by and indebted to your creative input, we would like to give you the opportunity to help us discover what makes you tick and how we can improve our products to suit your needs in the future. That's why we are offering you our award winning plug-ins for 3D Studio Max 3 totally free of charge so that you can take your creativity one step further, while we develop versions for 3D Studio Max 4 to offer you. I am of course talking about [[ClothReyes]], [[MetaReyes]], [[DirtyReyes]], [[CartoonReyes]], [[SurfReyes]] and [[JetaReyes]].''

This is some serious stuff here. This is top level quality plugins, not slackerware by any means. Ignore this one at your own cost. Highly recommended!

[http://www.ruff-stuff.com/GDC2000/DeveloperConference.html Game Editing Scripts] by [http://www.ruff-stuff.com Fred Ruff]
A bunch of info on some MAX scripts demoed at GDC. Mostly focused on streamlining work flow, he also offers some cool UI scripts as well and other gee whiz type things. Plus you can download them yourself and pick them apart and build your own. Highly recommended!

[http://www.gimp.org/ The Gimp] by [mailto:!spam-pmattis@gimp.org Peter Mattis] and [mailto:!spam-spencer@xcf.berkeley.edu Spencer Kimball]
The GIMP is the "GNU Image Manipulation Program." It is a freely distributed piece of software suitable for such tasks as photo retouching, image composition and image authoring. Very handy if you're on a *NIX operating system. There are ports for you Windows people too.

[http://www.fileplanet.com/dl/dl.asp?/planetquake/polycount/Tools/discreet/gmaxinst.exe gmax] by [http://www.discreet.com/products/gmax/ Discreet]
YOU HAVE GOT TO GET THIS TOOL!! This is a toned down version of 3d Studio Max, but for free! Right now you can just make Quake 3 models and levels for it, but given some time, it's going to be quite the versatile little workhorse. Especially with more and more [http://tdp.nu/cgi-bin/plugsearch_r4.pl?search=gmax scripts] being produced. Grab the files from discreet, or from our own local mirrors. You have to get the Q3 plugins from them though. We can't do the user agreement for them :) Highly recommended!

* [http://www.fileplanet.com/dl/dl.asp?/planetquake/polycount/Tools/discreet/gmaxinst.exe gmax main install]
* [http://www.fileplanet.com/dl/dl.asp?/planetquake/polycount/Tools/discreet/gmax_tutorials.exe gmax tutorials]
* [http://www.fileplanet.com/dl/dl.asp?/planetquake/polycount/Tools/discreet/gmax_help.exe gmax help files]
[http://user.fundy.net/morris/redirect.html?photoshop1.shtml Keyboard Shortcut Keys for Photoshop] by [http://user.fundy.net/morris Trevor Morris]
A set of EVERY shortcut key available for [[PhotoShop]]. You'll find lists of all the shortcut keys for PS 5.0, 5.x and 6.0. Laminate these things and keep them in your wallet to impress the members of the opposite sex. If you don't have the latest version, [http://showcase.netins.net/web/wolf359/ps4sc1.htm a set for PhotoShop 4 is available here]. Highly recommended!

[http://members.bellatlantic.net/~mbristol/ Lightwave Tools and Exporters] by [mailto:drtrogg@hotmail.com Michael "Ansai" Bristol]
For those of you of the Lightwave persuasion, this is definitely a place you'll want to stop by if you've a mind to create any custom models for games. This is really the only set of Lightwave plugins out there for creating custom game art. The exporters even configure some of the text files for you. Current 'active' formats are Quake2 MD2, Quake3 MD3, and Unreal Tournament (with ActorX support). Highly recommended!

[http://www.linuxartist.org/ Linux Artist.org]
This site is absolutely full of 2D and 3D tools for Linux. Impressive amount of stuff here. Good description of the tools. Nice documentation. If you are a Linux user, give this one a look. You never know what you might find.

[http://www.geocities.com/lithunwrap/ LithUnwrap] by [bbolthou@bigfoot.com Brad Bolthouse]
[[LithUnwrap]] is a free Windows tool for mapping and editing the UV coordinates of of low poly models. It can unwrap a 3D model and export the mapping to a bitmap texture which can then be painted. Also on the official [[LithUnwrap]] site are also tutorials explaining how to use it. Works with most popular game model formats.

[http://www.mondomed.com/Mlabs/Mlabs_01.html MAX Plugins and Scripts], by [http://www.mondomed.com Mondo Labs]
Mondo Media has set themselves up a really nice set of plugins and scripts for 3DS Max. Very useful stuff in here. Check them out.

[http://www.aliaswavefront.com/en/Community/Special/ple_announce/index.html Maya Personal Learning Edition], by [http://www.aliaswavefront.com/en/Home/homepage.jhtml Alias|Wavefront]
It looks as though Alias|[[WaveFront]] is releasing a Personal Learning Edition of Maya. This will be pretty much the whole deal with NURBS modeling, animation, inverse kinematics, Maya Artisan, Maya Paint Effects, particles, dynamics and Maya’s advanced rendering capabilities. The only downsides are that it will smack a watermark on any images created with it and use a non-standard file format as well as being incompatible with any industry-standard plug-ins. The learning edition will be available in February, and you can sign up at the link above.

[http://www.swissquake.ch/chumbalum-soft/ms3d1x/index.html Milkshape], by [http://www.swissquake.ch/chumbalum-soft/ chUmbaLum sOft]
A nice free modeling and animation utility, capable of importing and exporting various (game) file formats. Currently there is support for Half-Life models, Quake2 models, Unreal/UT models and Genesis 3D models. Support for any other game file format are planned, but need some extra researches. [[MilkShape]] 3D is shareware.

[http://www.kickengine.co.uk/downloads.html Model Manager] by [http://www.kickengine.co.uk/index2.html Kick Engine]
This is a model viewer that can be used as a stand alone model viewer or in association with other Kick Engine tools. This model viewer supports a wide range of formats. Some of the more important ones are .3ds and .MD3. As with all good things, this has its downfall for the everyday user. This program requires a pretty beefy machine to run it to it's full capacity. These are the specs quoted on the Kick Engine page: "P2 400, 64MB RAM, 32MB GRAPHICS CARD FOR 32 BIT COLOR (16 MEG FOR 16-BIT COLOR OUTPUT), SOUND CARD and 256MB VIRTUAL MEMORY" If you have the machine to run it, this looks pretty dern handy.

[http://openfx.org/download/index.php OpenFX] by [http://openfx.org/news/index.php The OpenFX Team]
An open source 3D modeling program. It currently runs under any Win32 environment with future plans for FreeBSD and Linux platforms. They already tested it under WINE for Linux and had a pretty good run of it with the current release of WINE. Powerful feature-set includes a full renderer and raytrace engine, NURBS support, kinematics-based animation, morphing, and an extensive plugin API, and it is all open source. You can pick a copy up directly right here but drop by the site first to get the whole low-down.

[http://pakrat.fragland.net/ PakRat] by [mailto:naughton@mac.com Tom Naughton]
[[PakRat]] is a program that displays MDL, MD2, and MD3 models and soon Quake 3 maps. You can drag textures from any paint program and drop them on any mesh (great for skinning). It also sports drag and drop MD3 assembly. It's free, open source, under active development, and Mac only.

[http://asp.planetquake.com/dl/dl.asp?q2pmp/ascmaker.zip Phillip Martin's 3D Studio Max 1.x ASE exporter plug-in]/
[http://asp.planetquake.com/dl/dl.asp?q2pmp/ascmaker2.zip Phillip Martin's 3D Studio Max 2.x ASE exporter plug-in]
This allows you to export pieces of your animations from 3D Studio for conversion into the standard model format. For experienced 3D Studio Max users only. The version 2 is bundled with a new how-to text file. Plus you'll find a tutorial on the tutorials page.

[http://www.photomodeler.com/Lite/ Photomodeler Lite] by [http://www.eossystems.com/ Eos Systems]
With [[PhotoModeler]] Lite, you can create 3D models from photos complete with points, lines, surfaces, and phototextures mapped on right from your photos! Since this is freeware, that means it is fully functional and F-R-E-E. Words we like at any time.

[http://asp.planetquake.com/dl/dl.asp?q2pmp/PhysCollapse.dlu Physique Collapser plugin for MAX 2.5 / CS2.1] by [mailto:npherno@sunstorm.net NPherno]
The man of many coding talents has whipped up another item for the folks who are using the dynamic duo of 3DStudio MAX 2.5 and Character Studio 2.1. This plugin, a Physique Collapser, allows you to detach the biped and physique modifiers from a mesh and still retain all the animations to a mesh. Sounds only mildly good on the surface, but consider if you're working on a Half-Life model and you need to adjust a few bits because it's not deforming correctly, or you want to add a new appendage or basically any mesh adjustments. Well with this you can easily do them without the nastiness that can happen when trying to go back into the modifier stack to deal with these objects. Sounds better now, huh? :)

Note: It will not currently work on any bones system other than the biped. If you've added any MAX or 3rd party bones, you'll have to work around them for the moment. A future version is planned that will work on those as well. Also if you want to reattach the biped to the mesh after detaching it, it's best to save the file and reload it after detaching it. Thanks to Space Dog for that tip. Other than that its pretty straight forward, if you have any comments or questions, stick them in the message board and we'll talk about it there. This was made from uncompiled code that was included with the CS2.1 update. Why it was never complied, we're unsure, but it does work well.

[http://www.cs.ualberta.ca/~melax/polychop/plugin Polychop] by Stan Melax
Probably the best polygon reduction tool out there and it's free. Comes in MAX 2.5 and 3 flavors as well as [http://amber.rc.arizona.edu/lw/decimate2.html Lightwave]. [http://www.cs.ualberta.ca/~melax/polychop/ The main site] has several nice items related to polygon reduction in general as well. Here's [tools/polychop/gdmag.pdf a nice article] in pdf format from Game Developer Magazine from November 1998 that discusses the tool.

[http://www.fileplanet.com/dl/dl.asp?/planetquake/polycount/polytier/polytier-maps.zip Polytier Maps] by [mailto:wrath@polycount.com Wrath], [mailto:rogue13@polycount.com rogue13], and [mailto:harlequin@planetquake.com HarlequiN]
Two Max scene files and a Quake 3 map upon which you can take beautiful screenshots for pimping your creations. Also available separately.

* [http://www.fileplanet.com/dl/dl.asp?/planetquake/polycount/polytier/polycount_tier.zip Polycount Tier MAX File] by [mailto:wrath@polycount.com Wrath]
* [http://www.fileplanet.com/dl/dl.asp?/planetquake/polycount/polytier/polycount-stage.zip Polycount Tier MAX File] by [mailto:rogue13@polycount.com rogue13]
* [http://www.fileplanet.com/dl/dl.asp?/planetquake/polycount/polytier/Q3map_hqn-polytier.zip Polycount Tier Quake 3 Map] by [mailto:harlequin@planetquake.com HarlequiN]
[http://www.planetquake.com/polycount/cottages/toolbox/files/Polyvis_10.exe Polyvis] by [http://www.planetquake.com/polycount/cottages/toolbox/ Elmek]
Polyvis is a maxscript utility intended to help artist determine what polygons on certain objects are visible to a particular camera during animation of that camera/object. The utility is especially intended to determine what polygons are visable on weapons in FPS games. This [http://dynamic.gamespy.com/~polycount/ubb/Forum1/HTML/004248.html?000-200108 message board thread] gives a more complete description.

[http://asp.planetquake.com/dl/dl.asp?q2pmp/q2mdlr9b.zip Q2 Modeler v.9b] by [mailto:phillip_martin@optusnet.com.au Philip Martin]
[http://www.eldermage.com/dl/q2mdl911.zip Updated to v.911b] by [mailto:jaimi@eldermage.com Jaimi McEntire]
A free modeler to make your models with. Many of the models on this site were modeled using this tool. This program is an invaluable tool to the modelers of the community, both the beginner who can use this tool alone to create their models and the advanced who can bring the models from other programs to here for compiling and skin generation [I personally couldn't do reviews or my own models with out it.] Note: Version .9b was thought to be the final version of the tool. The original author has stopped development on it, but another brave soul, [mailto:jaimi@eldermage.com Jaimi McEntire], has picked up the torch, and will lead it once again to glory. Jaimi has also updated it to [http://www.eldermage.com/dl/q2mdl911.zip version .911b]. Also, here's the [http://asp.planetquake.com/dl/dl.asp?q2pmp/MDL.HLP Help file for latest version] (place in the directory with the rest and it should work fine).

[http://www.planetquake.com/polycount/resources/quake2/tools/Prefabs/Alx_Prefabs-info.shtml Prefabs] by [mailto:BigRocket@juno.com Big Rocket]
A series of prefab primitive objects that you can use to help start a model. Very useful in conjunction with model editing programs such as Quake 2 Modeler that doesn't offer primitive creation built in.

[http://www.planetquake.com/polycount/resources/quake2/tools/Prefabs/Hunter_Prefabs-info.shtml More Prefabs] by [mailto:Hunter@polycount.com Hunter]
Yet another series of prefab primitive objects. Basically a larger selection of primitive shapes at your disposal, in creating your own PPMs for Quake 2, 3 etc.. (Comes in .md2 and .AQM formats)

[http://www.planetquake.com/qview/ QView] by [mailto:lonerunner@planetquake.com LoneRunner]
QView is a small easy and free viewer for anybody who like to view models from games based on any Quake engine. A great list of features, and available source code. Definitely a good one to check out. Word them up, yo.

Reference Image Archives
Many modelers and skinners rely on reference images to help them model. Whether your main interest is accuracy or inspiration, these are invaluable sources to which you may refer while modeling or skinning.

* [http://www.planetquake.com/shattered/shine/images/ref/index.htm shine's Reference Image Archive]
* [http://www.planetquake.com/polycount/cottages/rorshach/reference.htm Rorshach's PhotoReference Section]
* [http://dynamic.gamespy.com/~polycount/ubb/Forum1/HTML/004052.html Ongoing Reference Image Thread]
[http://www.scriptspot.com/ ScriptSpot]
THE place to go for all your Max scripting needs. HIGHLY RECOMMENDED

[http://grad.qeradiant.com/skined/ SkinED]
A free skinning tool. Not bad for what it is. A visit to the site reveals that [[SkinEd]] will get one final update and that's the end. However a new tool is under development by the name of Grad. It sounds like it will be a skinning and modeling tool for the Quake2/3 engines.

[http://www.futurenet.com/pcplus/article.asp?FRM=1&id=3028 TrueSpace 1.0 - Freeware]
Seeing as how [[TrueSpace]] is currently at version 4.0, and you can no longer buy 1.0, this is probably a legal copy. If anyone finds out otherwise, please let us know.

[http://www.turbosquid.com/Website/HTML/download.cfm Turbo Squid] by [http://www.turbosquid.com/ Turbo Squid]
Okay, now this is just cool. Turbo Squid is a free, downloadable software used to buy and sell digital assets. It's also a production tool to help digital artists more rapidly find, preview and acquire essential content. In addition, it's a clearinghouse where digital artists can make money selling their content. Not only that, but it's a growing library with over 70,000 assets available for purchase or free. Finally, it's an application that can run as a standalone or inside your favorite 2D and 3D programs. Not bad, eh?

[http://www.cuneytozdas.com/software/max/texporter/ Texporter] by [hmailto:cuneyt@cuneytozdas.com Cuney Tozdas]
If you are a modeler using MAX, and you don't know about this free plugin, consider yourself enlightened. This is one of those 'must-haves'. Texporter converts mapping coordinates of a mesh object to a bitmap. It generates a bitmap on which you can see topology of the mesh in 2D. This can be thought as the unfolded mesh. This “unfolded” map then can be used as a template to paint texture (or bump, opacity, etc.) maps on your favorite painting program. Now with Max 4 support!

[http://http://asp.planetquake.com/dl/dl.asp?q2pmp/Mappingtools.zip UVW Unwrap+ Modifier for 3D Studio Max 2.x] by [mailto:Speuger@home.com Speuger] and [mailto:Gwot@planetquake.com Gwot]
A extension to the skin mapping tools that come standard with MAX. Adds a nice set of tools that those familiar with more sophisticated skin tools like NST, will appreciate. [tutorials/UVWunwrap/UVWunwrap.shtml A small tutorial can be found here].

[http://www.viewpoint.com Viewpoint] (formerly [[MetaStream]])
An EXTREMELY handy little tool that lets you export your creations into a web-friendly format for pimping wherever you've a mind to. It's also necessary for seeing previews of works from some of our more prolific modelers on the [http://dynamic.gamespy.com/~polycount/ubb/Ultimate.cgi Message Boards] (hint: check the Pimping and Previews forum). And here's a nice little kick... Hobbyists get free broadcast keys! Consider this something you need, if you make models and want to show them off. Exporters from various software packages can be found [http://developer.viewpoint.com/ here].

[http://www.3dvirtualight.com/ VirtuaLight Global Illumination Renderer]
This is a stand alone jobbie that any package should be able to use. Also as long as you aren't using it for profit its free.

[http://www.toolsinmotion.com/plugins.html Vroom for Maya] by [http://www.toolsinmotion.com TestaRossa]
This is a library that includes plug-ins to read and write skeletal animation in the Acclaim ASF/AMC, Biovision BVH, and Motion Analysis HTR mocap file formats. In addition, it can import the motion of a mocap skeleton into a Maya skeleton regardless of the reference pose and skeletal structure. A free evaluation version is available.

[http://wadfather.game-edit.com/ The Wadfather]
A huge free texture archive, including environment maps, textures, sprites and assorted other neat stuff that you can use. I recommend you check it out.

[http://asp.planetquake.com/dl/dl.asp?q2pmp/zascout.ms Zascout] by [mailto:zebayan@null.net Zayaban]
An .ASC exporter for MAX 3 and 2.5. Exports files in ASC format which is generic model format. Intended for use with Q2 modeler.

PolycountOldTOC

2006-05-31T03:30:47Z

VitoMiliano:

__NOTOC__
This was thrilling to compile. Please keep things in the list format. Dynamic pages that will be difficult to redirect properly are in italics.

= General Links =
* Poll (poll/poll.shtml) X
* ''News archives'' (news/newsarchives.asp)
* ''News search'' (news/newsarchives.asp?function=search&advanced=1)
* <s>Contact (contacts/index.shtml) {1} </s> [[OldSiteContact]]
* Polycount for PalmOS (news/pqa.zip) X
* Links (links/index.shtml) {2}
* <s>Credits (credits/index.shtml) {1} this should be merged with the contact page</s> [[OldSiteCredits]]
= Download Database =
* ''UT2004 Models, UT2004 Vehicles, UT2003 Models, Quake 3 Models, UT Models, JKA Models, JK2 Models, GTA3 Models, Serious Sam Models, Quake 2 Models, Q3 Map Models, TA Team Models, TA Head Models, Elite Force Models, Half-Life Models, Heretic2 Models, [[CounterStrike]] Models, The Sims Models, Kingpin Models'' (downloads/ and downloads/index.asp?game=##&sort=date&order=DESC) {2}
= Other Models and Skins =
* Q3 Weapon Models (q3weapons/q3weapons-index.shtml) {3}
* HL Weapon Models (hlweapons/hlweapons-index.shtml) {3}
* UT2003 Accessories (dynamic.gamespy.com/~polycount/skins/ut2003skin-index.shtml wtf?) {3}
* Quake 2 Accessories (skins/q2skin-index.shtml) {3}
* Quake 3 Accessories (skins/q3skin-index.shtml) {3}
* Unreal T Accessories (skins/utskin-index.shtml) {3}
* Half-Life Accessories (skins/hlskin-index.shtml) {3}
* Rune Accessories (skins/runeskin-index.shtml) {3}
* Sims Accessories (skins/simskin-index.shtml) {3}
* Accessory Top-Picks (skins/top-picks/top-picks.shtml) {3} potentially X
* Top-Packs (skins/top-picks/top-packs/top-packs.shtml {3} potentially X
= Resources =
* <s>Resources (resources/index.shtml) {1} we should be able to get alot of the heavy lifting here from the community</s> [[OldSiteResources]]

Under Resources, there are these directories and significant files. Directories without any sub-content just have an index.shtml file in them listing resources elsewhere on the net. Most directories also have lots of other directories with supporting files, like images and stuff, which aren't listed for brevity.

* avp2 {3}
** index.shtml
** tutorials
*** talonengine
**** talonenginetut.shtml
* bandw {3} {i} wtf is this? Black and White
* chat-rooms {2}
** chat-index.shtml
** 2design X
*** 2design.shtml
* model_design
** model_design.shtml
* modjobs X
** modjobs.shtml
* drakan {3}
** index.shtml
** gfx
*** JSheffield.zip
* eliteforce {3}
** index.shtml
** tutorials.shtml
** tutorials
*** q3-ef
**** Q3AEF.shtml
* <s>FAQ-genera {1} probably needs reviewl</s>
** <s>faq-general-index.shtml</s> [[OldSiteResourcesFaqGeneral]]
* <s>general {1} </s> [[OldSiteResourcesGeneral]]
** misc {i} sunstorm?
*** sunstorm.shtml
* tools {1}
** infografica.shtml
** polychop
*** gdmag.pdf
* tutorials {2}
** ALPHAWolf_Tut01
*** Low<code><nowiki></nowiki></code>Poly<code><nowiki></nowiki></code>Characters.shtml
* cswingstut
** cswingstut.shtml
* Hitman<code><nowiki></nowiki></code>Daz_Tut01
** Digital<code><nowiki></nowiki></code>Painting.shtml
* Model-unwrap
** model-unwrap.shtml
** model-unwrap-pic1.shtml
** model-unwrap-pic2.shtml
** model-unwrap-pic3.shtml
** model-unwrap-pic4.shtml
** model-unwrap-pic5.shtml
* NURBS-mapping
** Nurbs-mapping.shtml
** tutorial.html
** vrml1.html
** vrml2.html
** vrml3.html
* Shine_Tut03
** Poly<code><nowiki></nowiki></code>Reduce.shtml
* Shine_Tut04
** Making a Head.shtml
* Shine_Tut05
** Setup Bones Part1.shtml
* Surface<code><nowiki></nowiki></code>Tools
** Surface Tools for Low Poly Modeling2.doc
** Surface<code><nowiki></nowiki></code>Tools.shtml
** Surface<code><nowiki></nowiki></code>Tools-mts.shtml
* UVWunwrap
** UVWunwrap.shtml
* ASC_Export_Tut01.shtml
** Shine_Tut01.shtml
** Shine_Tut02.shtml
* video_tutorials {1}
** video-tut-list.shtml
* apps.shtml {1}
** genmisc.shtml {1}
** index.shtml
** lightwave.shtml {1}
** max.shtml {1}
** maya.shtml {1}
** milkshape.shtml {1}
** misc.shtml {1}
** modelanim.shtml {1}
** nst.shtml {3}
** q2m.shtml {3}
** skinning.shtml {1}
** tools.shtml {1}
** tutindex.shtml
** tutorials.shtml
* gfx (looks like game logos for pages maybe) {i} i suspect it is, thats what i think its a dup of that other directory
* glossary (24 pages of definitions plus images) {1}
* glossary2 (only one glossary page, but lots of examples files) {1} can we consolidate these?
* gta3 {3}
* halflife {2}
** index.shtml
** tools.shtml
** tutorials.shtml
** tutorials (directory with 20 pages of modeling tutorials plus example content)
* heretic2 {3}
** index.shtml
** tools.shtml
** tutorials.shtml
* jk2 {3}
** index.shtml
** tutorials
*** Model<code><nowiki></nowiki></code>Tutorial (eight files under here making this up)
*** jk2_model_construction.shtml
* kingpin {3}
** tools
*** framelist.shtml
*** tools.shtml
* index.shtml
** Kingpin-animations.html
* lithtech {3}
** tutorials
*** lithtech_primer.shtml
* index.shtml
** tools.shtml
** tutorials.shtml
* manual (how to review a model?) {i} it may go X
* nolf {3}
* quake {2}
** FAQ.shtml
** index.shtml
** tools.shtml
** tutorials.shtml
* quake2 {1}
** tools
*** Prefabs
**** Alx_Prefabs-info.shtml
**** Hunter_Prefabs-info.shtml
** Testbox
*** testbox.shtml
* tutorials
** NGLV
** NST_Tut01
** Custom VWEP.shtml
** NST_Retro<code><nowiki></nowiki></code>Map.shtml
** Weapon Skin Linking.shtml
* FAQ.shtml
** index.shtml
** md2text.txt
** q2frameslist.shtml
** tools.shtml
** tutorials.shtml
* quake3 {1}
** Model_Doc
*** Model_manual_ps.htm
* Shader_Doc
** Q3<code><nowiki></nowiki></code>Ashader_manual.htm
* tools
** tutorials (lots of files below these, ugh)
*** josh
*** max-to-q3
*** MAX-to-q3data
*** Skin-shader
*** Sound<code><nowiki></nowiki></code>Pak
*** Steed-Tut
* index.shtml
** md3text.txt
** tools.shtml
** tutorials.shtml
* rune {3}
** tutorials
*** lodsettings
**** runetut-lodsettings.shtml
* index.shtml
* sims {3}
** index.shtml
** tools.shtml
** tutorials.shtml
* ssam {3}
* thps {3} {i}
* tribes {3}
** index.shtml
** tools.shtml
** tutorials.shtml
* unreal {2}
** tools
** tutorials (lots of files in these subdirs)
*** lodsettings
*** mage
*** pix
*** sounds
*** umod
*** umod-backup
*** UTut01.shtml
*** UTut02.shtml
*** UTut03.shtml
*** UTut04.shtml
*** UTut05.shtml
*** UTut06.shtml
*** Utut07.shtml
* index.shtml
** tools.shtml
** tutorials.shtml
** UTtut-mainpage.shtml
** UTtut-part5.shtml
* ut2003 {1}
** tutorials
*** backups (this might just be backup content, not sure, something about Intertwined)
*** ut2mod
*** pushing_tutorial.shtml
* index.shtml
** tools.shtml
** tutorials.shtml
Also what I'd consider resources are:

* Good, Bad and Ugly (skins/gbu/* with eight article directories under it) {2}
* Skin news archives (skins/archived-news/* with 30 pages of news under it) {i} no idea
* Articles (ten article directories below that:) {2}
** animation-tips
** BnW<code><nowiki></nowiki></code>interview
** chiq_interview_012602
** chrisbruce_072002
** Gwot062k2
** max3preview
** q3-model-preview
** Steed-gdc99
** Steed-Interview
** Steed-Interview-2
* Subdermal (six pages and a contest) {2}

= Not Linked To =
* [[AskDev]] (ask a developer column?) X this didnt pan out. a dev house wanted to help just answer questions. But pulled out right as we set it all up.
* docs/gamespace_release.zip X
* misc
** Discreet_QCon2k1 {3} {i} needs review
** e32k4 {3} {i} needs review
** gfx {i} is this just a directory full of original polycount gfx?
** id-model-renders {3}
** pimps {3} {i} needs review
** 12-3action.htm {3} {i} needs review
** gamespy-broadcastkey.txt X
** lead_action_designer.doc X
** micro-forte-syd-jobdoc.shtml X
** stuff.htm {3} {i} needs review
** Unreal_Coach_jobpost_053104.doc X
* modeloftheweek X
* modelpacks {3}
* paintchat {2} conditional that we can get it working again, free/cheap. if not... X
* previews X
** nicknacks X
* reviewlists X
* skindom (woah nelly tons of stuff here) {3}
* cutedoll.shtml (contest?) {3} archive purposes only
* info (actual static model info files, non-db) {2} after database
* reviews (actual static model review files, non-db) {2} after database

OldSiteResourcesFaqGeneral

2006-05-31T03:30:29Z

VitoMiliano:

__NOTOC__

'''General FAQ'''

'''Player Models'''

Player models are visual representations of a person or robot playing the game that they are placed in. Generally these are 2 legged, 2 armed, more or less human styled items, although as you can observe from the site, this is by no means a hard rule.

The player model for just about all games will usually consist of a actual 3d model file that you place in a specific directory within your installation of the game to use. Some of the player models for certain games will also require 2d art or 'skins' to go with the model as well to work properly. Additional items might also be available such as custom weapons and sounds. As a rule, anything that the author has included with the model or approved as such, will be in the initial zipped file that you will download. You can also expect to see a read me file in each that should give you some general instructions on where to place the model within your installation properly. If you have any problems with a player model, you should first read this file to make sure you have followed the correct installation procedure as well as any special requirements it may have.

If a game allows for user created player models to be used, it should have a way to select the player models you install on your own. Inspect your user manuals for each game's requirements, but it should be under something along the lines of 'Multiplayer' or 'Player Setup.' If a model does not show up were you expect, please check the individual FAQ's for each game as each has specific do's and dont's that are could trip you up.

'''"What is a Player Model?"'''

As before, a player model is 3d representation of other players in the game, whether they are other live gamers or robots. The model is actually just a visual placeholder for you to shoot at. The actually entity that a player uses in the game is called the 'bounding box.' This is a 3d volume that the game knows exactly what size and where it is at all times. It is also invisible, which is why we need to use the player models to see each other. The bounding box is what the game sees as you run around the levels. It is what collides with the walls and floors to keep you within the world. It is where the the rockets and bullets come from that you spray at the other players. It is also what is used to determine if you got hit in the game and how badly. Now a bunch of refrigerators running around the game is not real exciting, which is why the box is invisible and we use player models.

The player models are located in the game in the exact same spot as the bounding box. As you run around the levels, the game displays the 3d model doing different animations as per what actions you tell it you are doing. If you are running along, the model is displaying the run animations while it is pushing the bounding box around the level. If you jump the box will lift off the ground the prescribed amount and the model will display a jumping motion at the same time. So when you shoot the big bad guy, his own bounding box is there as well and registered that you have just hit him in the upper section of the box and with enough damage to kill him. The game then knows that it has to then display the model in a dieing animation and a proper amount of 'blood and bits', which you see in the game.

Basically the concept of player models is that it is visual trick. The game doesn't care what it is displaying, it merely is keeping track of the bounding box and displaying the proper visuals because it is told to do so. The game would work the exact same way with a bunch of cubes sliding around in the levels, but it wouldn't be as fun as shooting a large scary demon robot from outer space.

'''"I think a model is unfair or cheating. What can I do to stop it?"'''

An immediate concern that comes to peoples minds when the notion of using 3rd party models is that someone could make a model that's unfair, ie: it's to small to see, or below the floor (making it virtually invisible). This problem is easily remedied. If there are any models that you feel are unfair, you have the choice of simply not installing them or deleting them. For instance: You're playing along, racking up the kills, and this someone comes around the corner using this new model you just got. You shoot at his head, but the shot goes right through him and he puts your insides all over the wall. You can simply go in your game directory that holds the model and either delete the directory of that model or rename to something like model_unfair or something. Now anyone using that model will show up as the default character for that game.

'''"Whenever I see a certain model or a group of a lot of user created models, my machine lags out, why?"'''

It is possible that if you join a game and there are so many people using different player models that your computer starts running out of memory and frame rate suffers. If this becomes a problem, you'll have to pick your favorite models and either rename or delete the others.

Some models by themselves require a lot of processing power to to display, because of their polygon count or a variety of reasons. check the review or info page for any model you suspect, if a model is blatantly using a lot of power we will usually call it out in the discussion of the model.

OldSiteResourcesGeneral

2006-05-31T03:26:31Z

VitoMiliano:

__NOTOC__
'''[tools.shtml Tools]'''

The tools you find inside are of a more generic nature. Meaning that they are not focused for one game or engine in particular. Even though they may ''seem'' to favor one over another, they really can apply to almost any project you choose. A nice place to find some gems.

'''[tutindex.shtml Tutorials]'''

Again the same thing here, the tutorials are not necessarily meant for Quake engines or Unreal. you can apply what is being said in these tutorials to many different projects. Sometimes these are the most educational. Broken up into different sections because the page would just be too big if we didn't. You can find some of the same links in different sections.

OldSiteResources

2006-05-31T03:24:13Z

VitoMiliano:

__NOTOC__
Welcome to the polycount modeling and skinning Resources. Within this section of polycount is a virtual wealth of knowledge. See your own creations inside of the games you play. You wanna learn how? Find out here. The first few are for modeling, skinning and computer art in general, while the sections that follow are game specific. Enjoy! And don't forget, when you're done with your creation to send it to us so we can make it available to everyone.

[http://www.planetquake.com/polycount/resources/FAQ-general/faq-general-index.shtml Frequently Asked Questions]
This is the first place you want to start if you're considering making a model or skin for any game.

[http://www.planetquake.com/polycount/resources/glossary2/index.shtml Real-Time 3D Glossary]
If you're gonna walk the walk, you've gotta talk the talk. Or at least so you can understand what other artists are saying.

[http://www.planetquake.com/polycount/resources/general/index.shtml General Resources]
These tools and tutorials really can't be categorized. They apply to digital art, including modeling and skinning, in general. If your question doesn't deal with a specific game, you may want to try here first.

[http://www.planetquake.com/polycount/resources/quake3/index.shtml Quake 3:Arena/Team Arena]
Currently considered the easiest game to create models and skins for, and certainly the engine shows off your creations well.

[http://www.planetquake.com/polycount/resources/unreal/index.shtml Unreal/Unreal Tournament]
One of the most popular games to create models for, the Unreal and Unreal Tournament engines are simply beautiful, and the games fun.

[http://www.planetquake.com/polycount/resources/jk2/index.shtml Jedi Knight 2: Jedi Outcast]
A Star Wars game created using the Quake 3 engine.

[http://www.planetquake.com/polycount/resources/halflife/index.shtml Grand Theft Auto 3]''' http://www.planetquake.com/polycount/images/new.gif '''
That's right, I said GTA3, baby. Rockstar's masterpiece is now open for editing.

[http://www.planetquake.com/polycount/resources/quake2/index.shtml Quake 2]
Quake 2 is where the user-made model scene really took off. It's also where polycount got its roots.

[http://www.planetquake.com/polycount/resources/halflife/index.shtml Half-Life/Counter Strike]
File Half-Life under "oldies but goodies." The engine may be dated, but the game itself still has a high re-play value. The engine presents a very interesting medium.

[http://www.planetquake.com/polycount/resources/eliteforce/index.shtml Star Trek Voyager: Elite Force]
A Star Trek game created using the Quake 3 engine.

[http://www.planetquake.com/polycount/resources/quake/index.shtml Quake]
The first true 3D game. The Quake engine is now open source so if you're really looking for a project this is a great place to start.

[http://www.planetquake.com/polycount/resources/heretic2/index.shtml Heretic 2]
Not much is known about this game other than it's based on the Quake 2 engine.

[http://www.planetquake.com/polycount/resources/sims/index.shtml The Sims]
The game is may be old, but it still sells at full retail price. Its popularity is astonishing... and so is its customizability!

[http://www.planetquake.com/polycount/resources/rune/index.shtml Rune]
A fairly new game that we've seen some good stuff for, but we're waiting to see more.

[http://www.planetquake.com/polycount/resources/nolf/index.shtml No One Lives Forever]
No models and skins here, yet, but there are some tools if you'd like to make them.

[http://www.planetquake.com/polycount/resources/lithtech/index.shtml Lithtech Engine]
A very pretty engine upon which Shogo and Blood 2 were built.

[http://www.planetquake.com/polycount/resources/tribes/index.shtml Tribes/Tribes 2]
The king of the team-based gameplay scene, Tribes and Tribes 2 have some very solid engines.

[http://www.planetquake.com/polycount/resources/drakan/index.shtml Drakan]
It's unknown whether any user-made models or skins exist for this game.

[http://www.planetquake.com/polycount/resources/kingpin/index.shtml Kingpin]
An exciting game based on the Quake 2 engine, it's seeing a few models and skins coming its way.

[http://www.planetquake.com/polycount/resources/ssam/index.shtml Serious Sam]
A visceral shooter with an absolutely gorgeous engine. We're waiting to see what the community can come up with for this one.

[http://www.planetquake.com/polycount/resources/bandw/index.shtml Black and White]
You'd think that anyone that would spend so much time playing god would want to create their own worlds, or people or creatures... Find out how!

[http://www.planetquake.com/polycount/resources/avp2/index.shtml Aliens vs. Predator 2]
It's unknown whether any user-made models or skins exist for this game, but there are currently mod tools.

[http://www.planetquake.com/polycount/resources/thps/index.shtml Tony Hawk Pro Skater 2]
Not much known here, other than the fact that it's customizable.

OldSiteCredits

2006-05-31T03:22:31Z

VitoMiliano:

__NOTOC__

'''The Credits:'''

The who did what and who does what listing plus exciting and interesting email links. I can tell you're excited already. Read on adventurous viewer.

'''The Site Team:'''

[mailto:rogue13@polycount.com rogue13] - Webmaster and owner of the leadership matrix here at the site. He can smooze and talk circles around a fire hydrant. Enjoys the occasional intoxicant. Tries to indulge in modeling and animating when he can, thanks to the site, not often enough. In real life he's an architect, but no, he doesn't do levels.

'''[mailto:wrath@planetquake.com Wrath]''' - Meshsmith supreme. He works by day as a modeler for Sunstorm Interactive, that means he's a gaming professional, and as a modeler for himself by night, that makes him happy. Busy as hell, but happy.

[mailto:hunter@polycount.com Hunter] - General purpose worker on the site. He's teaching himself modeling, animating and skinning and has a love for the community that is unequaled. He loves you and your little model too.

'''[mailto:shadokat@polycount.com Shado Kat]''' - King of the spreadsheet. Mr. Kat was THE man behind converting the massive database of reviews and info pages for the models here in the site. He's even a modeler as well. But to prove that he's human, he allows himself to be side tracked and redirected at a high frequency. He's so giving.

[mailto:phunkyumoto@planetquake.com Rikki Knight] - King of Transformers models. One of the first hosted sites we had and is always involved in the newest trend in the modeling community. He's so trendy. He's our Half-Life model master as well.

[mailto:shine@polycount.com Jon [Shine] Jones] - the 15 year old whiz kid. He's a modeler/animator with some skinning abilities all rolled up into what looks amazingly like a Pokemon. He deals mostly with giving us first impressions on the models as they come in for the info pages for the new models. Don't let his age get in the way, he's got more quality work behind him than a lot of modelers.

'''[mailto:spacedog@planetquake.com SpaceDog]''' - General worker on the site. Desperately trying to learn programming, modeling, skinning, the facts of life all at the same time in school. His head is set to explode at a predetermined capacity so don't stand too close if he's working.

'''[mailto:gotta get him email addy Bearkub]''' - Late night news worker. He works in a server room late on the 3rd shift. He's rather interested in the entire gaming scene and helps out by catching the late shift on general news in the community.

'''The Accessory Skin Grunt Team:'''

[mailto:massivebitch@polycount.com Massive Bitch] - One of the leaders for the site's accessories. You got issues or questions on skins, sounds, or viewable weapons for player models, then he's your bitch. He came from his own site to the q2pmp as Lead Slave for a while. He's been promoted to Lead Skin Slave. He loves the add-ons and even gets in a little modeling action from time to time when he's un-busy.

[mailto:soulreaper@polycount.com Soul Reaper] - Our very own Reaper 'o Souls, helps to bring you the very latest in skins technology. At least, he helps to do that when he's not engrossed with something to do with Sailor Moon. (He's a bit obsessed you know)

[mailto:Kythkin@mac.com Kythkin] - Semi-dedicated out of work Quake3:Arena Skin Grunt. Master of the Q3:A accessory submissions - If you submit it to him it'd better be good ;)

[mailto:schwimmelpuckel@polycount.com SchwimmelPuckel] - Professional graphic artist by day / polycount Q3:A skin Commander by night. This Danish skinner will be using his keen eyes to review our latest skin submissions. Enough of this - grab a berliner and click on something!

[mailto:arco2002@hotmail.com Arco] - Arco is new on the skinning scene and has already made a name for himself on polycount with skinning efforts such as the grim skin for SUW Captain. Q3:A brought him into the skinnin' realm and subsequently to the Accessory Team and we're tickled-pink to have 'im on the team.

[mailto:leachjb@hotmail.com Sniper 1] - Flight control software engineer for fighter jets by day / Skin Grunt by night. He stumbled onto polycount after Quake3:Arena came out & has been a modeling/skinning freak ever since. Real life keeps him busy, but there always room for Q-U-A-K-E.

[mailto:kirin@polycount.com Kirin] - Coming from the year 2030, he's usually a night worker. He's working on Q3 modeling and learning the basics about 3D Studio MAX at the same time. He loves to make skins and also takes care of a beautiful faerie-filled garden in the back yard ... (even though in the year 2047, it's going to be replaced with a large Arena for fragging and the such ... oh well). At least the Quake3 Engine will still be there ... at least that's what he thinks.

[mailto:cygnus@computer.org Cygnus] - As co-director of the [http://www.smackdown.to/ Sactown Smackdown] LAN party, he once downloaded (on a 28.8 modem no less) every model the old Q2PMP had (around 300 at the time) and planted them all on their Quake 2 server. Now that's love. As an electronics engineer in [[RealLife]]™, he has a wicked eye for detail and the curse of being a perfectionist. He likes good, creative, detailed work, so show him what you've got.

[mailto:dukester@popi.net Dukester] - The Grunt is a CNC Punch programmer who lives just outside dallas. He likes to exclusively skin the fem models and someday hopes to learn how to use [[PaintShopPro]] properly. ''"What's a layer?"'' You can find him in the evenings on Mplayer.com drinkin' his Coors Lite ;)

[mailto:rlyss@yahoo.com Redlemons] - Red's a high school student in Australia. He's been playing PC games since he was knee-high to a grasshopper, and intends to keep playing until he dies, or id Software falls apart. Whichever comes first.

[mailto:astrozombie_138@hotmail.com Astro Zombie] - He's a Former G.I. and Gulf War Veteran and is presently a 3D animation student at The Art Institute International of Portland. He's done some work for a local start-up game company on a game that will probably never see the light of day and is currently a "kept man" as his wife supports the both of them while he focuses on school and prepare his demo reel.

[mailto:arya@saphiria.net Arya] - Is the court jester but can be smart at certain times. She has a wild attitude and learns fast. She'll eventually absorb the information and, if you're unlucky, she'll use it against you. Otherwise, she's just as nice as anyone else, and quite a moral person despite her position as a jester. She hangs around various pubs and bbs'es.

[mailto:mask@well.com Ken] - is a graphic designer who works in multimedia and spends his days building corporate CD ROMS and web sites. He's a good technician, a repressed artist and can turn out a mean Q3A skin on occasion.

[mailto:georgiana@gamegirlz.com Geo] - A woman of untold beauty. This is literally true, noone's ever told about it. You might visit her [http://www10.ewebcity.com/geo/ website] to learn more, but steel yourself ! - She'll try to scare you away!

'''Folks Who Helped Make polycount A Reality:'''

'''Mix''' - web designer for Game Spy Industries. Came in and laid out all the initial html and design.

'''Chris Longden''' - techie for Game Spy Industries. Laid the work on the massive database and got the site's tech working properly. The guy is a genius.

'''Stupid Fool''' - innocently asked if there was anything he could do to help and was sucked into hours of tedious copy and pasting.

PolycountOldTOC

2006-05-26T08:47:49Z

VitoMiliano:

__NOTOC__
This was thrilling to compile. Please keep things in the list format. Dynamic pages that will be difficult to redirect properly are in italics.

= General Links =

* Poll (poll/poll.shtml)
* ''News archives'' (news/newsarchives.asp)
* ''News search'' (news/newsarchives.asp?function=search&advanced=1)
* Contact (contacts/index.shtml)
* Polycount for PalmOS (news/pqa.zip)
* Links (links/index.shtml)
* Credits (credits/index.shtml)

= Download Database =

* ''UT2004 Models, UT2004 Vehicles, UT2003 Models, Quake 3 Models, UT Models, JKA Models, JK2 Models, GTA3 Models, Serious Sam Models, Quake 2 Models, Q3 Map Models, TA Team Models, TA Head Models, Elite Force Models, Half-Life Models, Heretic2 Models, CounterStrike Models, The Sims Models, Kingpin Models'' (downloads/ and downloads/index.asp?game=##&sort=date&order=DESC)

= Other Models and Skins =

* Q3 Weapon Models (q3weapons/q3weapons-index.shtml)
* HL Weapon Models (hlweapons/hlweapons-index.shtml)
* UT2003 Accessories (dynamic.gamespy.com/~polycount/skins/ut2003skin-index.shtml wtf?)
* Quake 2 Accessories (skins/q2skin-index.shtml)
* Quake 3 Accessories (skins/q3skin-index.shtml)
* Unreal T Accessories (skins/utskin-index.shtml)
* Half-Life Accessories (skins/hlskin-index.shtml)
* Rune Accessories (skins/runeskin-index.shtml)
* Sims Accessories (skins/simskin-index.shtml)
* Accessory Top-Picks (skins/top-picks/top-picks.shtml)
* Top-Packs (skins/top-picks/top-packs/top-packs.shtml

= Resources =

* Resources (resources/index.shtml)

Under Resources, there are these directories and significant files. Directories without any sub-content just have an index.shtml file in them listing resources elsewhere on the net. Most directories also have lots of other directories with supporting files, like images and stuff, which aren't listed for brevity.

* avp2
** index.shtml
** tutorials
*** talonengine
**** talonenginetut.shtml
* bandw
* chat-rooms
** chat-index.shtml
** 2design
*** 2design.shtml
* model_design
** model_design.shtml
* modjobs
** modjobs.shtml
* drakan
** index.shtml
** gfx
*** JSheffield.zip
* eliteforce
** index.shtml
** tutorials.shtml
** tutorials
*** q3-ef
**** Q3AEF.shtml
* FAQ-general
** faq-general-index.shtml
* general
** misc
*** sunstorm.shtml
* tools
** infografica.shtml
** polychop
*** gdmag.pdf
* tutorials
** ALPHAWolf_Tut01
*** LowPolyCharacters.shtml
* cswingstut
** cswingstut.shtml
* HitmanDaz_Tut01
** DigitalPainting.shtml
* Model-unwrap
** model-unwrap.shtml
** model-unwrap-pic1.shtml
** model-unwrap-pic2.shtml
** model-unwrap-pic3.shtml
** model-unwrap-pic4.shtml
** model-unwrap-pic5.shtml
* NURBS-mapping
** Nurbs-mapping.shtml
** tutorial.html
** vrml1.html
** vrml2.html
** vrml3.html
* Shine_Tut03
** PolyReduce.shtml
* Shine_Tut04
** Making a Head.shtml
* Shine_Tut05
** Setup Bones Part1.shtml
* SurfaceTools
** Surface Tools for Low Poly Modeling2.doc
** SurfaceTools.shtml
** SurfaceTools-mts.shtml
* UVWunwrap
** UVWunwrap.shtml
* ASC_Export_Tut01.shtml
** Shine_Tut01.shtml
** Shine_Tut02.shtml
* video_tutorials
** video-tut-list.shtml
* apps.shtml
** genmisc.shtml
** index.shtml
** lightwave.shtml
** max.shtml
** maya.shtml
** milkshape.shtml
** misc.shtml
** modelanim.shtml
** nst.shtml
** q2m.shtml
** skinning.shtml
** tools.shtml
** tutindex.shtml
** tutorials.shtml
* gfx (looks like game logos for pages maybe)
* glossary (24 pages of definitions plus images)
* glossary2 (only one glossary page, but lots of examples files)
* gta3
* halflife
** index.shtml
** tools.shtml
** tutorials.shtml
** tutorials (directory with 20 pages of modeling tutorials plus example content)
* heretic2
** index.shtml
** tools.shtml
** tutorials.shtml
* jk2
** index.shtml
** tutorials
*** ModelTutorial (eight files under here making this up)
*** jk2_model_construction.shtml
* kingpin
** tools
*** framelist.shtml
*** tools.shtml
* index.shtml
** Kingpin-animations.html
* lithtech
** tutorials
*** lithtech_primer.shtml
* index.shtml
** tools.shtml
** tutorials.shtml
* manual (how to review a model?)
* nolf
* quake
** FAQ.shtml
** index.shtml
** tools.shtml
** tutorials.shtml
* quake2
** tools
*** Prefabs
**** Alx_Prefabs-info.shtml
**** Hunter_Prefabs-info.shtml
** Testbox
*** testbox.shtml
* tutorials
** NGLV
** NST_Tut01
** Custom VWEP.shtml
** NST_RetroMap.shtml
** Weapon Skin Linking.shtml
* FAQ.shtml
** index.shtml
** md2text.txt
** q2frameslist.shtml
** tools.shtml
** tutorials.shtml
* quake3
** Model_Doc
*** Model_manual_ps.htm
* Shader_Doc
** Q3Ashader_manual.htm
* tools
** tutorials (lots of files below these, ugh)
*** josh
*** max-to-q3
*** MAX-to-q3data
*** Skin-shader
*** SoundPak
*** Steed-Tut
* index.shtml
** md3text.txt
** tools.shtml
** tutorials.shtml
* rune
** tutorials
*** lodsettings
**** runetut-lodsettings.shtml
* index.shtml
* sims
** index.shtml
** tools.shtml
** tutorials.shtml
* ssam
* thps
* tribes
** index.shtml
** tools.shtml
** tutorials.shtml
* unreal
** tools
** tutorials (lots of files in these subdirs)
*** lodsettings
*** mage
*** pix
*** sounds
*** umod
*** umod-backup
*** UTut01.shtml
*** UTut02.shtml
*** UTut03.shtml
*** UTut04.shtml
*** UTut05.shtml
*** UTut06.shtml
*** Utut07.shtml
* index.shtml
** tools.shtml
** tutorials.shtml
** UTtut-mainpage.shtml
** UTtut-part5.shtml
* ut2003
** tutorials
*** backups (this might just be backup content, not sure, something about Intertwined)
*** ut2mod
*** pushing_tutorial.shtml
* index.shtml
** tools.shtml
** tutorials.shtml

Also what I'd consider resources are:

* Good, Bad and Ugly (skins/gbu/* with eight article directories under it)
* Skin news archives (skins/archived-news/* with 30 pages of news under it)
* Articles (ten article directories below that:)
** animation-tips
** BnWinterview
** chiq_interview_012602
** chrisbruce_072002
** Gwot062k2
** max3preview
** q3-model-preview
** Steed-gdc99
** Steed-Interview
** Steed-Interview-2
* Subdermal (six pages and a contest)

= Not Linked To =

* AskDev (ask a developer column?)
* docs/gamespace_release.zip
* misc
** Discreet_QCon2k1
** e32k4
** gfx
** id-model-renders
** pimps
** 12-3action.htm
** gamespy-broadcastkey.txt
** lead_action_designer.doc
** micro-forte-syd-jobdoc.shtml
** stuff.htm
** Unreal_Coach_jobpost_053104.doc
* modeloftheweek
* modelpacks
* paintchat
* previews
** nicknacks
* reviewlists
* skindom (woah nelly tons of stuff here)
* cutedoll.shtml (contest?)
* info (actual static model info files, non-db)
* reviews (actual static model review files, non-db)

PolycountOldTOC

2006-05-26T08:47:12Z

VitoMiliano:

__NOTOC__
This was thrilling to compile. Please keep things in the list format. Dynamic pages that will be difficult to redirect properly are in italics.

= General Links =

* Poll (poll/poll.shtml)
* ''News archives'' (news/newsarchives.asp)
* ''News search'' (news/newsarchives.asp?function=search&advanced=1)
* Contact (contacts/index.shtml)
* Polycount for PalmOS (news/pqa.zip)
* Links (links/index.shtml)
* Credits (credits/index.shtml)

= Download Database =

* ''UT2004 Models, UT2004 Vehicles, UT2003 Models, Quake 3 Models, UT Models, JKA Models, JK2 Models, GTA3 Models, Serious Sam Models, Quake 2 Models, Q3 Map Models, TA Team Models, TA Head Models, Elite Force Models, Half-Life Models, Heretic2 Models, CounterStrike Models, The Sims Models, Kingpin Models'' (downloads/ and downloads/index.asp?game=##&sort=date&order=DESC)

= Other Models and Skins =

* Q3 Weapon Models (q3weapons/q3weapons-index.shtml)
* HL Weapon Models (hlweapons/hlweapons-index.shtml)
* UT2003 Accessories (dynamic.gamespy.com/~polycount/skins/ut2003skin-index.shtml wtf?)
* Quake 2 Accessories (skins/q2skin-index.shtml)
* Quake 3 Accessories (skins/q3skin-index.shtml)
* Unreal T Accessories (skins/utskin-index.shtml)
* Half-Life Accessories (skins/hlskin-index.shtml)
* Rune Accessories (skins/runeskin-index.shtml)
* Sims Accessories (skins/simskin-index.shtml)
* Accessory Top-Picks (skins/top-picks/top-picks.shtml)
* Top-Packs (skins/top-picks/top-packs/top-packs.shtml

= Resources =

* Resources (resources/index.shtml)

Under Resources, there are these directories and significant files. Directories without any sub-content just have an index.shtml file in them listing resources elsewhere on the net. Most directories also have lots of other directories with supporting files, like images and stuff, which aren't listed for brevity.

* avp2
** index.shtml
** tutorials
*** talonengine
**** talonenginetut.shtml
* bandw
* chat-rooms
** chat-index.shtml
** 2design
*** 2design.shtml
* model_design
** model_design.shtml
* modjobs
** modjobs.shtml
* drakan
** index.shtml
** gfx
*** JSheffield.zip
* eliteforce
** index.shtml
** tutorials.shtml
** tutorials
*** q3-ef
**** Q3AEF.shtml
* FAQ-general
** faq-general-index.shtml
* general
** misc
*** sunstorm.shtml
* tools
** infografica.shtml
** polychop
*** gdmag.pdf
* tutorials
** ALPHAWolf_Tut01
*** LowPolyCharacters.shtml
* cswingstut
** cswingstut.shtml
* HitmanDaz_Tut01
** DigitalPainting.shtml
* Model-unwrap
** model-unwrap.shtml
** model-unwrap-pic1.shtml
** model-unwrap-pic2.shtml
** model-unwrap-pic3.shtml
** model-unwrap-pic4.shtml
** model-unwrap-pic5.shtml
* NURBS-mapping
** Nurbs-mapping.shtml
** tutorial.html
** vrml1.html
** vrml2.html
** vrml3.html
* Shine_Tut03
** PolyReduce.shtml
* Shine_Tut04
** Making a Head.shtml
* Shine_Tut05
** Setup Bones Part1.shtml
* SurfaceTools
** Surface Tools for Low Poly Modeling2.doc
** SurfaceTools.shtml
** SurfaceTools-mts.shtml
* UVWunwrap
** UVWunwrap.shtml
* ASC_Export_Tut01.shtml
** Shine_Tut01.shtml
** Shine_Tut02.shtml
* video_tutorials
** video-tut-list.shtml
* apps.shtml
** genmisc.shtml
** index.shtml
** lightwave.shtml
** max.shtml
** maya.shtml
** milkshape.shtml
** misc.shtml
** modelanim.shtml
** nst.shtml
** q2m.shtml
** skinning.shtml
** tools.shtml
** tutindex.shtml
** tutorials.shtml
* gfx (looks like game logos for pages maybe)
* glossary (24 pages of definitions plus images)
* glossary2 (only one glossary page, but lots of examples files)
* gta3
* halflife
** index.shtml
** tools.shtml
** tutorials.shtml
** tutorials (directory with 20 pages of modeling tutorials plus example content)
* heretic2
** index.shtml
** tools.shtml
** tutorials.shtml
* jk2
** index.shtml
** tutorials
*** ModelTutorial (eight files under here making this up)
*** jk2_model_construction.shtml
* kingpin
** tools
*** framelist.shtml
*** tools.shtml
* index.shtml
** Kingpin-animations.html
* lithtech
** tutorials
*** lithtech_primer.shtml
* index.shtml
** tools.shtml
** tutorials.shtml
* manual (how to review a model?)
* nolf
* quake
** FAQ.shtml
** index.shtml
** tools.shtml
** tutorials.shtml
* quake2
** tools
*** Prefabs
**** Alx_Prefabs-info.shtml
**** Hunter_Prefabs-info.shtml
** Testbox
*** testbox.shtml
* tutorials
** NGLV
** NST_Tut01
** Custom VWEP.shtml
** NST_RetroMap.shtml
** Weapon Skin Linking.shtml
* FAQ.shtml
** index.shtml
** md2text.txt
** q2frameslist.shtml
** tools.shtml
** tutorials.shtml
* quake3
** Model_Doc
*** Model_manual_ps.htm
* Shader_Doc
** Q3Ashader_manual.htm
* tools
** tutorials (lots of files below these, ugh)
*** josh
*** max-to-q3
*** MAX-to-q3data
*** Skin-shader
*** SoundPak
*** Steed-Tut
* index.shtml
** md3text.txt
** tools.shtml
** tutorials.shtml
* rune
** tutorials
*** lodsettings
**** runetut-lodsettings.shtml
* index.shtml
* sims
** index.shtml
** tools.shtml
** tutorials.shtml
* ssam
* thps
* tribes
** index.shtml
** tools.shtml
** tutorials.shtml
* unreal
** tools
** tutorials (lots of files in these subdirs)
*** lodsettings
*** mage
*** pix
*** sounds
*** umod
*** umod-backup
*** UTut01.shtml
*** UTut02.shtml
*** UTut03.shtml
*** UTut04.shtml
*** UTut05.shtml
*** UTut06.shtml
*** Utut07.shtml
* index.shtml
** tools.shtml
** tutorials.shtml
** UTtut-mainpage.shtml
** UTtut-part5.shtml
* ut2003
** tutorials
*** backups (this might just be backup content, not sure, something about Intertwined)
*** ut2mod
*** pushing_tutorial.shtml
* index.shtml
** tools.shtml
** tutorials.shtml

Also what I'd consider resources are:

* Good, Bad and Ugly (skins/gbu/* with eight article directories under it)
* Skin news archives (skins/archived-news/* with 30 pages of news under it)
* Articles (ten article directories below that:)
** animation-tips
** [[BnWinterview]]
** chiq_interview_012602
** chrisbruce_072002
** Gwot062k2
** max3preview
** q3-model-preview
** Steed-gdc99
** Steed-Interview
** Steed-Interview-2
* Subdermal (six pages and a contest)

= Not Linked To =

* [[AskDev]] (ask a developer column?)
* docs/gamespace_release.zip
* misc
** Discreet_QCon2k1
** e32k4
** gfx
** id-model-renders
** pimps
** 12-3action.htm
** gamespy-broadcastkey.txt
** lead_action_designer.doc
** micro-forte-syd-jobdoc.shtml
** stuff.htm
** Unreal_Coach_jobpost_053104.doc
* modeloftheweek
* modelpacks
* paintchat
* previews
** nicknacks
* reviewlists
* skindom (woah nelly tons of stuff here)
* cutedoll.shtml (contest?)
* info (actual static model info files, non-db)
* reviews (actual static model review files, non-db)

PolycountOldTOC

2006-05-26T08:37:27Z

VitoMiliano:

__NOTOC__
This was thrilling to compile. Please keep things in the list format. Dynamic pages that will be difficult to redirect properly are in italics.

= General Links =

* Poll (poll/poll.shtml)
* ''News archives'' (news/newsarchives.asp)
* ''News search'' (news/newsarchives.asp?function=search&advanced=1)
* Contact (contacts/index.shtml)
* Polycount for PalmOS (news/pqa.zip)
* Links (links/index.shtml)
* Credits (credits/index.shtml)

= Download Database =

* ''UT2004 Models, UT2004 Vehicles, UT2003 Models, Quake 3 Models, UT Models, JKA Models, JK2 Models, GTA3 Models, Serious Sam Models, Quake 2 Models, Q3 Map Models, TA Team Models, TA Head Models, Elite Force Models, Half-Life Models, Heretic2 Models, CounterStrike Models, The Sims Models, Kingpin Models'' (downloads/ and downloads/index.asp?game=##&sort=date&order=DESC)

= Other Models and Skins =

* Q3 Weapon Models (q3weapons/q3weapons-index.shtml)
* HL Weapon Models (hlweapons/hlweapons-index.shtml)
* UT2003 Accessories (dynamic.gamespy.com/~polycount/skins/ut2003skin-index.shtml wtf?)
* Quake 2 Accessories (skins/q2skin-index.shtml)
* Quake 3 Accessories (skins/q3skin-index.shtml)
* Unreal T Accessories (skins/utskin-index.shtml)
* Half-Life Accessories (skins/hlskin-index.shtml)
* Rune Accessories (skins/runeskin-index.shtml)
* Sims Accessories (skins/simskin-index.shtml)
* Accessory Top-Picks (skins/top-picks/top-picks.shtml)
* Top-Packs (skins/top-picks/top-packs/top-packs.shtml

= Resources =

* Resources (resources/index.shtml)

Under Resources, there are these directories and significant files. Directories without any sub-content just have an index.shtml file in them listing resources elsewhere on the net. Most directories also have lots of other directories with supporting files, like images and stuff, which aren't listed for brevity.

* avp2
** index.shtml
** tutorials
*** talonengine
**** talonenginetut.shtml
* bandw
* chat-rooms
** chat-index.shtml
** 2design
*** 2design.shtml
* model_design
** model_design.shtml
* modjobs
** modjobs.shtml
* drakan
** index.shtml
** gfx
*** JSheffield.zip
* eliteforce
** index.shtml
** tutorials.shtml
** tutorials
*** q3-ef
**** Q3AEF.shtml
* FAQ-general
** faq-general-index.shtml
* general
** misc
*** sunstorm.shtml
* tools
** infografica.shtml
** polychop
*** gdmag.pdf
* tutorials
** ALPHAWolf_Tut01
*** LowPolyCharacters.shtml
* cswingstut
** cswingstut.shtml
* HitmanDaz_Tut01
** DigitalPainting.shtml
* Model-unwrap
** model-unwrap.shtml
** model-unwrap-pic1.shtml
** model-unwrap-pic2.shtml
** model-unwrap-pic3.shtml
** model-unwrap-pic4.shtml
** model-unwrap-pic5.shtml
* NURBS-mapping
** Nurbs-mapping.shtml
** tutorial.html
** vrml1.html
** vrml2.html
** vrml3.html
* Shine_Tut03
** PolyReduce.shtml
* Shine_Tut04
** Making a Head.shtml
* Shine_Tut05
** Setup Bones Part1.shtml
* SurfaceTools
** Surface Tools for Low Poly Modeling2.doc
** SurfaceTools.shtml
** SurfaceTools-mts.shtml
* UVWunwrap
** UVWunwrap.shtml
* ASC_Export_Tut01.shtml
** Shine_Tut01.shtml
** Shine_Tut02.shtml
* video_tutorials
** video-tut-list.shtml
* apps.shtml
** genmisc.shtml
** index.shtml
** lightwave.shtml
** max.shtml
** maya.shtml
** milkshape.shtml
** misc.shtml
** modelanim.shtml
** nst.shtml
** q2m.shtml
** skinning.shtml
** tools.shtml
** tutindex.shtml
** tutorials.shtml
* gfx (looks like game logos for pages maybe)
* glossary (24 pages of definitions plus images)
* glossary2 (only one glossary page, but lots of examples files)
* gta3
* halflife
** index.shtml
** tools.shtml
** tutorials.shtml
** tutorials (directory with 20 pages of modeling tutorials plus example content)
* heretic2
** index.shtml
** tools.shtml
** tutorials.shtml
* jk2
** index.shtml
** tutorials
*** ModelTutorial (eight files under here making this up)
*** jk2_model_construction.shtml
* kingpin
** tools
*** framelist.shtml
*** tools.shtml
* index.shtml
** Kingpin-animations.html
* lithtech
** tutorials
*** lithtech_primer.shtml
* index.shtml
** tools.shtml
** tutorials.shtml
* manual (how to review a model?)
* nolf
* quake
** FAQ.shtml
** index.shtml
** tools.shtml
** tutorials.shtml
* quake2
** tools
*** Prefabs
**** Alx_Prefabs-info.shtml
**** Hunter_Prefabs-info.shtml
** Testbox
*** testbox.shtml
* tutorials
** NGLV
** NST_Tut01
** Custom VWEP.shtml
** NST_RetroMap.shtml
** Weapon Skin Linking.shtml
* FAQ.shtml
** index.shtml
** md2text.txt
** q2frameslist.shtml
** tools.shtml
** tutorials.shtml
* quake3
** Model_Doc
*** Model_manual_ps.htm
* Shader_Doc
** Q3Ashader_manual.htm
* tools
** tutorials (lots of files below these, ugh)
*** josh
*** max-to-q3
*** MAX-to-q3data
*** Skin-shader
*** SoundPak
*** Steed-Tut
* index.shtml
** md3text.txt
** tools.shtml
** tutorials.shtml
* rune
** tutorials
*** lodsettings
**** runetut-lodsettings.shtml
* index.shtml
* sims
** index.shtml
** tools.shtml
** tutorials.shtml
* ssam
* thps
* tribes
** index.shtml
** tools.shtml
** tutorials.shtml
* unreal
** tools
** tutorials (lots of files in these subdirs)
*** lodsettings
*** mage
*** pix
*** sounds
*** umod
*** umod-backup
*** UTut01.shtml
*** UTut02.shtml
*** UTut03.shtml
*** UTut04.shtml
*** UTut05.shtml
*** UTut06.shtml
*** Utut07.shtml
* index.shtml
** tools.shtml
** tutorials.shtml
** UTtut-mainpage.shtml
** UTtut-part5.shtml
* ut2003
** tutorials
*** backups (this might just be backup content, not sure, something about Intertwined)
*** ut2mod
*** pushing_tutorial.shtml
* index.shtml
** tools.shtml
** tutorials.shtml

PolycountOldTOC

2006-05-26T08:35:01Z

VitoMiliano:

__NOTOC__
This was thrilling to compile. Please keep things in the list format. Dynamic pages that will be difficult to redirect properly are in italics.

= General Links =

* Poll (poll/poll.shtml)
* ''News archives'' (news/newsarchives.asp)
* ''News search'' (news/newsarchives.asp?function=search&advanced=1)
* Contact (contacts/index.shtml)
* Polycount for PalmOS (news/pqa.zip)
* Links (links/index.shtml)
* Credits (credits/index.shtml)

= Download Database =

* ''UT2004 Models, UT2004 Vehicles, UT2003 Models, Quake 3 Models, UT Models, JKA Models, JK2 Models, GTA3 Models, Serious Sam Models, Quake 2 Models, Q3 Map Models, TA Team Models, TA Head Models, Elite Force Models, Half-Life Models, Heretic2 Models, CounterStrike Models, The Sims Models, Kingpin Models'' (downloads/ and downloads/index.asp?game=##&sort=date&order=DESC)

= Other Models and Skins =

* Q3 Weapon Models (q3weapons/q3weapons-index.shtml)
* HL Weapon Models (hlweapons/hlweapons-index.shtml)
* UT2003 Accessories (dynamic.gamespy.com/~polycount/skins/ut2003skin-index.shtml wtf?)
* Quake 2 Accessories (skins/q2skin-index.shtml)
* Quake 3 Accessories (skins/q3skin-index.shtml)
* Unreal T Accessories (skins/utskin-index.shtml)
* Half-Life Accessories (skins/hlskin-index.shtml)
* Rune Accessories (skins/runeskin-index.shtml)
* Sims Accessories (skins/simskin-index.shtml)
* Accessory Top-Picks (skins/top-picks/top-picks.shtml)
* Top-Packs (skins/top-picks/top-packs/top-packs.shtml

= Resources =

* Resources (resources/index.shtml)

Under Resources, there are these directories and significant files. Directories without any sub-content just have an index.shtml file in them listing resources elsewhere on the net. Most directories also have lots of other directories with supporting files, like images and stuff, which aren't listed for brevity.

* avp2
** index.shtml
** tutorials
*** talonengine
**** talonenginetut.shtml
* bandw
* chat-rooms
** chat-index.shtml
** 2design
*** 2design.shtml
* model_design
** model_design.shtml
* modjobs
** modjobs.shtml
* drakan
** index.shtml
** gfx
*** JSheffield.zip
* eliteforce
** index.shtml
** tutorials.shtml
** tutorials
*** q3-ef
**** Q3AEF.shtml
* FAQ-general
** faq-general-index.shtml
* general
** misc
*** sunstorm.shtml
* tools
** infografica.shtml
** polychop
*** gdmag.pdf
* tutorials
** ALPHAWolf_Tut01
*** [[LowPolyCharacters]].shtml
* cswingstut
** cswingstut.shtml
* HitmanDaz_Tut01
** [[DigitalPainting]].shtml
* Model-unwrap
** model-unwrap.shtml
** model-unwrap-pic1.shtml
** model-unwrap-pic2.shtml
** model-unwrap-pic3.shtml
** model-unwrap-pic4.shtml
** model-unwrap-pic5.shtml
* NURBS-mapping
** Nurbs-mapping.shtml
** tutorial.html
** vrml1.html
** vrml2.html
** vrml3.html
* Shine_Tut03
** [[PolyReduce]].shtml
* Shine_Tut04
** Making a Head.shtml
* Shine_Tut05
** Setup Bones Part1.shtml
* [[SurfaceTools]]
** Surface Tools for Low Poly Modeling2.doc
** [[SurfaceTools]].shtml
** [[SurfaceTools]]-mts.shtml
* UVWunwrap
** UVWunwrap.shtml
* ASC_Export_Tut01.shtml
** Shine_Tut01.shtml
** Shine_Tut02.shtml
* video_tutorials
** video-tut-list.shtml
* apps.shtml
** genmisc.shtml
** index.shtml
** lightwave.shtml
** max.shtml
** maya.shtml
** milkshape.shtml
** misc.shtml
** modelanim.shtml
** nst.shtml
** q2m.shtml
** skinning.shtml
** tools.shtml
** tutindex.shtml
** tutorials.shtml
* gfx (looks like game logos for pages maybe)
* glossary (24 pages of definitions plus images)
* glossary2 (only one glossary page, but lots of examples files)
* gta3
* halflife
** index.shtml
** tools.shtml
** tutorials.shtml
** tutorials (directory with 20 pages of modeling tutorials plus example content)
* heretic2
** index.shtml
** tools.shtml
** tutorials.shtml
* jk2
** index.shtml
** tutorials
*** [[ModelTutorial]] (eight files under here making this up)
*** jk2_model_construction.shtml
* kingpin
** tools
*** framelist.shtml
*** tools.shtml
* index.shtml
** Kingpin-animations.html
* lithtech
** tutorials
*** lithtech_primer.shtml
* index.shtml
** tools.shtml
** tutorials.shtml
* manual (how to review a model?)
* nolf
* quake
** FAQ.shtml
** index.shtml
** tools.shtml
** tutorials.shtml
* quake2
** tools
*** Prefabs
**** Alx_Prefabs-info.shtml
**** Hunter_Prefabs-info.shtml
** Testbox
*** testbox.shtml
* tutorials
** NGLV
** NST_Tut01
** Custom VWEP.shtml
** NST_RetroMap.shtml
** Weapon Skin Linking.shtml
* FAQ.shtml
** index.shtml
** md2text.txt
** q2frameslist.shtml
** tools.shtml
** tutorials.shtml
* quake3
** Model_Doc
*** Model_manual_ps.htm
* Shader_Doc
** Q3Ashader_manual.htm
* tools
** tutorials (lots of files below these, ugh)
*** josh
*** max-to-q3
*** MAX-to-q3data
*** Skin-shader
*** [[SoundPak]]
*** Steed-Tut
* index.shtml
** md3text.txt
** tools.shtml
** tutorials.shtml
* rune
** tutorials
*** lodsettings
**** runetut-lodsettings.shtml
* index.shtml
* sims
** index.shtml
** tools.shtml
** tutorials.shtml
* ssam
* thps
* tribes
** index.shtml
** tools.shtml
** tutorials.shtml
* unreal
** tools
** tutorials (lots of files in these subdirs)
*** lodsettings
*** mage
*** pix
*** sounds
*** umod
*** umod-backup
*** UTut01.shtml
*** UTut02.shtml
*** UTut03.shtml
*** UTut04.shtml
*** UTut05.shtml
*** UTut06.shtml
*** Utut07.shtml
* index.shtml
** tools.shtml
** tutorials.shtml
** UTtut-mainpage.shtml
** UTtut-part5.shtml
* ut2003
** tutorials
*** backups (this might just be backup content, not sure, something about Intertwined)
*** ut2mod
*** pushing_tutorial.shtml
* index.shtml
** tools.shtml
** tutorials.shtml

PolycountOldTOC

2006-05-26T08:05:08Z

VitoMiliano:

__NOTOC__
This was thrilling to compile. Please keep things in the list format. Dynamic pages that will be difficult and/or complicated to redirect properly are in italics.

= From the Front Page =

== General Links ==

* Poll (poll/poll.shtml)
* ''News archives'' (news/newsarchives.asp)
* ''News search'' (news/newsarchives.asp?function=search&advanced=1)
* Contact (contacts/index.shtml)
* Polycount for PalmOS (news/pqa.zip)
* Links (links/index.shtml)
* Credits (credits/index.shtml)

== Download Database ==

* ''UT2004 Models, UT2004 Vehicles, UT2003 Models, Quake 3 Models, UT Models, JKA Models, JK2 Models, GTA3 Models, Serious Sam Models, Quake 2 Models, Q3 Map Models, TA Team Models, TA Head Models, Elite Force Models, Half-Life Models, Heretic2 Models, [[CounterStrike]] Models, The Sims Models, Kingpin Models'' (downloads/ and downloads/index.asp?game=##&sort=date&order=DESC)

== Other Models and Skins ==

* Q3 Weapon Models (q3weapons/q3weapons-index.shtml)
* HL Weapon Models (hlweapons/hlweapons-index.shtml)
* UT2003 Accessories (dynamic.gamespy.com/~polycount/skins/ut2003skin-index.shtml wtf?)
* Quake 2 Accessories (skins/q2skin-index.shtml)
* Quake 3 Accessories (skins/q3skin-index.shtml)
* Unreal T Accessories (skins/utskin-index.shtml)
* Half-Life Accessories (skins/hlskin-index.shtml)
* Rune Accessories (skins/runeskin-index.shtml)
* Sims Accessories (skins/simskin-index.shtml)
* Accessory Top-Picks (skins/top-picks/top-picks.shtml)
* Top-Packs (skins/top-picks/top-packs/top-packs.shtml
* Resources (resources/index.shtml)
* Video Tutorials (resources/general/video_tutorials/video-tut-list.shtml)

› UT2004 Models
› UT2004 Vehicles
› UT2003 Models
› Quake 3 Models
› UT Models
› JKA Models
› JK2 Models
› GTA3 Models
› Serious Sam Models
› Quake 2 Models
› Q3 Map Models
› Q3 Weapon Models
› TA Team Models
› TA Head Models
› Elite Force Models
› Half-Life Models
› HL Weapon Models
› Heretic2 Models
› [[CounterStrike]] Models
› The Sims Models
› Kingpin Models