zig-rtweekend

Following along with "Ray Tracing in One Weekend" (https://raytracing.github.io) in Zig. Mostly an exericise in learning Zig.

A key difference is that while the original code C++ code avoided templates completely, I am trying to make all functions generic. The code might not be particularly idiomatic due to the more-or-less direct translation from C++, but I have tried to look up and come up with programming patterns better suited for Zig. I now see why people complain about C++ templates being Turing complete. Infinite recursion was messing things up, so keeping all structs concrete till I figure out/ read about a different architecture.

Progress

Diffuse Materials

Ray Tracing in One Weekend

1. Overview
2. Output an Image
3. The vec3 class
4. Rays, a Simple Camera, and Background
5. Adding a Sphere
6. Surface normals and Multiple Objects
7. Antialiasing
8. Diffuse Materials
9. Metal
10. Dielectrics
11. Positionable Camera
12. Defocus Blur
13. Final Render

Ray Tracing: The Next Week

1. Overview
2. Motion Blur
3. BVH
4. Solid Textures
5. Perlin Noise
6. Image Texture Mapping
7. Rectangles and Lights
8. Instances
9. Volumes
10. A Scene Testing All New Features

Ray Tracing: The Rest of Your Life

1. Overview
2. A Simple Monte Carlo Program
3. 1D MC Integration
4. MC Integrations on the Sphere of Directions
5. Light Scattering
6. Importance of Sampling Materials
7. Generating Random Directions
8. Orthonormal Bases
9. Sampling Lights Directly
10. Mixture Densities
11. Some Architectural Decisions
12. Cleaning up PDF Management
13. The Rest of Your LIfe

TODO

• Try different polymorphism patterns: see this showtime. Specifically, it would be nicer to do const s1 = Sphere { ... }; const s1_h = s1.hittable(); instead of the make thing that we have going on right now
• Parallelize
  • Load-balancing
• GPU Acceleration? See Mach engine and Zig gamedev scene in general for inspiration maybe?