From 9c29f261ef8c01134922d07b7709ab2408b4c0b0 Mon Sep 17 00:00:00 2001 From: Sanjay Salem <38601117+sanjaysalem17@users.noreply.github.com> Date: Fri, 5 Nov 2021 13:48:26 -0400 Subject: [PATCH] Update camera rays md --- docs/pathtracer/camera_rays.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/pathtracer/camera_rays.md b/docs/pathtracer/camera_rays.md index af26839..6aecd65 100644 --- a/docs/pathtracer/camera_rays.md +++ b/docs/pathtracer/camera_rays.md @@ -26,7 +26,7 @@ Implement `Camera::generate_ray`. This function should return a ray **in world s
-Note that the camera maintains camera-space-to-world space transform matrix `iview` that you will need to use in order to get the new ray back into **world space**. Note that since `iview` is a transform matrix, it contains translation, rotation, and scale factors. Be careful in how you use it on specific objects, and take a look at `lib/mat4.h` to see what functions are available for the `Mat4` object. +Note that the camera maintains camera-space-to-world space transform matrix `iview` that you will need to use in order to get the new ray back into **world space**. Note that since `iview` is a transform matrix, it contains translation, rotation, and scale factors. Be careful in how you use it on specific objects, and take a look at `lib/ray.h` and `lib/mat4.h` to see what functions are available for the `Ray` and `Mat4` objects. Once you have implemented `Pathtracer::trace_pixel`, `Rect::sample` and `Camera::generate_ray`ou should now have a camera that can shoot rays into the scene! See the **Raytracing Visualization** below to confirm this. -- GitLab