Skip to main content

Alto's Adventure Style Procedural Surface Generation Part 1

Alto's Adventure Style - Procedural Surface Generation

A Screenshot of Alto's Adventure Gameplay
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 the plane comes with 10 vertices along both it's width and height.
So modifying them will be easy because we know how many vertices are there on each row of the mesh.
This inside a class called 'SurfaceGenerator', you can call it whatever you want but remember that this class will be used in part 2.
So here are the member variables used:
public bool generateContinuosly = false;  
public bool generateCollider = false;  
public float yScaling = 5.0f; 
public float detailScaling = 1.0f;  
public Vector3[] vertices;  
private Mesh mesh;  
Nothing fancy going on, just declaring some variables. The '[ Range( float , float ) ]' is an attribute used to show in the inspector a slider with the values defined in the parameters.
And the '[ HideInInspector ]' attribute prevents public fields from being shown in the inspector.
void Start()  
   mesh = GetComponent<MeshFilter>().mesh;  
   vertices = mesh.vertices;  
void Update()  
Nothing fancy in the Start & Update functions either.
Now we will look at the 'GenerateSurface' function.
 void GenerateSurface()  
    vertices = mesh.vertices;  
    int counter = 0;   
    for (int i = 0; i < 11; i++)  
      for (int j = 0; j < 11; j++)  
        MeshCalculate(counter, i);
    mesh.vertices = vertices;  
    if (generateCollider)  
       MeshCollider collider = gameObject.AddComponent<MeshCollider>();  
       collider.sharedMesh = null;  
       collider.sharedMesh = mesh;  
Now we will look at the important stuff
MeshCalculate(counter, i); 
There will be a function called 'MeshCalculate' that takes in the index of the current vertex and the current row of that vertex (basically it's vertical offset, keep in mind this is in object space and therefore vertical does not actually mean up-down in world space, but in model/object space it is) and performs a certain set of actions which will modify the vertices of the mesh in some way.
Recaculate bounds takes up the entire set of vertices and makes a box which encloses all those points.
We have to do this inorder to make sure the bounding volume is correct.
collider.sharedMesh = null;  
collider.sharedMesh = mesh;  
sharedMesh takes the 'mesh' object used for collision detection.
we are just setting it to the updated mesh after setting the previous one to null ( not necessary ) to help with garbage collection.
void MeshCalculate(int vertexIndex, int yOffset)  
     vertices[vertexIndex].z = Mathf.PerlinNoise  
         (Time.time + (vertices[vertexIndex].x + transform.position.x) / detailScaling,  
          Time.time + (vertices[vertexIndex].y + transform.position.y)) * yScaling;  
       vertices[vertexIndex].z -= yOffset;  
     vertices[vertexIndex].z = Mathf.PerlinNoise  
        ((vertices[vertexIndex].x + transform.position.x) / detailScaling,  
        (vertices[vertexIndex].y + transform.position.y)) * yScaling;  
     vertices[vertexIndex].z -= yOffset;  
This function basically uses Perlin Noise to generate those up and down waves/hills.
vertices[vertexIndex].z -= yOffset;  
we have this line to prevent all the vertices from bunching up and just forming a single line of vertices.
   vertices[vertexIndex].z = Mathf.PerlinNoise  
       (Time.time + (vertices[vertexIndex].x + transform.position.x) / detailScaling,  
        Time.time + (vertices[vertexIndex].y + transform.position.y)) * yScaling;  
   vertices[vertexIndex].z -= yOffset;  
If the 'generateContinuosly' bool is true then it uses the Time.time value to give the seed value to the perlin noise function.
If  'generateContinuosly' is false the only factor acting as the seed to the perlin noise is the position of each individual vertex as well as the position of the object in world space.
Source code for Part 1 is available HERE.
Goto Part 2 for the rest of the tutorial, source code and unitypackage (contains everything).😀.
For more Unity development tutorials go HERE.
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.


Assets Worth Checking Out


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…

How To Animate A Fish Swimming With Shaders

Animate Fish Swimming With Shaders We are going to make swimming animation by using only shader code.
By the time we are done, it's going to look like this.
You will probably need the fish model used in this tutorial, that can be found HERE. Can use your own model but the shader code might have to be modified accordingly because of the orientation of the model that you might be using ( issues with whether the X axis & Z axis is flipped ).
The shader used way out performs a similar scene with skeletal animations applied on the fish models.
On a previous benchmark I did comparing the shader animation with the skeletal animation there was a difference of 28 FPS( on average ) with 50 fish.
The shader we are going to make is really powerful and flexible and don't think that it's limited to making fishes swim😀.

So this mesh oriented like this when imported into unity and this is important to understand because this means that the model's vertices have to be moved along the X-…

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…

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.

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

Access Reflection Probe Data For Custom Shaders

The Unity shader documentation regarding reflection probes is pretty minimal and not at all comprehensive.
This short tutorial is intended to bring reflection probe functionalities to the forefront your future shader writing endevors which is a fancy way of saying "Look at this cool stuff and go and use it somewhere" 😏
Here we will try just the bare minimum of making a shader that reflects the cubemap data from reflection probe and displays it on the object.

These reflection probes are basically objects that store a complete image of the environment surrounding it into a cubemap which then can be read by shaders to create various effects.
More information on how reflection probes work in Unity can be found here :
Using Reflection Probes In Unity

I am not going over how to set up Reflection Probes here only how to access them inside our custom shaders.
So this is what we will be making:
The reflection probe takes in the cubemap only if it is within it's range otherwise i…