Skip to main content

Fortnite Procedural Construction Animation Shader


Fortnite Construction Shader

This shader is loosely based on the one that was presented by the Fortnite developers in their GDC talk: Inner Working Of Fortnite's Shader-Based Procedural Animations.

 Here is what we will end up with:
Fortnite building shader
This technique requires you to author the 3D model in a certain way, More or less how those Fortnite developers did.
So we need the authored 3D model and the shader that uses data we get from the model to achieve the desired effect.

There are some nuances here and there so make sure you don't miss out on the details.😗
The first step will be preparing the 3D model and putting in the required data. I used Blender 2.79 but any 3D modeling software would do.

3D Model Preparation

  1. Model It
    3d mesh
  2. Apply Vertex Colors: For the direction of flight
    Each color is a component of a vector (x, y, z). This will be considered as local space.
    Values range from -1.0 to +1.0 for each component.
    Negative values are achieved by using values of less than 0.5 and positive values with values greater than 0.5.
    Assume 'val' : Range from 0.0 - 1.0
    You can use your own mapping such as '(val - 0.5) * 2'.
    • Gives -1.0 if val was 0.0
    • Gives +1.0 if val was 1.0
    • Gives 0.0 if val was 0.5
    • Gives 0.5 if val was 0.75
    • Gives -0.5 if val was 0.25
    Basically :
    (0.0 , 0.5) maps to (-1.0 , 0.0)
    (0.5 , 1.0) maps to (0.0 , 1.0)
    The mapping I've used :
    • Gives 0.0 if val was 0.5
    • Gives +1.0 if val was 1.0
    • Gives 0.0 if val was 0.0
    • Gives 0.5 if val was 0.75
    • Gives -0.5 if val was 0.25
    • Gives -1.0 if val was 0.4999 (less than 0.5 but tending towards it)
    Basically :
    (0.0 , 0.5) maps to (0.0 , -1.0)
    (0.5 , 1.0) maps to (0.0 , 1.0)
    vertex colors
  3. UV Channel 1: For applying timing textures and rotation amount.
    The UV map is difficult to see, I suggest zooming in. Those dots placed are each of the separate vertex sections that make up the mesh.
    Shown here : Red channel = x position of UV & Green channel = y position of UV
    • The greater the UV's x coordinate of a vertex the later movement of the vertices will start ( assuming the initial stage was having all pieces together )
    • The greater the UV's y co-ordinate the more rotations about the local z-axis it will do.
    First UV Channel data for mesh
  4. UV Channel 2: Actual texture map.
    The texture used can be found here: Pexels - Antique Backdrop
    textured mesh

Fortnite Construction Surface Shader

We will be using a surface shader as our base. So go ahead and create one.
  1. Defining Our Properties
    Properties 
    {
     _Color ("Color", Color) = (1,1,1,1)
     [HideInInspector]_MainTex("Main texture", 2D) = "white"{}
     _ActualTex("Actual Texture", 2D) = "white"{}
     _Glossiness ("Smoothness", Range(0,1)) = 0.5
     _Metallic ("Metallic", Range(0,1)) = 0.0
     _Placement("Placement value", Range(-0.0, 100.0)) = 0.0
    }
    
    We don't actually end up using _MainTex in our shader, But we need to declare it here due to quirks of using a secondary UV channel.
    Since we don't end up using it we can hide it in the inspector with [HideInInspector] attribute.
  2. Input Struct & CG Declarations
    sampler2D _ActualTex;
    sampler2D _MainTex;
    half _Glossiness;
    half _Metallic;
    fixed4 _Color;
    float _Placement;
    
    struct Input 
    {
     float2 uv_MainTex; // UV co-ordinates for our timing & rotation about z-axis
     float2 uv2_ActualTex; // 2nd UV co-ordinate used for the actual texturing purposes
     float4 color : COLOR; // Vertex color
    };
    
  3. Helper Functions
    float3 ConvertToDir(float3 val)
    {
     val.x = lerp(-val.x * 2, (val.x - 0.5) * 2, step(0.5, val.x));
     val.y = lerp(-val.y * 2, (val.y - 0.5) * 2, step(0.5, val.y));
     val.z = lerp(-val.z * 2, (val.z - 0.5) * 2, step(0.5, val.z));
     //In case it's not clear, With a conditional statement : val.z = (val.z < 0.5)? -val.z * 0.5 : (val.z -0.5) * 2;
     //Alternative mapping : val.z = (val.z - 0.5) * 0.5;
     val = normalize(val);
     return val;
    }
    
    float4 RotateAroundZInDegrees (float4 vertex, float degrees)
    {
            //Creating a rotation matrix to multiply with our vertex position
     float angle = radians(degrees);
     float c = cos(angle);
     float s = sin(angle);
     float4x4 rotateZMatrix = float4x4(c,-s,0,0,
            s,c,0,0,
            0,0,1,0,
            0,0,0,1);
     return mul(vertex , rotateZMatrix);
    }
    
  4. The Vertex Shader
    void vert (inout appdata_full v) 
    {
     /*1*/float val = max((_Placement - v.texcoord.x * 100), 0);
     /*2*/v.vertex = RotateAroundZInDegrees(v.vertex, val * v.texcoord.y * 100);
     /*3*/v.vertex.xyz += ConvertToDir(v.color.xyz) * val;
    }
    
    *Note: The _Placement value is the value that determines where our vertices end up.
    v.texcoord.x:- Timing value, Determines when the movement of the vertices for that vertex starts. (Range : 0.0 - 1.0)
    v.texcoord.y:- The amount of rotation to be applied. (Range : 0.0 - 1.0)
    1. When _Placement value crosses the threshold value set by (v.texcoord.x * 100) only then the vertex moves.
    2. The lower the value of 'val' less the rotation applied on the vertex.
    3. The 'ConvertToDir(v.color.xyz)' function takes in vertex color and converts that into a direction for the vertex to move. Then we multiply with 'val' thereby determining the distance the vertex moves in that direction.
  5. The Surface Shader
    void surf (Input IN, inout SurfaceOutputStandard o) 
    {
     fixed4 c = tex2D (_ActualTex, IN.uv2_ActualTex) * _Color;
     o.Albedo = c.rgb;
     o.Metallic = _Metallic;
     o.Smoothness = _Glossiness;
     o.Alpha = c.a;
    }
    
    Nothing mystical happening here. Sampling our texture with the correct texture map and UV coordinates.
  6. Vertex Shader Declaration And Shadow Pass
    #pragma surface surf Standard fullforwardshadows vertex:vert addshadow
    We need to declare our vertex function with 'vertex:vert' since our vertex function is called 'vert'.
    We are modifying our vertices so the shadows won't look correct as it's using Unity's default shadow pass, So we need to tell Unity to use a custom shadow pass which takes into consideration those new vertex positions; To do this 'addshadow' is used in our #pragma.
That's it! Hope you learned something.
Support Bitshift Programmer by leaving a like on Bitshift Programmer Facebook Page and be updated as soon as there is a new blog post.
If you have any questions that you might have about shaders or unity development in general, don't be shy and leave a message on my facebook page or down in the comments.
For the Unity-Package, go HERE.
For the entire source code, go HERE.
For more Shader development tutorials, go: HERE
For Unity development tutorials, go: HERE

POPULAR POSTS

Gift Wrapping Convex Hull Algorithm With Unity Implementation

Convex Hull Algorithm Convex Hull algorithms are one of those algorithms that keep popping up from time to time in seemingly unrelated fields from big data to image processing to collision detection in physics engines, It seems to be all over the place. Why should you care? Cus you can do magic with it and it seems so simple to implement when you first hear about it, but when you start thinking about it, you will realize why it's not such a straightforward thing to do.
Now that I got you interested (hopefully) and now we will see just what a convex hull is.
As you may have noticed a perimeter was made with the same points that was given and these perimeter points enclose the entire set of points.
Now we have to clear up the term 'Convex'.
Convex means no part of the object is caved inwards or that none of the internal angles made by the points exceed 180 degrees.
In this example of a concave shape internal angles go beyond 180 degrees.
What are those red lines for? Well...…

Shader Optimization Part 1

The process of shader optimization can seem like trial and error... in fact, that's how it is most of the time.
Most of the time shader optimizations could be boiled down to educated guesses because each time a shader gets compiled, the GPU driver of that specific hardware is what converts your code into actual machine code, therefore, the machine code generated will be different for each GPU and the driver itself might perform some optimizations on top of your's which won't be available on another GPU, thereby making it difficult to have a standard way of writing optimal shader code.

So the best way to know for sure is to actually test it on the hardware you are targeting.
With that said, Here are some universal best ways of getting your shader to perform better.😅 Do Calculations On Vertex Shader The most commonly used case for this is lighting, an example would be Gouraud lighting, where lighting calculations are done per vertex but at the loss of quality.

Some calculatio…

Visual Upgrade - Unity Asset Store [ September, 2018 ]

Visual Overhaul - Assets That Turn Mediocre Into Drool Worthy *Note: These assets are not arranged in any way, no comparison is done. They are just really cool assets that will help make your game look at least a bit better. 😁
8. Bat Particles
7.GPU Instancing Animation
6.Colored Pencils
5.Graphics Adapter Pro
4.Sleek Render: Mobile Post Processing
3.1000+ Effects pack
2.COLR - Coloring Redefined
1.AllSky

Check out more such Unity Asset Store Gems : HERE
Don't forget to share these wonderful assets with your colleagues and friends.
Support Bitshift Programmer by leaving a like on Bitshift Programmer Facebook Page and be updated as soon as there is a new blog post.
If you have any questions that you might have about shaders, C# or Unity development in general don't be shy and leave a message on my facebook page or down in the comments.

Creating Android Plugins For Unity

Creating Android Plugins For Unity When creating a game / app with Unity which targets a specific platform like Android or iOS it would really handy if you could access some  platform specific features such as native pop-up windows ( modal dialogs ), battery status, vibration access, location access, file system access etc.. 
*Note : The following tutorial assumes that you know a bit about Android development and java in general. Even if you don't know android development I hope this tutorial shows you how easy and rewarding it is to make your own Android plugins. Before we start you should make a folder called 'Plugins' inside the 'Assets' directory and inside that create a 'Android' folder. This is where all our .aar / .jar files go which is basically a .dll file for windows folks.
We will be making a plugin that displays a Toast dialog which consists of a string we pass
from Unity and also a method that performs some math operation and returns the output…