This page has been translated automatically.
Video Tutorials
How To
Professional (SIM)
Interface Overview
Assets Workflow
Settings and Preferences
Working With Projects
Adjusting Node Parameters
Setting Up Materials
Setting Up Properties
Landscape Tool
Using Editor Tools for Specific Tasks
Extending Editor Functionality
Built-in Node Types
Light Sources
World Nodes
Sound Objects
Pathfinding Objects
Setting Up Development Environment
Usage Examples
UUSL (Unified UNIGINE Shader Language)
File Formats
Materials and Shaders
Rebuilding the Engine Tools
Double Precision Coordinates
Common Functionality
Controls-Related Classes
Engine-Related Classes
Filesystem Functionality
GUI-Related Classes
Math Functionality
Node-Related Classes
Objects-Related Classes
Networking Functionality
Pathfinding-Related Classes
Physics-Related Classes
Plugins-Related Classes
IG Plugin
CIGIConnector Plugin
Rendering-Related Classes
Content Creation
Content Optimization
Material Nodes Library
Art Samples
Warning! This version of documentation is OUTDATED, as it describes an older SDK version! Please switch to the documentation for the latest SDK version.
Warning! This version of documentation describes an old SDK version which is no longer supported! Please upgrade to the latest SDK version.

Material Editor

Material Editor enables you to create your own materials visually without writing a single line of code - simply create and connect nodes building a graph! It is simple enough for users who are new to materials creation and powerful enough to let you do a lot of things. A brief list of features includes:

  • Ability to create your own base materials (.mgraph) and use them as directly assigned to objects or as parent materials for hundreds of other materials to avoid reassembling the material graph over and over again. The Materials hierarchy window will help you.
  • Ability to create your own custom graph nodes using other nodes (Subgraphs), or using your code. When you change the contents of a Subgraph, all materials using it will be updated as well.
  • Ability to switch between material types (there are five available at the moment: Mesh Opaque PBR, Mesh Alpha Test PBR, Mesh Transparent PBR, Mesh Transparent Unlit, Decal PBR).
  • Optional toggling of performance-affecting features on and off.
  • Ability to construct the final material's UI, you can add various parameters and even combine them into groups for convenience.
  • Connector - a special 'collapsed' mode of a graph node when it occupies less space and can be attached right to an input of another graph node.
  • Expression - a special node enabling you to write simple arithmetic operations, but the main thing is that you can use it as a swizzle in combination with the ability to change the number of data components. Be sure you'll like it!
  • Ability to write code in a special Function node, here you can implement even multiple functions calling each other.
  • You can drag-n-drop textures from the Asset Browser or directly from your file manager, and they will be automatically imported with the corresponding nodes added to the graph.
  • Loops - a complex, but very cool feature enabling you to repeat an arbitrary sequence of actions multiple times. We have analyzed multiple existing implementations of graph loops and invented a new one that is almost on par with loops in code. Why not write loops in code then? Because using a graph makes implementation of complex things inside a loop much easier than doing the same in code.
  • When working with complex or large graphs, you may end up with your wires are all over the place crisscrossing each other and you may want more visual clarity. That's when portals come into play. You can connect a wire to a Portal In node at one location and then place a Portal Out node at any other location you need and take what you've supplied to Portal In from a Portal Out (like you dug a tunnel for your wire under the node graph).

See Also#

Material Graph Asset#

A Material Graph asset (.mgraph) is both a source material network (node-based description to be compiled into a material) and a normal base material that can be assigned to a mesh surface.

To create a new Material Graph, right-click in the Asset Browser to open the Create menu, then select Create Material -> Material Graph.

Specify a name for your graph asset. A new *.mgraph asset will be created in the current folder of your project.

As the Material Graph asset represents a base material, it is also available in the root of the Materials Hierarchy and can be assigned to supported surfaces and objects. Depending on the material's type it can be assigned to the following objects:

Working with Material Graphs#

Right-click on the *.mgraph asset and choose Edit Graph or simply double-click the asset to open it in the Material Editor window.

The Material Editor window includes the Graph View displaying the material graph network and the settings panel.

The material graph network consists of nodes — functional blocks accountable for processing input data. By composing the graph network, you define the look of your material.

The Material node is the master node of your material. It provides a set of inputs for graphic data and generates a material of a specific type depending on the current settings.

Finally, the output from the Master Node is connected to the Final node — the primary output material node.

A material graph can contain several Material nodes, but only the one connected to the Final node will be used.

Press the Save button to save changes and compile the material graph to a base material. Compilation errors, if any, will be listed in the Warnings and Errors panel and in the Console window.

Navigation Controls#

Mouse Wheel drag Pan material graph
Mouse Wheel scroll Zoom in/out
RMB / Space key Display node creation palette
LMB click Select node / edge
LMB drag on background Select nodes with the rectangle tool
Shift + LMB on node Add to node selection
Ctrl + LMB on node Remove from node selection
LMB drag on node Move the selected nodes
Ctrl + C Copy the selected nodes to the clipboard
Ctrl + V Paste nodes from the clipboard
Ctrl + D Clone the selected nodes
Delete Key Delete the selected nodes / edge
Copying and pasting networks of nodes is performed via a text format for convenient sharing of material graphs and their parts, so you can copy a shared text representation of a graph network and paste it right to your material editor.

Common Settings#

The Common Settings define the set of supported features for the material.

Type The type of the output material:
  • Physically-based mesh materials:
    • Mesh Opaque PBRdeferred opaque material;
    • Mesh Alpha Test PBRdeferred alpha test material;
    • Mesh Transparent PBRforward (transparent) material;
  • Mesh Transparent Unlit — transparent non-physical material;
  • Decal PBRdeferred decal material.
Vertex Mode Defines the mode for vertex adjustment and tessellation inputs:
  • Position — vertex positions are replaced by new values.
  • Offset — new values are added to original vertex positions.
Vertex Space Defines the vector space for vertex adjustment and tessellation. Options depend on the Vertex Mode selected:
  • Position Vertex Mode:
    • Camera World — positions are relative to the camera position.
    • Object — positions are relative to the object's pivot.
    • View — positions are relative to the camera.
    • Absolute World — positions are relative to the world origin.
  • Offset Vertex Mode:
    • World — offsets are relative to the world origin.
    • Object — offsets are relative to the object's pivot.
    • Tangent — offsets are relative to the surface tangent.
    • View — offsets are relative to the camera.
Normal Space Defines the space for normal vectors:
  • World;
  • Object;
  • Tangent;
  • View.
Depth Mode Defines how the Depth data is treated:
  • Offset;
  • Override.
Depth Shadow Flag indicating whether custom depth affects shadows.
Tessellation Enables the Tessellation-related inputs and Tessellation settings.
Two Sided Enables the Two Sidedoption.
Write Velocity Offset Enables the Velocity input.
Advanced Mode Enables the Compilation Settings.

Transparent Material Settings#

The following settings are available only for the Mesh Transparent PBR and Mesh Transparent Unlit material types.

Blend Mode

Blending preset. One of the following can be selected:

  • Alpha blend;
  • Additive;
  • Multiplicative;
  • Disabled;
  • Custom.
Blend Src Option used to scale the source color (the color of an overlaying material). Available only when Custom preset is selected.
Blend Dest Option used to scale the destination color (the color of an obscured material). Available only when Custom preset is selected.
Overlap Enables the Overlap option.
Depth Test Enables the Depth Test option.
Depth Write Enables the Depth Write option.
Participate in PostEffects Enables the Post Processing options.

Decal Material Settings#

The following settings are available only for the Decal PBR material types.

Normal Under Decal

Defines the tangent space (Tangent-Binormal-Normal matrix) used for normal mapping:

  • Take From Decal Mesh — normals of the decal mesh (for Mesh decals) or plane (for Orthographic and Projected decals) are used;
  • Up Direction of Decal — decal's local up vector is used;
  • GBuffer Normal — normals from the screen normal buffer are used;
  • GBuffer Depth Based Normal — normals are constructed based on the screen depth buffer content. Unlike GBuffer Normal, this option provides unaltered normals as they are presented in the scene geometry.
Normal Blend Mode

Blending mode for decal's normals:

  • Alpha Blend;
  • Additive.
Screen Projection Enables Screen Projection of the decal instead of projecting it onto a surface (only Mesh decals are supported).

Compilation Settings#

These settings are only for the Direct3D compiler (DirectX API).

It is not recommended to make changes to the default values without understanding these settings.
Optimization Level Level of shader optimization and arithmetic refactoring (such as merging a multiply instruction followed by an add into a fused mad):
  • The level 0 means no optimization at all. Compilation is fast and provides the slowest code.
  • The other levels correspond to gradually increasing extent of optimization up to the highest level 4.
Warning Mode The following modes are available:
  • Disable — warnings are disabled;
  • Soft — warnings are logged but ignored;
  • Hard — warnings are considered errors.
IEEE Strictness Forces the IEEE strict compile.


In the Parameters panel, you define the list of material parameters.

The following controls are available:

  • Add — add a new parameter.
  • Clone — clone the selected parameter.
  • Move Up — move the selected parameter up in the list.
  • Move Down — move the selected parameter down in the list.
  • Remove — remove the selected parameter.

When adding a new parameter, you should specify the parameter's Name, Type, and default settings in the parameter creation dialog. The following set of parameter types is provided:

  • Slider — a float value within the specified range ([0.0f; 1.0f] by default).
  • Color — a float vector of 4 components representing a color value.
  • Texture2D, Texture3D, Texture2DArray, TextureCube — a texture of the corresponding type.
  • Group — an auxiliary type for grouping parameters. Use the and buttons to rearrange and group parameters.
  • Float, Float2, Float3, Float4 — a float value or a vector of N float values.
  • Int, Int2, Int3, Int4 — an integer value or a vector of N integer values.

To use a parameter in your material graph, drag the item to the Graph View to create a node of the corresponding type:

Warnings and Errors#

The Warnings and Errors panel enables you to track problems in the material graph and is visible only if there are any.

The panel lists all problem nodes in the graph, select an entry to see the problems with its ports or data in the Message section.

Some warnings may appear after migrating your content to a higher SDK version. These are reminder warnings meant to notify about changes in the logic of certain nodes. You can discard the warning by using the Remove Warning button.


Nodes of Material Editor are functional blocks that represent data sources and processing instructions similar to variables and functions in shader programming.

Most nodes have the output preview shown on a preview sphere (for most nodes) or a plane (for textures).

Some nodes have a set of settings defining their behavior. Double-clicking the node opens the dialog for adjustment of the node's settings.

Nodes that have no more than one input and one output port have a special connector mode — they are collapsible for convenience. A collapsed node connected to another node becomes attached to it. Drag the collapsed node to break the connection and detach the node.

Nodes are split into several groups based on their applicability and color-coded for better identification.


A port defines an input (left side) or output (right side) of a node. Connecting edges to a port allows data to flow through the Material Graph node network.

Each port has a data type defining edges that can be connected to it. All data types are color-coded, meaning that each of them has an associated color used for identification.

float float2 float3 float4
int int2 int3 int4
matrix — a matrix of float values: float2×2, float3×3, float4×4.
texture — any type of a texture: Texture2D, Texture3D, Texture2DArray and TextureCube.
bool — a boolean value used in logical nodes and loops.
any — arbitrary data type meaning the port supports several data types.
error — indicates an error (e.g., no required input provided or type conversion has failed).

Only one edge can be connected to any input port, but you can connect multiple edges to an output port.

Most input ports have a default input value.


An edge represents a connection between two ports (input and output). Edges define how data flows through the Material Graph node network. You can only connect an edge from an output port to an input port.

A new edge is created by dragging from the desired output port to the desired input port or vice versa. To remove an edge select it with the left click and hit Delete.

Port Adapters#

Port adapter is a feature giving you the ability to select data components in an arbitrary order, combine and rearrange them, providing convenient access to elements and a lot of flexibility. It is available for the following data types:

  • bool;
  • float, float2, float3, float4;
  • int, int2, int3, int4.

When you drag a new edge to an input port, a number of available connection options shall appear:

  • The = option provides the direct connection in the case the input type can provide all needed data components.
  • Selecting another option creates an Expression node accountable for type conversion.

You can change the adapter later by double-clicking the expression and editing the field. The Expression node enables you to write simple arithmetic operations and even use the Unigine Graphic API.

Adding New Nodes#

In order to add a new node, right-click on the background or press Space and select a node type from the palette or type its name in the Search field to find it.

Dragging an edge from an input port opens a node creation palette with a pre-set filter to the required data type for the corresponding port.

Textures can be dragged directly from the Asset Browser. In this case, a Sample Texture node with corresponding settings will be added automatically.


Sometimes you need to perform certain actions multiple times, cloning the relevant groups of nodes will make your graph overcomplicated very quickly, even if only 10 iterations are required. In UNIGINE, you can create loops for that, just like in programming.

To create a loop, add the Loop Begin and Loop End nodes and connect their Loop ports.

To add changing variables to the loop, connect nodes with starting values to the Add port of the Loop Begin node. By double-clicking the Loop Begin node, you can open the Input Constructor enabling you to rearrange, rename, delete existing inputs and implicitly set their type as well as set the maximum number of iterations.

Then, build a graph implementing the functionality of a single iteration, the result of which should be passed to the Loop End node for further iterations. You can use the result of all iterations further in your graph.

You can use the Index of the current iteration and the Maximum Iterations values in your logic. The Index starts with 0 and is equal to Maximum Iterations-1 at the last iteration.

Here's an example of a simple loop, incrementing a value by 0.1 10 times:

The Loop End node has the break input port that takes a boolean value, false by default. Passing a truth value (e.g., obtained via Logical Nodes) will interrupt the loop and exit the current iteration.

Custom Code#

No matter how advanced the materials system is, you might want something specific, maybe too complicated to implement via basic nodes. Or sometimes, it might be quicker to write several lines of code for mathematical operations instead of spawning a bunch of nodes and connecting them. The solution is simple - create a Function node and wrap any shader function into it. Input and output ports for the node shall be automatically generated according to the function's signature.

To add or edit code to the node double-click on the node, the Code Editor window will open. You can write as many functions as you need, the last function in the code will be considered the main one.


Sometimes, especially in complex material graphs, there are too many crisscrossing edges making the whole graph look like a spiderweb, and the data flow very hard to understand. A portal is a set of special nodes including a single input and one or more outputs, all having the same name. Portals serve to reduce the number of edges and make the graph more 'readable'.

To create a portal, start with adding a Portal In node. Connect an input to the new node and double-click on it to adjust its color and name.

And then you can create as many Portal Out nodes as you need. By double-clicking on a Portal Out node you can select the name of the desired input portal in case several portals are used.


A Subgraph is a special type of material graph, which can be referenced from inside other material graphs. This can be very useful when the same operations are to be performed multiple times in a single graph or across multiple graphs. You simply pack these operations into a box with a set of inputs and outputs and then use this box anywhere you need. A Subgraph differs from a Material Graph in three main ways:

  • A Subgraph does not generate any material, it is used as a building block in material graphs.
  • A Subgraph does not have Material and Final nodes. Instead, it has two nodes called Inputs and Outputs, defining all input and output ports.
  • A Subgraph is stored in a *.msubgraph asset.

Basically, the process of construction of a Subgraph is the same as when you create a Material Graph.

To create a new Subgraph, right-click in the Asset Browser to open the Create menu, then select Create Material -> Material Graph.

Click Save to apply and save changes.

All subgraphs are automatically added to the palette, so if your start typing a name of such a subgraph in the search field of the node creation palette, it will be displayed in the list.

Configuring Inputs and Outputs#

Double click on the Inputs node or the Outputs node to open the constructor panel enabling you to add, rearrange, delete and set the name and type of input and output ports of the subgraph correspondingly.

By connecting nodes to the ports of the Inputs node, you specify the optional ports of the subgraph having default values.

Using Subgraphs#

To add a subgraph to your material graph currently opened in the Editor, simply find it by name in the node creation palette or drag it from the Asset Browser, or you can add the Sub Graph node to your graph network, specify the *.msubgraph asset by double-clicking the node, and connect necessary edges to input and output ports of the subgraph.

There is a set of core subgraphs implementing basic functionality (like contrast, refract, object_triplanar, etc.) stored in the core/subgraphs folder.

Last update: 2022-03-10
Build: ()