This is a software unidirectional raytracing engine, fully written in C++17, with no dependencies or external libraries used.
If you are using MSVS, you can launch it from the project file. Alternatively, you can build it with CMake
cmake -H. -Bbuild
cmake --build build
./bin/RayTracing
As input, the program uses a scene file, where all properties are listed. Depending on the scene, object files, textures, and skyboxes might also be loaded. Scene path can be passed as an argument value at program start.
The output of the program is a single bpm file, containing a rendered image of a given resolution. BMP image format was chosen because of its simplicity.
In order to render something, we need information about scene. Those are stored in scene file. It is a text file that has several blocks:
- Options: Here all types of settings are store as a pair of =
- Object/Light: Each light or object block represents a single entity in the scene.
- End block: The scene file ends with an end block to indicate that all data has been read.
Ray tracing process for each pixel is a task that can be easily paralleled, so the program splits a scene into a set of 128x128 tiles and then renders them with a number of threads that equals to system thread count.
After scene was rendered, anti-aliasing may be applied. The process consists of 2 steps: running Sobel filter on rendered image to detect edges. And then launch tile renderer that will rewrite image pixel with color of 4 new rays launched for that pixel.
| Sobel filter result | 8x zoomed image comparison |
|---|---|
 |
 |
The simplest scene that can be rendered is a scene consisting of base shapes, like Sphere and Plane, and Point or Distant light sources. Here is an example of such a scene.
Here you can see all 4 types of surfaces:
- Diffuse - Collects info from all visible light sources
- Phong - Combines three components: ambient, diffuse, specular
- Reflective - Casts reflected ray for every ray fallen on it
- Transparent - Using Fresnel model: combines refracted and reflected rays
| Ambient | Diffuse | Specular | Final |
|---|---|---|---|
 |
 |
 |
 |
On the image below you can see the application of the skyboxes. Skybox is composed of 6 cube textures, and each time ray leaves the scene - we get color from one of those textures
In order to use Polygon Mesh, we have to first load it. There are a lot of object types that can store 3d object data, but the type of my choice was .obj file. It is relatively simple yet powerful enough to implement a full specter of features.
Backface culling is a simple technique that can give a little performance boost at the ray-triangle intersection test. If ray faces 'another side' of triangles, the intersection will not be fully computed. However, if the model has some holes in it, it may give visual artifacts:
| Backface culling on (2.1 s) | Backface culling off (2.7s) |
|---|---|
 |
 |
They do not change anything in visual appearance, however, they can boost performance up to tens of times. It does so by creating a hierarchy of bounding boxes, which allows saving a lot of ray-triangle intersections. Each box may have two ancestor boxes, or store a set of triangles. This way we may text triangles only when the ray intersects the box. Left and Right boxes are separated by SAH - Surface Area Heuristic. This program has an option to visualise those bounding boxes:
| Rendered object | Low penalty (1) | Higher penalty (10) |
|---|---|---|
 |
 |
 |
The only parameter determining AC construction is a penalty. The deeper AC is in the hierarchy, the bigger the minimum amount of triangles it can store. Therefore the total amount of AC will change. However, it doesn't have much impact on performance.
Model above containes 250'000 triangles. Without usage of AC render time was 356 seconds. With AC - only 6 seconds.
Mesh consists of polygons (triangles), and if we will draw them as they are we will receive an image that doesn't look nice. To fix it, we may use shaders. The most basic one will smoothen the surface by extrapolating the normal triangle vertices.
| Flat shading | Vertex shading |
|---|---|
 |
 |
The plain object is not very interesting and useful, so we can use texture maps to fix it. A texture map (sometimes called diffuse map) is an image storing information about objects' color. We can get them from texture coordinates, which are associated with each triangle. Also, those coordinates are normalized (from 0 to 1), therefore texture itself can have any size. The bigger the size - the better the quality.
| Texture file | Render without texture | Render with texture |
|---|---|---|
 |
 |
 |
Another tecnique similar to texture map is normal map. It can add to object more small details, without increasing the complexity of geometry. To use the tangent normal map we have to calculate tangent and bitangent for each triangle, and each time we'll need a normal we will transform the vector from the map into world space. In each pixel of such a map 3d vector is encoded, which shows direction of normal in tangent space.
Following 2 images show normal view of object, which means that color of surface shows direction of normal in world space. In upper image we can see that object is smooth, while on picture below surface has much more details in it. It is the effect of normal map.
We can add one more map to the object, which is specular map. This map is used for Phong shaded objects and can determine how reflective surface will be.
All 3 maps of the following model:
| Texture (diffuse) map | Normal map | Specular map |
|---|---|---|
 |
 |
 |
And with those 3 image we managed to enhance view of our model without significant performance loss.
The area light is the thing that can make a scene look much more plausible, but it also makes it much slower. In this engine, every area light source is parallelogram defined by its center position and sides vectors. Light quality is described by the number of samples per side of the parallelogram. So, the bigger the source - the more samples should be used and slower it will run.
| Original model | Low resolution of light source |
|---|---|
 |
 |
| Small light source | Large light source |
 |
 |
Also, if you are additionally interested in code and wish to expore it more, output folder has the call tree generated by Doxygen