Skip to main content

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.😅
  1. 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.
    gouraud shading
    Some calculations need not be done per fragment and still retain the desired quality such as UV co-ordinate modifications and world space/local space calculations.

    A good example would be rotating the UV coordinates of the skybox texture which will, in turn, pass the modified UV coordinates to the fragment shader which will render the rotated skybox.
    Even fog can be approximated per vertex and still get good results.
  2. Store Complex Functions In Texture

    A good example of this is when you need noise to achieve an effect, Most of the time sampling from a noise texture is more performant than calculating per it fragment/vertex.
    perlin noise
    Another example would be ambient occlusion, Baked in ambient occlusion basically comes for free as it can be considered as a part of the albedo/diffuse texture itself.

    Ambient occlusion solutions like SSAO should only be opted to be used in cases where the game visuals require better visual interaction of objects with surrounding geometry.
  3.   Avoid Non-Constant Math

    Never re-calculate something everytime the shader is called either use uniforms or declare constants within the shader itself.
    There are main 3 ways of achieving less non-constant code.
    1. declare a variable with a constant value.
      Example of doing it correctly:

      float x = 22.0/7.0;
      float y = 3.5 * sin(3.14);
      Example of doing it wrong:

      float x = 22.0;
      x = x/7.0;
      float y = sin(3.14);
      y *= 3.5;
    2.  Using #defines to declare universal constants like PI and it's variants like TWO_PI, HALF_PI etc.
      These can be defined anywhere in the CG PROGRAM. It is best to declare all #defines on top.

      #define PI 3.14159
      #define HALF_PI 1.57079
      #define TWO_PI
    3.  Use regular const statements perform the same function as #defines but these const statements can only be declared within the vertex/fragment shader.

      const float PI = 3.14159
  4. Use Lowest Precision Possible( applies mainly to mobile )

    On PCs and on most consoles all the precision will be maintained at highest precision but on mobiles, the other lower precision types will be considered as well.
    There are 3 levels of precision: float, half & fixed.
    • Where float is 32-bit value usually used for positions, UV coordinates and in general large values.
    • -60,000 to +60,000 with 3 digits of decimal precision.
      useful for accessing image data in HDR range, UV coordinates as well general floating point operations that don't exceed its range.
    • fixed has a value range between -2.0 to +2.0 mostly used when dealing with colors, not in HDR range.
  5. Multiply Scalar Values Before Vector Values

    Multiplying scalar values with each other is a simple and fast operation but if a scalar is multiplied with a vector then each value in the vector has to be multiplied with the scalar.
    So multiply all the scalars first then multiply the result with the vectors involved thereby reducing the number of instructions needed to be executed.
    Example of doing it correctly:

    float height = 2.45;
    float width = 1.22;
    float3 world = float3(1, 3, 5);
    float3 pos = (height * width) * world;
    Example of doing it wrong:

    float height = 2.45;
    float width = 1.22;
    float3 world = float3(1, 3, 5);
    float3 pos = height * (width * world);
  6. Avoid Branching Based On Dynamically Set Values

    Branching code usually the main culprit when it comes to slow shader performance.
    However branching only causes slow down if the condition being checked is local and is subject to change with each vertex/fragment, This is due to how GPUs perform calculations.

    Uniforms and Constants, however, do not cause slowdowns because they do not change based on vertex/fragment.
    There are various techniques that can be used to prevent branching even if the values are dynamic which we will go over in Part 2 (Will Be Released Soon).
  7. Uber Shaders

    These are shaders which are a combination of 2 or more logically separate effects.
    The most straight-forward use case Uber shaders are for image effects where layer upon layer of various image effects can be dealt with by using just one that achieves the same effect.
    An example would be separate image-effects such as blurring, tone mapping & fisheye effect.
    When all these shaders are combined into just a single one it becomes way more efficient because of no need for multiple passes.

    Uber shaders tend to be quite bulky as they account for a range of use-cases and therefore usually have a lot of conditional compilation statements thereby in-turn creating multiple shader variants which can lead to longer loading times and compilation times.
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 more Shader development tutorials, go: HERE
For Unity development tutorials, go: HERE

Assets Worth Checking Out


Introduction To Replacement Shaders & Shader Keywords

What is a replacement shader? A replacement shader is a shader that gets applied to every object being rendered.
Since the camera determines what objects end up being shown on screen, The functionality for setting up replacement shaders are in the camera class as well.

A good use case of a replacement shader would be in making effects like SSAO.
Here we need access to the normals and the depth information so a replacement shader that displays only the normals can be rendered ( stored in a render texture ) and then another shader that displays the depth information ( stored in a render texture ) and then the final image is rendered with the SSAO effect by taking the two render textures as input and doing a bunch of calculations.

Another use case would be to visualize the environment differently for various reasons like how they did in City Skylines.

The function that performs shader replacement is:
Camera.SetReplacementShader( Shader shader, string replacementTag ) Takes in a shader as …

Curved Surface Shader [ Unity Implementation ]

Curved Surface Shader This is the shader that we will be having at the end of this tutorial.
 The curved surface shader is capable of achieving really varied visual effects from showing space-time curve due to gravity to a generic curved world shader that is seen in endless runners like Subway Surfers.
The concepts that you learn here can open you up to a new way of looking at shaders and if you didn't think they were the coolest thing ever already, hopefully let this be the turning point.😝.

Both the examples show above use the same exact material is just that different values have been passed to the shader.
Start by creating a new unlit shader in Unity and we will work our way from there.
First we define what the properties are:
_MainTex("Texture", 2D) = "white" {} _BendAmount("Bend Amount", Vector) = (1,1,1,1) _BendOrigin("Bend Origin", Vector) = (0,0,0,0) _BendFallOff("Bend Falloff", float) = 1.0 _BendFallOffStr("Falloff s…

Noise Generation Algorithms : White Noise With Shader Example

White Noise Many of you may know what white noise is and how it can be used in code.
But there are a spectrum of  'Coloured Noises' as well these include ones like brown noise, pink, blue and violet noise all these have slightly different properties and can be very useful in creating different effects. More details on coloured noises can be found HERE.
A lot of movies as well as video games like City Skylines use white noise to add a feeling of realism and texture to the on screen content, it's also referred to as a grain filter or overlay. It is a really subtle effect and should not be over used.
Creating white noise boils down to the random function used.
While writing C++ code or C# code we have access to good pseudo-random functions from their standard libraries... but while writing code in shaders we usually have to create our own pseudo-random number generator.
One really good way of making one is by using the frac( in Unity & HLSL ) or fract( in GLSL ) functio…

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…

Making An Audio Visualizer In Unity With Blend Shapes & Audio API - Part 1

Audio Visualizer with Unity Audio API & Blend Shapes This tutorial is going to be split into two parts, The first part (this one) we are going to be covering Blendshapes, what they are, what it's used for and how to use them in Unity and in Part 2 we will cover integrating that with Unity's audio API to get the desired result.
So now you got a feel as to what we will be making.
Blendshapes are just like transitions that the vertices go through to go from being in one position in space to another with the help of a transition value. All the major 3d modelling software from Blender to Maya has it.
As you can see that the model has 2 shape keys, one called MinValue and another called MaxValue, these names don't carry over into unity but the index of the shape key( blend shape ) matters.
We will be manipulating the MaxValue to make changes to the mesh.
This is how the model looks when it has it's MaxValue set at zero.
You may have guessed now that it is just a basic linear i…