From 4dd3b88ce3156d8a4a85cc19a806b0099d10adb4 Mon Sep 17 00:00:00 2001 From: ktyl Date: Tue, 4 Jan 2022 21:42:35 +0000 Subject: [PATCH] start ray tracing in one weekend --- rt/weekend.md | 9 +++++++++ 1 file changed, 9 insertions(+) create mode 100644 rt/weekend.md diff --git a/rt/weekend.md b/rt/weekend.md new file mode 100644 index 0000000..e6aed0e --- /dev/null +++ b/rt/weekend.md @@ -0,0 +1,9 @@ +# Ray Tracing in One Weekend + +[The book](https://raytracing.github.io/books/RayTracingInOneWeekend.html) + +I became interested in ray tracing as an image synthesis technique some time around summer 2020. +I'd learned just the year prior about first-principles rasterization and working with graphics APIs in C++, and had found my taste for graphics programming. +On the recommendation of a friend I started working out a first-principles CPU ray tracer based on [Ray Tracing in One Weekend](https://raytracing.github.io/books/RayTracingInOneWeekend.html) (though it took longer) and started to generate my own first ray traced images. The source code for my final project is [on my GitHub](https://github.com/ktyldev/). + +The book describes a very simple sphere-based ray tracer, though there are later books in the series (available [here](https://raytracing.github.io/)) which expand on the first with forays into rendering more complex shapes, volumentrics, and camera artifacts.