//Oh, hey there! //This tutorial is in the process of being rewritten, so what you see here is actually a work in progress, //about 95% complete.
In this tutorial, I will attempt to show you how to enable custom tinting through shaders, as found on the single-player skins.
Before we begin, we're going to need a skin to actually use this on. For this tutorial, we'll use the Shadowtrooper, and make his chest crystal use custom tinting.
The texture we're modifying.
The new 'base' texture.
The crystal. Note how it is desaturated (grayscale). This is crucial.
RGB tinting is handled shader-side, in the rgbGen modifier. There are two possible modes that follow rgbGen: Entity, and lightingDiffuseEntity. 'rgbGen lightingDiffuseEntity' results in tinting with normal lighting, while 'rgbGen Entity' forces the stage to full-bright.
Great, we just made a colorful crystal. But that's not all we can do. You know how in the SP species selection menu, there's a row of solid-color icons above Frankenstein's body-part bins? Notice how most custom SP skins only have one? Well, I'm gonna show you how to make those.
If you've worked with SP skins before, you should be familiar with 'playerchoice.txt'. If not, go read an SP skin tutorial, there's too much for me to cover here. This is what you will find inside for most custom SP skins:
At a glance this may seem cryptic, but it's not. The '*white' header is actually a shader path. Moreover, this entire block can be copied and pasted with different headers to create multiple color options.
This could be added to the file, and suddenly you could pick white or red for your skin in the SP species selection menu. Be warned though: The SP menu can only fit up to 9 colors at once.
But of course, this alone isn't enough. Like I said, the header is a shader path. We need an actual shader to match. We have two options here: The space-saver method, and the super-fancy-schmancy method. The super fancy method is a shader complete with an image, while the space saver method is just a shader, using textures included in the game already.
Done! That was easy, wasn't it? Nice and simple, and no texture to pack up with the rest of the mod.
Since the fancy method involves its own image, your shader complexity depends on how complex the image is. If it's a simple, flat, still image, then you'll have a simple and short shader. If you've got something complex lined up that involves a more animated piece, you're going to have a slightly more complex shader. Whatever you do, remember it's going to be squeezed into a 32x32 pixel area.
Custom RGB Shaders
in Skinning
Posted
This tutorial is meant to teach you how to use the RGB system in your skin. This also shows you how to add tint presets to the SP species menu.
Tools you'll need
//Oh, hey there!
//This tutorial is in the process of being rewritten, so what you see here is actually a work in progress,
//about 95% complete.
In this tutorial, I will attempt to show you how to enable custom tinting through shaders, as found on the single-player skins.
Before we begin, we're going to need a skin to actually use this on. For this tutorial, we'll use the Shadowtrooper, and make his chest crystal use custom tinting.
The texture we're modifying.
The new 'base' texture.
The crystal. Note how it is desaturated (grayscale). This is crucial.
RGB tinting is handled shader-side, in the rgbGen modifier. There are two possible modes that follow rgbGen: Entity, and lightingDiffuseEntity. 'rgbGen lightingDiffuseEntity' results in tinting with normal lighting, while 'rgbGen Entity' forces the stage to full-bright.
The 'default' shader. (Pre-tint support)
models/players/shadowtrooper/accessories { { map models/players/shadowtrooper/accessories_rgb1 rgbGen lightingDiffuse } { map models/players/shadowtrooper/accessories_rgb2 blendFunc GL_ONE GL_ONE rgbGen lightingDiffuse } }Our new shader, with a dull crystal.
models/players/shadowtrooper/accessories { { map models/players/shadowtrooper/accessories_rgb1 rgbGen lightingDiffuse } { map models/players/shadowtrooper/accessories_rgb2 blendFunc GL_ONE GL_ONE rgbGen lightingDiffuseEntity } }Glowing crystal.
models/players/shadowtrooper/accessories { { map models/players/shadowtrooper/accessories_rgb1 rgbGen lightingDiffuse } { map models/players/shadowtrooper/accessories_rgb2 blendFunc GL_ONE GL_ONE rgbGen Entity glow } }Great, we just made a colorful crystal. But that's not all we can do. You know how in the SP species selection menu, there's a row of solid-color icons above Frankenstein's body-part bins? Notice how most custom SP skins only have one? Well, I'm gonna show you how to make those.
If you've worked with SP skins before, you should be familiar with 'playerchoice.txt'. If not, go read an SP skin tutorial, there's too much for me to cover here.
This is what you will find inside for most custom SP skins:
*white { setcvar ui_char_color_red 255 setcvar ui_char_color_green 255 setcvar ui_char_color_blue 255 }At a glance this may seem cryptic, but it's not. The '*white' header is actually a shader path. Moreover, this entire block can be copied and pasted with different headers to create multiple color options.
For instance:
models/players/shadowtrooper/uired { setcvar ui_char_color_red 255 setcvar ui_char_color_green 0 setcvar ui_char_color_blue 0 }This could be added to the file, and suddenly you could pick white or red for your skin in the SP species selection menu. Be warned though: The SP menu can only fit up to 9 colors at once.
But of course, this alone isn't enough. Like I said, the header is a shader path. We need an actual shader to match. We have two options here: The space-saver method, and the super-fancy-schmancy method. The super fancy method is a shader complete with an image, while the space saver method is just a shader, using textures included in the game already.
Space-Saver method:
models/players/shadowtrooper/uired { { map $whiteimage rgbGen const ( 1.000000 0.000000 0.000000 ) } }Done! That was easy, wasn't it? Nice and simple, and no texture to pack up with the rest of the mod.
Since the fancy method involves its own image, your shader complexity depends on how complex the image is. If it's a simple, flat, still image, then you'll have a simple and short shader. If you've got something complex lined up that involves a more animated piece, you're going to have a slightly more complex shader. Whatever you do, remember it's going to be squeezed into a 32x32 pixel area.