Skip to main content

Pixelation Shader - Unity Shader


Pixelation Shader

This is the correct way (one of many) of showing pixelation as a post-processing effect.
This effect will work in any aspect ratio without any pixel size scaling issues as well as it is very minimal in terms of coding it up.
image effect that pixelates the screen
pixelate image effect in action

In order to get this to work 2 components have to be set up:
1) The pixelation image effect
2) The script - which will be attached to the camera

So let's get started by creating a new image effect shader.
We will take a look at our Shaderlab properties :
_MainTex("Texture", 2D) = "white" {}
That's it, Everything else will be private and not shown in the editor.
Now we will see what are defined along with the _MainTex but are private.
sampler2D _MainTex;
int _PixelDensity;
float2 _AspectRatioMultiplier;
We will pass _PixelDensity & _AspectRatioMultiplier values from the script.
As this is an image effect there is no need to play around with the vertex shader.
Let's take a look at our fragment shader:
fixed4 frag (v2f i) : SV_Target
{
   float2 pixelScaling = _PixelDensity * _AspectRatioMultiplier;
   i.uv = round(i.uv * pixelScaling)/ pixelScaling;
   return tex2D(_MainTex, i.uv);
}
That's it ? 😒
Well.... ya... But still, let me break it down.
Firstly let us take out the aspect ratio correction stuff :
i.uv = round(i.uv * 100.0)/ 100.0;
If you replace the previous i.uv statement with this one you will still see that the image is pixelated but if your game aspect ratio is anything other than a square then it will stretch horizontally if the game window width is more than it's height and vise-versa.
Now let's get into the meat of it :
The round function basically converts a float like 0.6 to 1 and 0.4 to 0; It converts a float with a decimal point to the closest integer.
The uv.x & uv.y values go from 0 to 1. So if you multiply uv co-ordinate (0.125, 0.125) by 100 then you will end up with (12.5, 12.5) and then round it, you will get (12, 12) then you bring it back into the 0 to 1 range by dividing by the same amount; Now it's (0.12, 0.12). These same result will be for uv co-ordinates (0.126, 0.126), (0.129, 0.129) etc...
So the output color will keep taking color input from the same uv co-ordinate. That's how the pixelation effect is achieved.
We will now see how the aspect ratio is corrected in the C# script.
using UnityEngine;

[ExecuteInEditMode, RequireComponent(typeof(Camera))]
public class PixelateImageEffect : MonoBehaviour
{
    public Material material;
    public int pixelDensity = 80;

    private void OnRenderImage(RenderTexture source, RenderTexture destination)
    {
        Vector2 aspectRatioData;
        if (Screen.height > Screen.width)
            aspectRatioData = new Vector2((float)Screen.width / Screen.height, 1);
        else
            aspectRatioData = new Vector2(1, (float)Screen.height / Screen.width);
        material.SetVector("_AspectRatioMultiplier", aspectRatioData);
        material.SetInt("_PixelDensity", pixelDensity);
        Graphics.Blit(source, destination, material);
    }
}
You might be familiar with the OnRenderImage function if you have been following the blog for a while.
This function runs after everything on screen is rendered and two render textures are passed into it, source & destination.
the source is the input RenderTexture and destination is the output RenderTexture. You perform some changes to the source and apply it on the destination. The Graphics.Blit(source, destination, material) is basically doing just that.

'material' property is the post-porcessing material that was made with the shader.
We pass in the values for the pixel-density and aspect-ratio multiplier with the material.SetInt() & material.SetVector() methods.
Now we determine the value of 'aspectRatioData' which is a Vector2.
The x component of aspectRatioData is the multiplier for x-axis of uv and y component is for y-axis of uv.
if (Screen.height > Screen.width)
    aspectRatioData = new Vector2((float)Screen.width / Screen.height, 1);
else
    aspectRatioData = new Vector2(1, (float)Screen.height / Screen.width);
So if the height was greater then the x component was the ratio between width and the height and the y component was 1 ( when multiplied will remain same ).
If the width is greater then the y component will be the ratio between height & width and x component will be 1.
I hope you learned something today. Do not forget to share this if you liked it.
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.
For the entire source code, go : HERE
For more Shader development goodness, go : HERE
For Unity development tutorials, go : HERE

Comments

Assets Worth Checking Out

POPULAR POSTS

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…

Toon Liquid Shader - Unity Shader

Toon Liquid Shader This is how the shader will end up looking :
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 j…

Alto's Adventure Style Procedural Surface Generation Part 1

Alto's Adventure Style - Procedural Surface Generation This game appears to be a strictly 2D game but if you have played it enough you will notice that some of the art assets used look like it's 3D ( I don't know if they are tho ). If you haven't played the game you are missing out on one the most visually pleasing and calming games out there ( There is literally a mode called Zen mode in the game ).
Anyway, I am going to show you how to make a procedural 2D world ( without the trees, buildings and background ) like in Alto's Adventure.
But you may notice I have a plane which is in in the Z-axis giving a depth to the surface which is not there in Alto's Adventure but if you want to know how to do it then that will be in part 2.
To achieve the same effect of Alto's Adventure ( I'm leaving that up to you ) only minimal changes are needed to the code that I am going to explain.
We are going to be using the plane mesh in unity for creating the 2D surface as th…

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...…