Skip to main content

Toon Liquid Shader - Unity Shader


Toon Liquid Shader

This is how the shader will end up looking :
liquid shader object with wobble physics
Shader along with simple liquid wobble physics
liquid shader preview
Liquid shader preview
This shader is pretty neat and somewhat easy to implement as well as to understand. Since we will be adding some basic physics to the toon water as it is moved about we will have to support that in the vertex shader as well.
So let's start by looking at the properties :
Properties
{
 _Colour ("Colour", Color) = (1,1,1,1)
 _FillAmount ("Fill Amount", Range(-10,10)) = 0.0
 [HideInInspector] _WobbleX ("WobbleX", Range(-1,1)) = 0.0
 [HideInInspector] _WobbleZ ("WobbleZ", Range(-1,1)) = 0.0
 _TopColor ("Top Color", Color) = (1,1,1,1)
 _FoamColor ("Foam Line Color", Color) = (1,1,1,1)
 _Rim ("Foam Line Width", Range(0,0.1)) = 0.0
 _RimColor ("Rim Color", Color) = (1,1,1,1)
 _RimPower ("Rim Power", Range(0,10)) = 0.0
}
Just the usual stuff that we are used to. The only thing that may stand out is the [HideInInspector] tag, This works just like the HideInInspector attribute we have while writing C# code. This tag prevents this property from being displayed in the editor while viewing the material. However we can still access this property from our C# code during run time.
Now we will go through how they were declared in CG PROGRAM.
/*1*/float _FillAmount;
/*2*/float _WobbleX;
/*3*/float _WobbleZ;
/*4*/float4 _TopColor;
/*5*/float4 _RimColor;
/*6*/float4 _FoamColor;
/*7*/float4 _Colour;
/*8*/float _Rim;
/*9*/float _RimPower;
  1. _FillAmount is the height of the liquid, Larger the value the more it's filled.
  2. _WobbleX when we have rudimentary physics for the liquid to move about this affects x-axis motion.
  3. _WobbleZ when we have rudimentary physics for the liquid to move about this affects z-axis motion.
  4. _TopColor refers to the top part of the foam's color.
  5. _RimColor refers to the rim lighting color.
  6. _FoamColor is the foam's color.
  7. _Colour is the actual liquid's color.
  8. _Rim is the amount of rim lighting used.
  9. _RimPower is the sharpness of the rim lighting.
We have to set up some conditions for our pass:
Pass
{
 Zwrite On
 Cull Off // we want the front and back faces
 AlphaToMask On // transparency
 CGPROGRAM
 #pragma vertex vert
 #pragma fragment frag
 .
 .
 .
}
If you have been following the blog for a while now you should know what Zwrite On, Cull Off do.
Here we are not performing culling as the front face acts as the actual container and the back face which is a simple color acts as the top of the liquid thereby making it look solid even though it's not.

But AlphaToMask On might be new to you. AlphaMask will add wherever the geometry of the object ends up to a mask which won't allow geometry of the same material to come through as along as the alpha value at that point is less than what is already in the mask. (At least from what I understood. 😅)
Let's get started with the vertex shader :
float4 RotateAroundYInDegrees (float4 vertex, float degrees)
{
 float alpha = degrees * UNITY_PI / 180;
 float sina, cosa;
 sincos(alpha, sina, cosa);
 float2x2 m = float2x2(cosa, sina, -sina, cosa);
 return float4(vertex.yz , mul(m, vertex.xz)).xzyw ;
}

v2f vert (appdata v)
{
 v2f o;
 o.vertex = UnityObjectToClipPos(v.vertex);
 float3 worldPos = mul (unity_ObjectToWorld, v.vertex.xyz);
 // rotate it around XY
 float3 worldPosX= RotateAroundYInDegrees(float4(worldPos,0),360);
 // rotate around XZ
 float3 worldPosZ = float3 (worldPosX.y, worldPosX.z, worldPosX.x);
 // combine rotations with worldPos, based on sine wave from script
 float3 worldPosAdjusted = worldPos + (worldPosX  * _WobbleX)+ (worldPosZ* _WobbleZ); 
 // how high up the liquid is
 o.fillEdge =  worldPosAdjusted.y + _FillAmount;
 o.viewDir = normalize(ObjSpaceViewDir(v.vertex));
 o.normal = v.normal;
 return o;
}
Most of it is explained by the comments themselves but if the wobble thing seems confusing remember that it is just lifting side upwards or downwards depending on the position of the vertex and the wobble values given to the shader for each axis. 
*Remember no vertices are moved around in this shader only the value for how much the liquid is supposed to rise up is passed to the fragment shader.
Fragment shader :
fixed4 frag (v2f i, fixed facing : VFACE) : SV_Target
{
   // rim light
   float dotProduct = 1 - pow(dot(i.normal, i.viewDir), _RimPower);
   float4 RimResult = smoothstep(0.5, 1.0, dotProduct);
   RimResult *= _RimColor;
   // foam edge
   /* 1 */ float4 foam = ( step(i.fillEdge, 0.5) - step(i.fillEdge, (0.5 - _Rim)));
   float4 foamColored = foam * (_FoamColor * 0.75);
   // rest of the liquid
   float4 result = step(i.fillEdge, 0.5) - foam;
   float4 resultColored = result * _Colour;
   // both together
   float4 finalResult = resultColored + foamColored;
   finalResult.rgb += RimResult;
   // color of backfaces/ top
   float4 topColor = _TopColor * (foam + result);
   //VFACE returns positive for front facing, negative for backfacing
   /* 2 */return facing > 0 ? finalResult : topColor;
}
Here again most of it is explained through comments but we will go over the unusual bits.
Let's break it down :
  1. The step function will return 0.0 unless the value is over 0.5 otherwise it will return 1.0.
    So when we make the foam edge we take a small part near the top so for that purpose we use the step function.
  2. You may have noticed that this fragment function has an extra parameter called VFACE and this gives us information about which face it is. Is the the back face or front face?
    If it is front face it gives us positive values ( > 0) or if it is back face it gives negative values ( < 0). Depending on the type of face we color it differently.
Let's move on to making the C# file that goes along with this.
using UnityEngine;
public class Wobble : MonoBehaviour
{
    public float MaxWobble = 0.03f;
    public float WobbleSpeed = 5.0f;
    public float RecoveryRate = 1f;

    Renderer rend;
    Vector3 prevPos;
    Vector3 prevRot;
    float wobbleAmountToAddX;
    float wobbleAmountToAddZ;

    void Start()
    {
        rend = GetComponent<Renderer>();
    }

    private void Update()
    {
        // 1. decreases the wobble over time
        wobbleAmountToAddX = Mathf.Lerp(wobbleAmountToAddX, 0, Time.deltaTime * RecoveryRate);
        wobbleAmountToAddZ = Mathf.Lerp(wobbleAmountToAddZ, 0, Time.deltaTime * RecoveryRate);

        // 2.make a sine wave of the decreasing wobble
        float wobbleAmountX = wobbleAmountToAddX * Mathf.Sin(WobbleSpeed * Time.time);
        float wobbleAmountZ = wobbleAmountToAddZ * Mathf.Sin(WobbleSpeed * Time.time);

        // 3.send it to the shader
        rend.material.SetFloat("_WobbleX", wobbleAmountX);
        rend.material.SetFloat("_WobbleZ", wobbleAmountZ);

        // 4.Move Speed
        Vector3 moveSpeed = (prevPos - transform.position) / Time.deltaTime;
        Vector3 rotationDelta = transform.rotation.eulerAngles - prevRot;

        // 5.add clamped speed to wobble
        wobbleAmountToAddX += Mathf.Clamp((moveSpeed.x + (rotationDelta.z * 0.2f)) * MaxWobble, -MaxWobble, MaxWobble);
        wobbleAmountToAddZ += Mathf.Clamp((moveSpeed.z + (rotationDelta.x * 0.2f)) * MaxWobble, -MaxWobble, MaxWobble);

        // 6.save the last position
        prevPos = transform.position;
        prevRot = transform.rotation.eulerAngles;
    }
}
This adds a wobble to the liquid making it look like it's being affected by the motion of the object.
  1. Here whatever the value of wobbleAmountToAddX/Y will tend to go back to 0 with time. The larger the RecoveryRate the faster the liquid will settle.
  2. Now a sin function will take the place of a simple liquid wobbling approximation. This sin function will keep returning values between -1.0 to +1.0. The effect of the sin function is only noticeable if the wobbleAmountToAddX/Y is greater than 0.0.
  3. Sending the wobbleAmountX/Z values to shader. 
  4. moveSpeed stores how fast the object moved in each axis from previous frame.
    The rotationDelta just contains the change in rotation in each axis from the previous frame.
  5. wobbleAmountToAddX/Z is assigned a value which is an arbitrary calculation that takes into consideration the moveSpeed as well the rotationDelta to determine the wobble.
  6. Just saving the position and rotation of the object for use in the next frame to calculate the moveSpeed and rotationDelta.
That's it! Hope you learnt 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 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…

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:
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 PreparationModel It
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 wi…

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…