To understand Multitexture 2.04, one must understand the environment in which it operates:
The true deep magic of 2.04 was only unlocked on NVidia hardware via the GL_NV_register_combiners extension. Suddenly, you weren't chaining texture stages—you were programming a tiny SIMD machine inside the GPU.
You had:
A typical 2.04 register combiner setup looked like this pseudocode:
// Stage 0: Diffuse * Lightmap (RGB) R0.rgb = TEX0.rgb * TEX1.rgb// Stage 1: Dot3 bump (stores result in alpha) R1.rgb = TEX2.rgb (normal map) R1.a = DOT3(R1.rgb, CONSTANT_LIGHT_DIR) multitexture 2.04
// Stage 2: Combine R2.rgb = R0.rgb * R1.a // lightmapped diffuse * bump lighting R2.rgb = R2.rgb + SPECULAR_TEX3.rgb
Output = R2
This wasn't programming. This was alchemy. Every register was precious. You'd debug by flipping swizzles and watching the colors shift. If you ran out of registers, you'd sacrifice specular highlights or move detail maps to a second pass. To understand Multitexture 2
For engines like the original GoldSrc (Half-Life) or Id Tech 2 (Quake 2), lightmap scale and texture alignment are critical. Multitexture 2.04 handles the conversion between world units and texels with a raw precision that modern "smart" tools often automate incorrectly. If you are modding Counter-Strike 1.6 or Half-Life: Blue Shift, 2.04 is still the industry standard.
Cause: The plugin file (.dlt) is missing on slave nodes.
Solution: Copy MT_204.dlt to every render node’s plugins folder. Ensure the license file is identical on all machines. A typical 2