$texturegroup

It allows a model to have multiple skins consisting of one or more materials.
Alternate skins are typically included in props to allow more variety in model appearances, without needing to create more models.
== Syntax ==
 $texturegroup <name>
 {
 	{ "<default material>" } //Skin 0 (default)
 	{ "<new material>" } //Skin 1
 	[...]
 }
; name
: The name of the texturegroup. 
: 
; default material
: The name of a material (VMT) on a reference mesh.
; new material
: The name of a material (VMT) that will replace the material above it.
For models with multiple materials, $texturegroup accepts multiple materials per line. When used like this, the first skin should be treated as a set of column headings in a table. Only materials present in the first skin can change in any subsequent skins.
 $texturegroup <name>
 {
 	{ "<default material 1>" "<default material 2>" [...] } //Skin 0 (default)
 	{ "<new material 1>" "<new material 2>" [...] } //Skin 1
 	[...]
 }
Studiomdl allows up to 32 unique materials to exist on a model. This limit is hard-coded, but can be raised with a hacked studiomdl.
== Examples ==
 $texturegroup rockcliff_cluster01
 {
 	{ rockcliff02a }
 	{ rockcliff02b }
 	{ rockcliff02c }
 }
 $cdmaterials models\bots\sniper models\effects
 $texturegroup skinfamilies
 {
 	{ sniper_bot_red sniper_bot_head_red }
 	{ sniper_bot_blue sniper_bot_head_blue }
 
 	{ invulnfx_red invulnfx_red }
 	{ invulnfx_blue invulnfx_blue }
 }
 $cdmaterials models\player\hvyweapon
 $texturegroup skinfamilies
 {
 	{ heavy_head_red eyeball_r eyeball_l hvyweapon_red hvyweapon_red_sheen }
 	{ heavy_head_blue eyeball_r eyeball_l hvyweapon_blue hvyweapon_blue_sheen }
 
 	{ heavy_head_red_invun eyeball_invun eyeball_invun hvyweapon_red_invun hvyweapon_red_invun }
 	{ heavy_head_blue_invun eyeball_invun eyeball_invun hvyweapon_blue_invun hvyweapon_blue_invun }
 
 	{ heavy_head_zombie eyeball_zombie eyeball_zombie heavy_red_zombie_alphatest heavy_red_zombie_alphatest_sheen }
 	{ heavy_head_zombie eyeball_zombie eyeball_zombie heavy_blue_zombie_alphatest heavy_blue_zombie_alphatest_sheen }
 
 	{ heavy_head_red_invun eyeball_invun eyeball_invun hvyweapon_red_zombie_invun hvyweapon_red_zombie_invun }
 	{ heavy_head_blue_invun eyeball_invun eyeball_invun hvyweapon_blue_zombie_invun hvyweapon_blue_zombie_invun }
 }
== Multiple Texture Groups ==
Using more than one $texturegroup is allowed but not recommended. The behavior of multiple texture groups is unintuitive at best.
As a result of the above problems, despite what the syntax would imply, using multiple $texturegroup commands will not actually allow multiple states of a model's skins to be switched between, unlike .
If a model needs to have multiple texture states, they will have to be done by setting up skins in a fashion similar to this:
 $texturegroup skinfamilies
 {
 	{ <state 1> <substate 1> }
 	{ <state 1> <substate 2> }
 	{ <state 2> <substate 1> }
 	{ <state 2> <substate 2> }
 	[...]
 }
== Replacing Material With Material of Same Name From Different Folder ==
To replace a material with a material using the same name from a different folder, add ".." to the replacement material, followed by the new folder name of the replacement material.
".." pops the directory your original material is in, allowing you to enter a new folder, similar to .
Adding lines for the replacement materials locations is not required in this case.
If you just want to use another material that does not have the same name, you can just use another $CDMaterials line instead.
Example from the rescue helicopter:
 $CDMaterials "models\c2m5_helicopter_extraction\"
 $TextureGroup "skinfamilies"
 {
 	{ "helicopter_news_adj" "helicopter_news2" } //helicopter_news2 from models\c2m5_helicopter_extraction\
 	{ "..\hybridPhysx\helicopter_news_adj" "..\hybridPhysx\helicopter_news2" } //helicopter_news2 from models/hybridPhysx
 	{ "..\hybridPhysx\helicopter_army" "..\hybridPhysx\helicopter_army2" } //Could also add second $cdmaterials line and just use "helicopter_army2"
 }
== Further Information ==
* Skin options can also be used to provide , , etc. options for the model in each VMT. For optimization, See also and LOD Models.
* All alternative VTF textures should follow the same UV map layout.
* Even though studiomdl has a hardcoded limit of 32 unique materials, it technically supports up to 1024 total skins, so long as each skin is an arrangement of those 32 materials.
* Almost every team-colored model in the game has at least two skins. Typically, the default skin is RED, and the second skin is BLU.
== See also ==
* Multiple Skins for a Single Model
* 
* 
* - Same concept as , but for submodels
==External links==
Any of these modifications to studiomdl will allow you to compile with more than 32 materials:
* StdPatch
* QuickMdl
* Cra0kalo2013
texturegroup