This post continues the tutorial on volumetric rendering, introducing one of the most used techniques: **raymarching**.

You can find here all the other posts in this series:

- Part 1: Volumetric Rendering
**Part 2: Raymarching**- Part 3: Surface Shading
- Part 4: Signed Distance Fields
- Part 5: Ambient Occlusion
- Part 6: Hard and Soft Shadows
- Part 7: Volume Raycasting

### Introduction

Loosely speaking, the standard behaviour of Unity 5’s lighting engine stops the rendering when a ray from the camera hits the surface of an object. There is no built-in mechanism for those rays to penetrate within the surface of an object. To compensate for this, we have have introduced a technique called **raymarch**. What we have in a fragment shader is the position of the point we are rendering (in world coordinates), and the view direction from the camera. We can manually extends those rays, making them hit custom geometries that exists only within the shader code. The barebone shade that allows us to do this is:

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 |
struct v2f { float4 pos : SV_POSITION; // Clip space float3 wPos : TEXCOORD1; // World position }; // Vertex function v2f vert (appdata_full v) { v2f o; o.pos = mul(UNITY_MATRIX_MVP, v.vertex); o.wPos = mul(_Object2World, v.vertex).xyz; return o; } // Fragment function fixed4 frag (v2f i) : SV_Target { float3 worldPosition = i.wPos; float3 viewDirection = normalize(i.wPos - _WorldSpaceCameraPos); return raymarch (worldPosition, viewDirection); } |

The rest of this post will provide different implementations for the raymarch function.

### Raymarching with Constant Step

The first implementation of raymarching introduced in Volume Rendering used a constant step. Each ray is extended by STEP_SIZE in the view direction, until it hits something. If that’s the case, we draw red pixel, otherwise a white one.

Raymarching with constant step can be implemented with the following code:

1 2 3 4 5 6 7 8 9 10 11 12 |
fixed4 raymarch (float3 position, float3 direction) { for (int i = 0; i < STEPS; i++) { if ( sphereHit(position) ) return fixed4(1,0,0,1); // Red position += direction * STEP_SIZE; } return fixed4(0,0,0,1); // White } |

As seen already, it renders unsexy, flat geometries:

The post Surface Shading will be dedicated entirely to give threedimensionality to volumetric geometries. Before that, need to focus on a better implementation of the raymarch technique.

### Distance Aided Raymarching

What makes raymarching with constant step very inefficient is the fact that rays advances by the same amount every time, regardless of the geometry that fills the volumetric world. The performance of a shader suffers immensely by adding loops. If we want to use real time volumetric rendering, we need to find better a more efficient solution.

We would like a way of estimating how far a ray can travel without hitting a piece of geometry. In order for this technique to work, we need to be able to estimate the distance from our geometry. In the previous post we have used a function called sphereHit which indicated whether a point was inside a sphere or not:

1 2 3 4 |
bool sphereHit (float3 p) { return distance(p,_Centre) < _Radius; } |

We can change it in such a way that instead of a boolean value, it returns a distance:

1 2 3 4 |
float sphereDistance (float3 p) { return distance(p,_Centre) - _Radius; } |

This now belongs to a family of functions called **signed distance functions**. As the name suggests, it provides a measure which can be positive or negative. When positive, we are outside the sphere; when negative we are inside and when zero we are exactly on its surface.

What sphereDistance allows us is to have a conservative estimation of how far our ray can travel without hitting a sphere. Without any proper shading, volumetric rendering is fairly uninteresting. Even if this example might seem trivial with a single sphere, it becomes a valuable technique with more complex geometries. The following image (from Distance Estimated 3D Fractals) show how raymarch works. Each ray travels for as long as its distance from the closest object. In such a way we can dramatically reduce the number of steps required to hit a volume.

This brings us to the the distance-aided implementation of raymarching:

1 2 3 4 5 6 7 8 9 10 11 12 |
fixed4 raymarch (float3 position, float3 direction) { for (int i = 0; i < STEPS; i++) { float distance = sphereDistance(position); if (distance < MIN_DISTANCE) return i / (float) STEPS; position += distance * direction; } return 0; } |

To better understand how it works, we replaced the surface rendering with a colour gradient that indicates how many steps were requires for raymarch to hit a piece of geometry:

It’s immediately obvious that the flat geometry that faces the camera can be identified immediately. The edges, instead, are much trickier. This technique also estimate how close we are to any nearby geometry. We will see in a future instalment, Ambient Occlusion, how this can be helpful to add details to our volume.

### Conclusion

This post introduces the de-facto standard technique used for real time raymarching shaders. The rays advances in the volumetric medium according to a conservative estimation of the closest nearby geometry.

**The next post will focus on how to use distance functions to create geometrical primitives, and how they can be combined together to create whichever shape you want.**

#### Other Resources

- Part 1: Volumetric Rendering
**Part 2: Raymarching**- Part 3: Surface Shading
- Part 4: Signed Distance Fields
- Part 5: Ambient Occlusion
- Part 6: Hard and Soft Shadows
- Part 7: Volume Raycasting

##### 📧 Stay updated

A new tutorial is released every week.

##### 💖 Support this blog

This websites exists thanks to the contribution of patrons on Patreon. If you think these posts have either helped or inspired you, please consider supporting this blog.

I created a scene, put a cube in it, applied the material created with the shader of Raymarching with constant step, the code is correct, but the cube stays white all the time. Any reason for this?

This code doesn’t seem to work. The raymarch method always returns 0 for all values of _Radius and MIN_DISTANCE.

I had to fiddle around with this a lot to get results that looked even a little like Alan’s. The best MIN_DISTANCE value I found was 0.01. Declared like: #define MIN_DISTANCE 0.01

direction need normalize

How can you have a unity camera go within the volume contained inside the cube. Say for example I wanted to clip through it while the camera passes through it? I assume once the camera clips the mesh it no longer renders anything.

Hey! Exactly, that’s a big issue.

One solution is to use a billboard quad to render your volume.

You can also play with Cull Off.

Unfortunately there’s no one-line solution. Also, you have to take into account the camera position to interpolate the values properly; not just the view direction.

Very nice tutorial, but it would be nice if the animgif would show the actual expected output of the example and the boolean cube. It’s hard to see if I’m actually doing it right. 🙂

edit: and NOT the boolean cube, ofcourse. No boolean pun intended! 🙂

Amazing!!!

I make this shader here:

https://github.com/smkplus/UnityRayMarching

Ohh that’s so nice!

I’m glad this tutorial has helped you!

Great tutorial, just one question. In an attempt to get the cube to still display while the camera is inside of it, I tried turning Culling to Front and instead of passing the geometry position(of the cube) into raymarcher, passing in the world camera position. Oddly, it seemed to work. Why do we use the Intersection position as the origin from our raymarching, and not the world camera position?

Hey! It all depends on what you are trying to achieve.

If you are inside a cube that is culling its back faces, nothing will be drawn.

If you are inside a cube, you can have a two pass shader that uses the back faces to draw based on camera position. That, as you suggested, should work! 😀

Thanks so much for this wonderful series of tutorials! I’ve been meaning to learn about volumetric rendering for a long time. I’m having a slight issue which is that my cube gets distorted around edges, not sure what’s happening. Any ideas?

https://imgur.com/ntES7Z8

Mmm is very hard to tell what’s wrong without the shader code!