RaytracerGO/README.md

96 lines
8.1 KiB
Markdown
Raw Normal View History

2024-01-25 08:12:45 +00:00
# RaytracerGO
2024-01-25 09:08:24 +00:00
A raytracer and renderer writen in Go (Golang) following the book [Raytracing in one weekend](https://raytracing.github.io/books/RayTracingInOneWeekend.html#overview)
2024-01-25 08:39:51 +00:00
2024-01-25 08:40:22 +00:00
## Motivation
2024-01-25 08:39:51 +00:00
I've been meaning to tinker with graphics for quite a while and was motivated by a video programming a raytracing algorithm on a TI-84. Back in my school days I used to love to tinker with the TI-84 and also did some very elementary programming on it myself.
2024-01-25 09:08:24 +00:00
Video that started it all:
[Raytracing on a Graphing Calculator (again)](https://youtu.be/rY413t5fArw)
2024-01-25 08:46:19 +00:00
2024-01-25 09:15:02 +00:00
<img src="https://www.techeblog.com/wp-content/uploads/2022/12/ray-tracing-ti-84-plus-ce-graphing-calculator.jpg" alt="TI-84 Raytracing" width="720"/>
2024-01-25 08:39:51 +00:00
2024-01-25 09:08:24 +00:00
## Why Go?
The story starts with Zig. A few colleagues of mine and I tried to work on a Guake-like browser using Zig. We chose Zig because it's C-like, modern and because their mascot is a lizard, of course. But I don't like Zig all that much, and right now Go has caught my attention.
2024-01-25 09:11:07 +00:00
I like the language a lot, it's still very C-like, doesn't have classes :), is open-source and resembles Python a lot, while still being fast and having crazy fast compiling speeds (which is something I've started to appreciate since dabbling with Linux From Scratch). The only draw back of Go is that it is a little bit slower than C++, but I just want to experience what the Python-version of C is like :)
2024-01-25 09:19:50 +00:00
<img src="https://external-content.duckduckgo.com/iu/?u=https%3A%2F%2Fprogramaenlinea.net%2Fwp-content%2Fuploads%2F2020%2F04%2Fgolang-1024x516.png&f=1&nofb=1&ipt=363a10979aa43c8925c481b76c8a2b03a50ce948b3548b40a29432caf8a534d1&ipo=images" alt="Go-Programming" width="720"/>
## Taglibro
2024-01-25 09:20:22 +00:00
### Chapter 1: The PPM-image format
2024-01-25 09:19:50 +00:00
2024-01-25 19:47:28 +00:00
<img src="https://raytracing.github.io/images/img-1.01-first-ppm-image.png" alt="First PPM image" width="480"/>
2024-01-26 16:57:14 +00:00
Yay this is the first image I've ever generated without using any external imported library ^^
2024-01-26 17:55:10 +00:00
### Chapter 2: Vector operations: Ditching OOP for GO
2024-02-03 22:01:58 +00:00
Implemented the vec3 Class and colour utility functions without classes. Struktoj estas sufiĉa.
### Chapter 3: Implementing the camera, rays and a background
To understand computer graphics better I will try to describe some important definitions with my own words:
- Rays: A ray is a 3D-vector with an origin pointing with some length in one direction (P(x)=O+x*b, where O is the origin and b is a vector pointing in one direction)
- Viewport: Is essentially a window (typically the user window) through which we see the 3D environment. Adjusting the viewport allows you to zoom in, pan around, or focus on specific areas of your scene.
- Camera: Is essentially a mathematical function (a virtual eye of sorts) that captures rays that originate from its position and pass through the viewport and generates an image that the user can see.
By the end of this chapter I generated the following background:
2024-02-03 22:02:22 +00:00
2024-02-27 13:10:04 +00:00
<img src="https://raytracing.github.io/images/img-1.02-blue-to-white.png" alt="Second PPM image" width="480"/>
2024-02-10 17:44:32 +00:00
### Chapter 4: Creating a sphere
In this chapter I created a simple sphere and detect its surface by solving quadratic equations, which represent vectors. The sphere has no shading yet:
2024-02-27 13:10:04 +00:00
<img src="https://raytracing.github.io/images/img-1.03-red-sphere.png" alt="Second PPM image" width="480"/>
2024-02-12 12:28:07 +00:00
### Chapter 5: Surface normals
The first part of the chapter was the calculation and visualization of the normals, which we need for shading. But I also implemented the [fast inverse square algorithm](https://youtu.be/p8u_k2LIZyo) in Go just like in Quake III, which is pretty clever and fast. I did primarily because 1) I'm working with 32-bit floats for the sake of memory efficiency and 2) I don't care about accuracy - also it's very educational. But [as explained in this video](https://youtu.be/tmb6bLbxd08) the fast inverse square isn't always the better choice and in my case it probably isn't, because I need to import a Go standard library to disable data type safety and processor padding (something I've noticed when working with small data types in Zig). This is the first visualization of the normals of the sphere:
2024-02-27 13:10:04 +00:00
<img src="https://raytracing.github.io/images/img-1.04-normals-sphere.png" alt="Second PPM image" width="480"/>
2024-02-27 13:05:04 +00:00
The second part of the capter involved standardizing the code so that it can process multiple objects - it was quite translating this part into Go, as a lot of C++ OOP features are missing - but finally I managed to produce this neat output:
2024-02-27 18:03:05 +00:00
<img src="https://raytracing.github.io/images/img-1.05-normals-sphere-ground.png" alt="Second PPM image" width="480"/>
2024-02-27 20:19:49 +00:00
At the end I also added an intervals struct, to further simplify the code.
### Chapter 6: The Camera struct
This chapter was yet another simplification of the existing code - the viewport and the camera were moved out of main and got their own struct. The camera struct and the render function have two tasks:
1) Construct and dispatch rays into the world and
2024-02-28 14:30:44 +00:00
2) Use the results of these rays to construct the rendered image
### Chapter 7: Anti-Aliasing
The images rendered thus far have jagged edges and this is known as aliasing. To soften the edges each pixel gets sampled multiple times and the colour gets averaged. I've spend quite some time on this chapter due to a veeeery small bug in the code. This chapter produces a similar but softer image as before. Here an comparison:
<img src="https://raytracing.github.io/images/img-1.06-antialias-before-after.png" alt="Second PPM image" width="480"/>
2024-02-28 14:32:13 +00:00
2024-02-28 21:34:16 +00:00
This is also the first time the code starts to take some time to execute.
### Chapter 8: Diffuse objects
A diffuse object is any object that is not emitting light, takes on the colours of the environment and reflects light in all directions.
2024-02-28 21:35:03 +00:00
2024-02-28 21:34:16 +00:00
<img src="https://upload.wikimedia.org/wikipedia/commons/b/bd/Lambert2.gif" width="480"/>
2024-02-29 14:10:37 +00:00
I generated random reflection vectors and got the following (this is the first time a shadow can be observed, left one is mine, right one from the book - note the stripe is probably a consequence of fast inverse square and of using 32-bit floats instead of 64-bit ones):
2024-02-28 21:34:16 +00:00
<img src="https://media.discordapp.net/attachments/929667122404155445/1212496739668598875/image.png?ex=65f20c95&is=65df9795&hm=d8db91eee8a0f62250c1c64628e7d214aa39c504b94ffa13a554335addfb0905&=&format=webp&quality=lossless&width=1148&height=655" width="480"/><img src="https://raytracing.github.io/images/img-1.07-first-diffuse.png" width="480"/>
2024-02-29 13:05:49 +00:00
A problem that occurs on this image is the **shadow acne** problem: A ray will attempt to accurately calculate the intersection point when it intersects with a surface. Unfortunately for us, this calculation is susceptible to floating point rounding errors which can cause the intersection point to be ever so slightly off. This means that the origin of the next ray, the ray that is randomly scattered off of the surface, is unlikely to be perfectly flush with the surface. It might be just above the surface. It might be just below the surface. If the ray's origin is just below the surface then it could intersect with that surface again. Which means that it will find the nearest surface at t=0.00000001 or whatever floating point approximation the hit function gives us. The simple fix yields this image:
2024-02-29 14:10:37 +00:00
<img src="https://raytracing.github.io/images/img-1.09-no-acne.png" width="480"/>
To make the shadows look more realistic, I had to implement the Lambertian reflections: basically, most of the reflected rays will be close to the sphere normal and the probability density is dependent on cos(phi), where phi is the angle from the normal. It was very easy to implement and yields the following:
2024-02-29 14:23:45 +00:00
<img src="https://raytracing.github.io/images/img-1.10-correct-lambertian.png" width="480"/>
The last issue left in the chapter is the darkness of the image and it's due to some strange linear-gamma space conversion? I don't quite understand how that works, but by taking the square root of the colour values we get the right brightness. Nice
<img src="https://media.discordapp.net/attachments/874752364698013736/1212767017711697950/image.png?ex=65f3084d&is=65e0934d&hm=b8eabd56619cff0984e361c4917b9f63b7d7e3a76e28dbc666c7d91f9f6331de&=&format=webp&quality=lossless&width=720&height=405" width="480"/>