Why Custom shader fundamentals in Unity? - Purpose & Use Cases

The Big Idea

What if you could paint light and magic directly onto your game characters with just a few lines of code?

The Scenario

Imagine you want to make your game characters look shiny or have glowing eyes. Without custom shaders, you have to rely on basic colors and textures that don't change much. It's like painting a picture with only a few crayons and no way to add special effects.

The Problem

Using only built-in materials means your game looks plain and similar to others. Trying to fake effects by changing textures or lights manually is slow and often looks fake. It's hard to get smooth animations or cool lighting without writing special code.

The Solution

Custom shaders let you write small programs that tell the computer exactly how to color each pixel. This means you can create shiny metals, glowing effects, or water ripples easily. It gives you full control to make your game look unique and exciting.

Before vs After

✗ Before

material.color = Color.red;
// Only changes color, no effects

✓ After

Shader "Custom/Glow" {
  // Code to make object glow softly
}

What It Enables

Custom shaders unlock endless creative possibilities to make your game visuals stand out with unique lighting and effects.

Real Life Example

Think of a magic sword in a game that glows and pulses with light. A custom shader can create that glowing effect smoothly, making the sword look alive and powerful.

Key Takeaways

Manual coloring is limited and boring.

Custom shaders let you control pixel colors and effects directly.

This makes your game visuals more dynamic and unique.

Practice

1. What is the main purpose of a custom shader in Unity?

easy

A. To control exactly how objects look by writing small programs

B. To create 3D models from scratch

C. To write game logic and rules

D. To manage user input events

Solution

1. Step 1: Understand the role of shaders

   Shaders define how surfaces appear by controlling colors, lighting, and textures.

2. Step 2: Identify what custom shaders do

   Custom shaders let you write small programs to control object appearance beyond built-in options.

3. Final Answer:

   To control exactly how objects look by writing small programs -> Option A

4. Quick Check:

   Custom shader = control object look [OK]

Hint: Shaders control object appearance with code [OK]

Common Mistakes:

• Confusing shaders with 3D modeling
• Thinking shaders handle game logic
• Assuming shaders manage input

2. Which of the following is the correct way to start a simple Unity shader code block?

easy

A. ShaderBegin

B. StartShader

C. CGPROGRAM

D. ProgramCG

Solution

1. Step 1: Recall Unity shader syntax

   Unity shaders use CGPROGRAM to start the programmable shader code block.

2. Step 2: Check options for correct keyword

   Only CGPROGRAM is the valid keyword to begin the shader code section.

3. Final Answer:

   CGPROGRAM -> Option C

4. Quick Check:

   Shader code block starts with CGPROGRAM [OK]

Hint: Look for CGPROGRAM to start shader code [OK]

Common Mistakes:

• Using made-up keywords like StartShader
• Confusing CGPROGRAM with other terms
• Misspelling the keyword

3. What will be the output color of this simple shader fragment code?

fixed4 frag() : SV_Target {
    return fixed4(1, 0, 0, 1);
}

medium

A. Solid red color

B. Solid green color

C. Solid blue color

D. Transparent black color

Solution

1. Step 1: Analyze the returned color vector

   The function returns fixed4(1, 0, 0, 1), which means red=1, green=0, blue=0, alpha=1.

2. Step 2: Interpret color components

   Red is full intensity, green and blue are zero, alpha is fully opaque.

3. Final Answer:

   Solid red color -> Option A

4. Quick Check:

   fixed4(1,0,0,1) = red [OK]

Hint: RGBA (1,0,0,1) means solid red [OK]

Common Mistakes:

• Mixing up color channel order
• Ignoring alpha channel
• Assuming zero means white

4. Identify the error in this shader snippet:

Shader "Custom/Simple" {
    Properties {
        _Color ("Color", Color) = (1,1,1,1)
    }
    SubShader {
        Pass {
            CGPROGRAM
            fixed4 frag() : SV_Target {
                return _Color;
            }
            ENDCG
        }
    }
}

medium

A. Missing semicolon after _Color property declaration

B. _Color cannot be used directly in fragment shader

C. frag function missing input parameters

D. Incorrect use of ENDCG keyword

Solution

1. Step 1: Check Properties block syntax

   The property declaration is correct: no semicolon needed, parentheses balanced.

2. Step 2: Verify shader code block

   Properties like _Color must be declared inside CGPROGRAM as 'uniform fixed4 _Color;' to be used; direct use causes undeclared identifier error.

3. Final Answer:

   _Color cannot be used directly in fragment shader -> Option B

4. Quick Check:

   Properties need uniform declaration [OK]

Hint: Declare Properties as uniforms in CGPROGRAM [OK]

Common Mistakes:

• Assuming semicolons are needed in Properties
• Not declaring uniform for _Color
• Thinking ENDCG is incorrect

5. You want to write a custom shader that colors an object red only if its x-coordinate is positive, otherwise blue. Which fragment shader code correctly implements this?

hard

A. fixed4 frag() : SV_Target {
if (POSITION.x > 0) return fixed4(1,0,0,1);
else return fixed4(0,0,1,1);
}

B. fixed4 frag(float3 pos) : SV_Target {
if (pos.x > 0) return fixed4(1,0,0,1);
else return fixed4(0,0,1,1);
}

C. fixed4 frag(float3 pos : TEXCOORD0) : SV_Target {
return pos.x > 0 ? fixed4(1,0,0,1) : fixed4(0,0,1,1);
}

D. fixed4 frag(float3 pos : POSITION) : SV_Target {
return pos.x > 0 ? fixed4(1,0,0,1) : fixed4(0,0,1,1);
}

Solution

1. Step 1: Understand input semantics

   To access vertex position in fragment shader, use input parameter with semantic POSITION.

2. Step 2: Check code correctness

   fixed4 frag(float3 pos : POSITION) : SV_Target { return pos.x > 0 ? fixed4(1,0,0,1) : fixed4(0,0,1,1); } correctly declares pos with POSITION semantic and uses conditional operator to return red or blue.

3. Step 3: Identify errors in other options

   fixed4 frag(float3 pos) : SV_Target { if (pos.x > 0) return fixed4(1,0,0,1); else return fixed4(0,0,1,1); } lacks semantic, fixed4 frag(float3 pos : TEXCOORD0) : SV_Target { return pos.x > 0 ? fixed4(1,0,0,1) : fixed4(0,0,1,1); } uses TEXCOORD0 which is wrong for position, fixed4 frag() : SV_Target { if (POSITION.x > 0) return fixed4(1,0,0,1); else return fixed4(0,0,1,1); } uses POSITION as variable incorrectly.

4. Final Answer:

   fixed4 frag(float3 pos : POSITION) : SV_Target { return pos.x > 0 ? fixed4(1,0,0,1) : fixed4(0,0,1,1); } -> Option D

5. Quick Check:

   Use POSITION semantic for position input [OK]

Hint: Use POSITION semantic to get vertex position [OK]

Common Mistakes:

• Missing POSITION semantic in input
• Using wrong semantic like TEXCOORD0
• Referencing POSITION as variable directly