Uploaded October 2018 | Updated November 2026, 2 hours ago
Welcome back!
Let's expand our Ripple Shader so it's a bit easier to control and set the groundwork for some of the upcoming features we'll want to build for it. We're going to create two features:
The first is to move the distance or radius of the pulse ring into the Vector component that describes its location. This will add a fourth dimension to its location to represent the time it has existed in the world. We can also use this time value to control other things like the opacity of the effect, so the rippling pulse fades out over time and becomes less vivid.
The second feature is the ability to manually create new pulses using the mouse. This will allow us to raycast a point from our mouse into our scene and assign the shaders pulse origin to that value. It's simple, and there are still some issues with it (we can only create a single ripple) but it's a good step for building a more complex system in the future.
The complete Ripple Effect Shader playlist: youtube.com/playlist?list=PLEwYhelKHmigqgiurk2lz6l8gRtVaL2zz
The Shield Shader where we learn how to pass arrays to our shaders: youtube.com/playlist?list=PLEwYhelKHmihp8GNb-XXWE5VhqikYwluj
We've built a number of really cool Visual Effects over the past few years. You can check out some of their implementations and use them yourself by grabbing the code from GitHub: github.com/WorldOfZero/UnityVisualizations
Come and join the World of Zero Discord, we'd love to have you stop by: discord.gg/hU5Kq2u
Welcome back!
Let's expand our Ripple Shader so it's a bit easier to control and set the groundwork for some of the upcoming features we'll want to build for it. We're going to create two features:
The first is to move the distance or radius of the pulse ring into the Vector component that describes its location. This will add a fourth dimension to its location to represent the time it has existed in the world. We can also use this time value to control other things like the opacity of the effect, so the rippling pulse fades out over time and becomes less vivid.
The second feature is the ability to manually create new pulses using the mouse. This will allow us to raycast a point from our mouse into our scene and assign the shaders pulse origin to that value. It's simple, and there are still some issues with it (we can only create a single ripple) but it's a good step for building a more complex system in the future.
The complete Ripple Effect Shader playlist: youtube.com/playlist?list=PLEwYhelKHmigqgiurk2lz6l8gRtVaL2zz
The Shield Shader where we learn how to pass arrays to our shaders: youtube.com/playlist?list=PLEwYhelKHmihp8GNb-XXWE5VhqikYwluj
We've built a number of really cool Visual Effects over the past few years. You can check out some of their implementations and use them yourself by grabbing the code from GitHub: github.com/WorldOfZero/UnityVisualizations
Come and join the World of Zero Discord, we'd love to have you stop by: discord.gg/hU5Kq2u



![Correcting Lighting on our Grid Snapped Vertex Shader with Geometry Shaders
Lets fix our grid snapped vertex custom shader by introducing some improved lighting. Because were manipulating our objects geometry inside our shader the normals that are used to calculate lighting are incorrect. This causes objects to appear oddly smooth and lighting effects to look very different from what youd expect based on the geometry you see. We cant just correct the normals of each vertex because doing that would still cause the normal value to be interpolated along each of the triangles of our mesh (causing a smoothing effect). To resolve this were going to implement a geometry shader which allows us to dynamically recreate the mesh inside our shader so we can provide data that can be tweaked to our needs.
If present a geometry shader occurs after an a vertex shader but before the fragment shader following one of these two paths:
```mermaid
graph LR;
vert([Vertex Shader])
geom([Geometry Shader])
frag([Fragment Shader])
vert v2g ˃geom
geom g2f ˃frag
vert v2f ˃frag
```
It is not necessary for a geometry shader to recreate the same geometry that was passed in. The output can be completely modified to introduce additional information (weve used that capability in our [Grass Shader](https://youtu.be/b2AlyCNbYmY)). In this case our needs are simpler though, we are going to be using the geometry shader to isolate each triangle of our mesh. Doing this means that we can avoid interpolation caused by multiple triangles sharing a vertices without having to make those modification in our original mesh beforehand. This allows our shader to be compatible with any shape instead of just meshes specifically designed for this effect.
Our geometry shader recreates each triangle and assigns all the vertices of that triangle a unique normal so the face has uniform lighting. We also calculate the diffuse lighting we use inside of the geometry shader and pass that information along to the fragment shader. The geometry shader were using looks like this (assuming our vertex shader provides world space coordinates):
```shader
[maxvertexcount(3)]
void geom(triangle v2g IN[3], inout TriangleStream˂g2f˃ triStream)
{
float3 lightPosition = _WorldSpaceLightPos0;
float3 v0 = IN[0].pos.xyz;
float3 v1 = IN[1].pos.xyz;
float3 v2 = IN[2].pos.xyz;
float3 normal = normalize(cross(v0 - v1, v1 - v2));
float lightStrength = (dot(lightPosition, normal) + 1) / 2;
g2f OUT;
OUT.norm = normal;
OUT.lightStrength = lightStrength;
OUT.pos = mul(UNITY_MATRIX_VP, IN[0].pos);
triStream.Append(OUT);
OUT.pos = mul(UNITY_MATRIX_VP, IN[1].pos);
triStream.Append(OUT);
OUT.pos = mul(UNITY_MATRIX_VP, IN[2].pos);
triStream.Append(OUT);
}
```
***
My intro to exploring Geometry Shaders: https://youtu.be/HY6qFbmbij8
My video covering implementing diffuse lighting in more detail: https://youtu.be/4XfXOEDzBx4
A collection of other visual effects weve built: https://www.youtube.com/watch?v=l_2uGpjBMl4&list=PLEwYhelKHmig6ttzH0nRL3OOQsGLtVrtX
Watch the entire series where we explore this concept of snapping vertices to a grid: https://www.youtube.com/watch?v=e8NItqF_9hQ&list=PLEwYhelKHmiixWR3Tn5dYt1iUlSCL6OFq
Join the World of Zero Discord Server: https://discord.gg/hU5Kq2u Correcting Lighting on our Grid Snapped Vertex Shader with Geometry Shaders](https://i.ytimg.com/vi/VC-v874C5xQ/mqdefault.jpg)


. This retrieves a `MonoBehavior` from any `GameObject` in our scene which matches the type were searching for. This search method is not the final solution well end up using later in development, but for testing right now its more than enough to get us what we want. We can use the reference we retrieve to replace the actual instantiation, effectively moving the parts of the code we want into a separate place.
To make things a little easier and to make sure our new component is more useful well still do some of the lifting in the Asteroids code. This includes calculating the rotation and world position of each new Chunk of the Asteroid. We do this so that the controller we built can be used to generate brand new Asteroids and not just create debris from existing ones.
There is still a bit more to do to get a fully functioning destruction system (we dont track health yet for example), but this gets us to a place where object destruction and creation works reliably well.
The base subdivision destruction system was built in a Live Stream which you can find here: https://youtu.be/POVJ-QIyygE
Join the World of Zero Discord Server: https://discord.gg/hU5Kq2u Creating a Subchunk Spawner for Asteroids VR](https://i.ytimg.com/vi/VaGI6j_4e7Y/mqdefault.jpg)



