【Unreal Engine】Material Fundamentals: PBR Concepts and Essential Node Usage

Material Creation Challenges

In building beautiful game worlds with Unreal Engine (UE), materials are one of the most important elements. However, many beginners stumble here. Are you struggling with thoughts like "I just applied textures but it looks cheap somehow" or "There are too many nodes—I don't know where to start"?

Materials aren't simply for setting "color" or "patterns." They're blueprints of physics laws defining how light and objects interact. Understanding this blueprint and properly connecting nodes is what allows your 3D models to reflect light and have texture like the real world.

This article focuses on the essential nodes and material parameters (input pins) that beginners should first understand, based on Unreal Engine 5's Physically Based Rendering (PBR) concepts, thoroughly explaining practical material creation fundamentals.

---

Basic PBR Concepts

Materials in Unreal Engine are assets defining how mesh (3D model) surfaces behave with light. To define this behavior, UE adopts Physically Based Rendering (PBR).

PBR's core is "simulating light reflection in ways that follow real-world physics laws." This enables consistently realistic texture expression under any lighting environment.

The main parameters you set in the Material Editor (Base Color, Metallic, Roughness, etc.) define "material characteristics" based on these PBR laws.

Material Editor Basic Structure

The Material Editor is a node-based visual scripting environment.

Element	Role
Input Pins	Connection points to output nodes determining the material's final characteristics (Base Color, Metallic, etc.).
Nodes	Processing units that generate, process, and combine data (colors, textures, numbers).
Wires	Lines that flow data between nodes. Data types (Scalar, Vector, etc.) must match.
Output Node	Node applying the final result to the mesh (usually the large node in the center).

---

5 Essential Nodes

The Material Editor has hundreds of nodes, but mastering these 5 first enables creating most materials.

2.1. Constant Nodes

Constant nodes provide fixed numerical values or colors throughout the material.

Constant (Scalar)

Outputs a single floating-point number (Scalar Value). Mainly used for parameters defining texture in the 0-1 range like Metallic and Roughness.

Constant3Vector (Color)

Outputs three floating-point numbers (Vector3) for Red (R), Green (G), Blue (B). Mainly used for defining "colors" like Base Color and Emissive Color.

Constant4Vector

Outputs Vector4 with four values: R, G, B, plus Alpha (A).

2.2. Texture Sample

The most important node for loading texture assets (image files) and outputting their color information.

Parameter	Role
Texture	Specifies the texture asset to load.
UVs	Defines where on the mesh and at what scale to map the texture. Usually connect a Texture Coordinate node.

Best Practice: In PBR workflows, use multiple texture samplers for different purposes: Base Color, Normal Map, Roughness Map, Metallic Map, etc.

2.3. Arithmetic Nodes

Perform mathematical operations on input numbers or colors. Combining these adjusts texture colors or blends multiple effects.

Node	Function	Main Use
Multiply	Multiplies two inputs. Used to darken colors (multiply by 0.5) or increase texture intensity (multiply by 2.0).	Texture brightness adjustment, color multiplication.
Add	Adds two inputs. Mainly used to add multiple light source effects to Emissive Color or for texture offset.	Combining multiple effects, UV offset.
Power	Raises input A to the power of input B. Often used to adjust highlight sharpness (specular).	Roughness adjustment, highlight emphasis.

2.4. Linear Interpolate (Lerp)

Linearly blends (interpolates) two input values A and B at the ratio specified by Alpha input.

• When Alpha = 0, output is A.
• When Alpha = 1, output is B.
• When Alpha = 0.5, output is midpoint between A and B.

Practical Example: When creating wet ground material, connect dry Roughness value to A, wet Roughness value (lower) to B, and puddle mask texture to Alpha to lower roughness only in puddle areas.

2.5. Coordinate Nodes

Provide position and texture coordinate information on meshes.

Texture Coordinate

Outputs UV coordinates for mapping textures to meshes. Changing this node's UTiling and VTiling parameters easily adjusts texture repetition (tiling).

World Position

Outputs the mesh's absolute coordinates in world space. Using this enables creating advanced materials that automatically blend snow or moss based on object height.

---

Main Input Pins

The input pins on the Material Editor's output node are the "material blueprint" defining PBR physical characteristics. Connecting appropriate values (nodes) to these pins is the key to realistic texture expression.

3.1. Base Color

Role: Defines the diffuse reflection light color or specular reflection light color of the material. Value Range: Vector3 (RGB Color). PBR Notes:

• Metal (Metallic = 1): Base Color defines reflection light color (metal color).
• Non-metal (Metallic = 0): Base Color defines diffuse reflection light color (paint or plastic color).
• To accurately reproduce real material colors, avoid very bright colors (RGB values above 240) or very dark colors (RGB values below 10).

3.2. Metallic

Role: Defines whether the material is metal or non-metal. Value Range: Scalar (0.0 to 1.0).

• 0.0 (black): Non-metal (dielectric). Wood, stone, plastic, fabric, etc.
• 1.0 (white): Metal (conductor). Iron, gold, copper, etc.

Common Mistake: Using intermediate values between 0.0 and 1.0 (like 0.5) should be avoided except for special cases like alloys or rusted metal. Real materials are almost entirely either metal or non-metal.

3.3. Roughness

Role: Defines the degree of microscopic surface irregularities (microsurface), controlling light reflection "blur." Value Range: Scalar (0.0 to 1.0).

• 0.0 (black): Perfectly smooth mirror surface. Light reflects concentrated at one point.
• 1.0 (white): Completely rough surface. Light diffuses, highlights become large and blurry.

Practical Hint: Most real materials fall between 0.3 and 0.7. 0.0 and 1.0 are extreme values limited to special expression.

3.4. Normal

Role: Manipulates "apparent surface direction" to express fine bumps (detail) without changing mesh shape. Value Range: Vector3 (Normal Map texture). Importance: Normal Maps store normal information in texture blue, green, and red channels for Z, Y, and X axes respectively. Just connecting a Normal Map to this pin dramatically increases material realism.

💡 About Normal Map Format

Unreal Engine uses DirectX format Normal Maps. Some software like Blender exports in OpenGL format, which may have the Y-axis (green channel) inverted. If display looks wrong, enable the "Flip Green Channel" option in the texture's Details panel.

3.5. Emissive Color

Role: Makes the material appear to emit light (self-illumination). Value Range: Vector3 (RGB Color).

💡 Emissive Color in UE5's Lumen

In UE5's Lumen (Global Illumination and Reflection system), Emissive Color can actually illuminate surroundings as a light source. However, whether Emissive functions effectively as a light source depends on conditions like emitting surface area, luminosity intensity, and Lumen settings. Small areas with weak luminosity have limited environmental impact—illuminating environments like neon signs or display screens requires sufficient area and Emissive values (tens to hundreds). Consider performance costs too.

---

PBR Tiling Material Creation Example

Here we'll explain node connection examples for the most common and practical "PBR tiling material using textures."

4.1. Preparing Required Textures

High-quality PBR materials require at minimum these 4 texture types:

1. Base Color Map (Albedo): Diffuse reflection light color information.
2. Normal Map: Surface bump information.
3. Roughness Map: Surface roughness information (black and white).
4. Metallic Map: Metallicity information (black and white, unnecessary for non-metals).

4.2. Basic Node Connection Steps

1. Place Texture Coordinate Node:
   • Place a Texture Coordinate node and adjust UTiling and VTiling to set tiling (e.g., 2.0, 2.0).
2. Connect Texture Samplers:
   • Place four Texture Sample nodes and set each with the above 4 texture assets.
   • Connect the step 1 Texture Coordinate node to all Texture Sample nodes' UVs pins.
3. Connect to Output Node:
   • Connect Base Color Map's RGB output to main output node's Base Color pin.
   • Connect Normal Map's RGB output to main output node's Normal pin.
   • Connect Roughness Map's R (or G, B—any works, usually R) output to main output node's Roughness pin.
   • Connect Metallic Map's R output to main output node's Metallic pin.

4.3. Texture Intensity Adjustment (Using Multiply Node)

Using textures as-is may be too strong or weak. Roughness especially often needs adjustment.

graph LR
    A[Roughness Map (Texture Sample)] -->|RGB| B(Multiply);
    C[Constant (Scalar: 0.5)] -->|A| B;
    B -->|Result| D[Roughness Pin];

In the above example, Multiply node halves the Roughness Map values overall. This reduces surface roughness for a more glossy appearance.

---

Common Mistakes and Best Practices

5.1. Common Mistakes

1. Using PBR Rule-Violating Values

   • Metallic: Casually using values other than 0.0 and 1.0 (like 0.2 or 0.8).
   • Roughness: Using extreme values like 0.0 (mirror) or 1.0 (chalk) across wide areas.
   • Base Color: Using completely white (RGB: 255, 255, 255) or completely black (RGB: 0, 0, 0). These don't exist in real materials.

2. Ignoring Texture Data Types

   • When loading black-and-white (grayscale) textures like Roughness or Metallic, UE defaults to treating them as color information. These textures need sRGB unchecked in texture sampler node settings. sRGB is color space gamma correction and shouldn't be applied to data (numerical values) like Roughness.

3. Not Using Material Instances

   • Directly changing values in the Material Editor changes all meshes using that material. Recompiling materials for every minor adjustment like color or Roughness is inefficient.

5.2. Best Practice: Using Material Instances

Material Instances are a feature that inherits the original material's (master material's) structure while allowing external changes to only specific parameter values (constants, colors, etc.).

1. Parameterize in Master Material:
   • Right-click on Constant or Constant3Vector nodes and select "Convert to Parameter."
   • Give parameters descriptive names (e.g., Roughness_Value, Base_Color_Tint).
2. Create Material Instance:
   • Right-click the master material in Content Browser and select "Create Material Instance."
3. Adjust in Instance:
   • Opening the created Material Instance lets you adjust only parameter-exposed items in real-time without compilation.

This enables creating countless variations with different colors and textures from one master material, dramatically improving development efficiency.

---

Summary

Here's a summary of material fundamentals explained in this article.

Item	Overview	Nodes/Pins to Master
Understanding PBR	Materials are blueprints defining physics laws of light. Metallic and Roughness are core.	Metallic, Roughness pins
Data Sources	Three types of data compose materials: numbers, colors, textures.	Constant, Constant3Vector, Texture Sample
Data Processing	Adjust/blend data with arithmetic nodes and Lerp.	Multiply, Add, Power, Lerp
Coordinate Control	Control how textures are applied.	Texture Coordinate
Efficiency	Make adjustments with Material Instances to reduce compile time.	Convert to Parameter

Materials are deep, but start by understanding four node types—"constants," "textures," "arithmetic," "Lerp"—and four main pins—"Base Color," "Metallic," "Roughness," "Normal"—and setting values following PBR rules.