Skip to main content

Alto's Adventure Style Procedural Surface Generation Part 2


In this section we will be going through on how to make the depth surface that the ball is bouncing on. If you haven't seen Part 1, please do so and come back.
This is actually another plane which has a script that takes in a reference of the plane that does the up and down motion from the previous part.
Instead of relying on another set of perlin noise data to modify the vertices of the plane we take the first row of vertices from the plane with the 'SurfaceGenerator' component and give the same values to the current plane's vertices.
But we have to make sure that we give the 'z' value of the vertices of the 'SurfaceGenerator' object's mesh to the  'y' value of the depth surface.
I am calling that thing the depth surface because I can't think of a better word.๐Ÿ˜…
Let's call the class 'SurfaceImitator' because it imitates a surface.๐Ÿ‘.
The member variables are : 
public SurfaceGenerator reference;  
public bool generateCollider = true;  
private Mesh mesh;  
private Vector3[] vertices;  
The Start Function:
void Start()  
{  
   mesh = GetComponent<MeshFilter>().mesh;  
   vertices = mesh.vertices;  
}  
The LateUpdate Function: - We will come to why we are using 'LateUpdate' instead of  'Update' later on ( pun intended๐Ÿ˜‡)
void LateUpdate()  
{  
   vertices = mesh.vertices;  
   int counter = 0;  
   for (int i = 0; i < 11; i++)  
   {  
      for (int j = 0; j < 11; j++)  
      {            
        vertices[counter].y = reference.vertices[i].z;  
        counter++;  
      }  
    }  
   mesh.vertices = vertices;  
   mesh.RecalculateBounds();  
   mesh.RecalculateNormals();  
   if (generateCollider)  
   {  
      Destroy(GetComponent<MeshCollider>());  
      MeshCollider colliderComponent = gameObject.AddComponent<MeshCollider>();  
      colliderComponent.sharedMesh = null;  
      colliderComponent.sharedMesh = mesh;  
    }  
}  
Most of this code was already covered in the previous part.
The important part is this :
int counter = 0;  
for (int i = 0; i < 11; i++)  
{  
   for (int j = 0; j < 11; j++)  
   {            
       vertices[counter].y = reference.vertices[i].z;  
       counter++;  
   }  
}  
We are basically going through all the vertices of the mesh and setting each row's y axis value to the reference mesh's vertices ( These are not the mesh component vertices these are 'SurfaceGenerator' public member variable called 'vertices' ).
Coming to the point as to why we have to put this code in 'LateUpdate' is because of the fact that 'SurfaceGenerator' 'vertices' value gets updated on the 'Update' function of the 'SurfaceGenerator' so the values we get out of it will always be 1 frame behind all the time.
If the change in position of some of the vertices from one frame to another are very high we won't be able to match up with the 'SurfaceGenerator' vertices.
So inorder to get the current values of 'vertices' within the same frame we use 'LateUpdate'.
Source code of Part 2 is available HERE.
Unity package available HERE.
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.

Comments

Assets Worth Checking Out

POPULAR POSTS

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

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

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…

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…