COUNTER-MAP:  Counter-Strike Mapping
Visit us on IRC at, #countermap
Pic of the Week
Map Spotlight
Weekly Playtests
Random Map Idea
In the News
About Counter-Map
The Crew
Mapping Forums
Important Links



Nemesis' Utilities
Map Packs
Texture Packs
Mapping Utilities
File Database

 Back to Tutorials Page   Other Tutorials by Tommy14 

Info tutorial on texture types
By Tommy14  Last changed Jan 08 2002

Usefulness of content:  69 users  
 out of 5
 3.6 out of 5

Standard HL & Mods textures:

Regularly Tiling Textures (a-z, 0-9), used for regular brushes, and for entity brushes. (Glass textures are regular textures made transparent thru entity properties.) If NOT an entity, then blocks VIS.
problems = if over-stretched may cause compile failure. If the brush involved is clipped, carved, or vertex manipulated it may cause compile error due to perpendicular texture.

Randomly Tiling Textures (-0 to -9), if you use -0name texture of a series, any of these -0 to -9 will be substituted in randomly on that face to tile in - if the player is in software mode. Other video modes (3dfx, open gl) sometimes randomly tile and sometimes not, depending on the player's video card. If NOT an entity, then blocks VIS.
problems = may only work in games played in software mode, textures must match and tile well, and if a texture whose name starts with -1 to -9 is used on the map by mapper then that texture is treated like a regular texture, no random substitution happens.

Regular Animating (+0 to +9), if +0texturename is used on a brush, then the animated series up to +9 will continuously "play" on the brush. Waterfall is an animated texture that should be tied to func water. May or may not block VIS depending on usage.
problems = if a texture whose name starts with +1 to +9 is used on a brush, then no animation, only that texture is shown. Textures must combine well, and fit brush.

Switchable Animating (+A), like regular animating above, except there is one texture of +A. if the brush involved is made a named func wall or other entity, then a trigger can target it and switch from the animation to the "stopped" +A texture.
problems = as regular animation. Also MUST be an entity, therefore it never blocks VIS.

Rad/Light Textures (~), these give off light, but ONLY if listed with correct data in the lights.rad file or mapname.rad file. Supposedly it can be made switchable using a +A prefixed texture name, in the same way as Switchable Animating textures above. Other textures, like animated or regular, can also give off light if listed in lights.rad file.
problems = bad compiles stop lights from working. Too many different light types (8) shining on any brush cause compile crash. Memory used is the square of the number of lights on a brush face, 4 light types = 16 times the memory usage of 1 light type on a brush face - for EACH brush. But 8 identical lights do not cause a problem.

Masked/Transparent Textures ({), this is used for invisible, or semi-transparent textures, like ladders. It needs to be used with an entity like func wall or func illusionary with solid mode and fx set at 255. Texture for transparent part must be 0 0 255 blue, in Wally palette position #255. It must be entity, cannot block VIS.
problems = this texture is often made incorrectly, or set up incorrectly with the entity - be careful! Even totally invisible textures still make wpolys. ALL sides of a brush should be the same texture, although SKY or {invisible can sometimes cover a thin face or two.

Liquid/Water Procedural (!), if this texture covers a brush then the engine assumes it is liquid and treats it like such. If you would like it see-thru, then you have to tie to entity func water and set the flags. Does not block VIS in any way.
problems = ALL sides of a brush should be the same water texture, or a compile problem or game problem may occur.

Scroll (SCROLL), used for scrolling signs or conveyor belts. May be switchable with a +A texture like animated? It must be an entity, does not block VIS.
problems = if custom, the texture may require square size, such as 128x128; difficult to work with.

SKY (SKY), used for sky environments. can give off light when a light environment entity is used and ALL sides of the brush are covered with SKY. SKY does not create wpolys, so SKY generally cause less lag than regular {invisible textured brush faces. Does not block VIS.
problems = if zoner's compiling tools are not used, then mapper must block off sky with CLIP, or players can "Get out of map". Transparent within a map, will not block VIS inside a map, or between 2 map sections. SKY does not create wpolys, it is rendered in a manner similar to sprites, and so like sprites one can only measure the lag caused by the fps(frames per second).

HINT/SKIP (HINT/SKIP), a pair of textures of limited use, to split VIS leaf/portals so that line-of-sight & r_speeds can be reduced in some situations. Invisible, transparent, do not make wpolys, do not affect players, do not block VIS directly.
problems = hard to understand usage, and misuse may increase r_speeds; also ALL sides of a brush must be either HINT or SKIP, no other textures mixing allowed.

CLIP (CLIP), used to block & guide player movement. It does not stop grenades or gunfire, is invisible, does not block VIS.
problems = misuse can be irritating, and ALL sides of a brush must be CLIP, no mixing textures allowed.

AAATRIGGER (AAATRIGGER), used to help mappers visualize invisible brush entities, like triggers. It is usually invisible, but should NOT be used as a regular texture - it causes a compile problems and lighting problems. It MUST be an entity so it does not block VIS.
problems = if visible causes compile problems, and causes lighting problems along with odd scrolling & resizes in map, and can make HL & mods crash. Keep it invisible in an entity.

ORIGIN (ORIGIN), used to denote the axis of swinging platforms & rotating fans, hinges of rotating doors, track connection of trains, ground connection of vehicles, and pivots of pendulums. Must be part of an entity. Invisible, does not block VIS.
problems = if alone in map, or if more than one ORIGIN used per entity, then it causes compile crash; ALL sides of a brush must be ORIGIN, no mixing textures allowed.

Partially Supported Textures:

Translucent (@ or TRANSLUCENT), this is a rarely used texture not listed in the sdk. It is a regular texture without any clip, so you can walk thru it! Yet, if it is NOT tied to an entity, it blocks VIS! Good uses are for walkthru bead doors, walkthru curtains, or very tall elephant grass.
problems = must be very thin, or may lead to hall-of-mirrors problems, somewhat experimental and may not work with all mods.

Proposed EXPERIMENTAL Textures:

NULL (), proposed in Valve ERC forums, possibly under development, to be used like CAULK in Quake, or SKIP in HL - except it can be mixed on a brush with other textures. It will remove that face it covers from the map. It will not block VIS.
problems = will probably be many....

VIS one way (), proposed in Valve ERC forums, but not under development. It would block VIS line-of-sight in one direction, but not the other - sort of a one way glass except for VIS. It would be of the same type invisible order as HINT/SKIP and CLIP.
problems = will probably be many....

Texture Sounds:

Texture sounds (various textures), the materials.txt file lists the textures that have special sounds associated with them. It is best NOT to change this file, since everyone has the same standard file, but to change instead the name of your texture to match one of the names in the materials.txt file.
problems = Of course check there is not another texture of the same name in one of the WADs you are using in WC.

by Tommy14,

with help from: Koala Jones, Uno1 ,nazgul, Danger-Mouse, and funatic.

 Back to Tutorials Page   Other Tutorials by Tommy14 

 Rate this tutorial for us! 
 Poor   1  2  3  4  5  Excellent
 Usefulness of Content  
Get Hammer level editor, the most commonly used editor for CS and HL levels.
- - - - - - - - - - - -

Get Zoner's Half-Life Compile Tools, the premier compiling tools for CS maps.
- - - - - - - - - - - -

Get the "experts" Hammer configuration for CS mappers to utilize advanced custom CS entities.
- - - - - - - - - - - -

An improved CS:S entity definition file, to allow CS:S mappers to use all entities and options.
- - - - - - - - - - - -