raytracing.github.io icon indicating copy to clipboard operation
raytracing.github.io copied to clipboard

Main Web Site (Online Books)

Results 175 raytracing.github.io issues
Sort by recently updated
recently updated
newest added

![image](https://user-images.githubusercontent.com/10294860/183796145-bf5b4fd4-a7b7-4cf8-a2ad-33cb6db5906f.png) I don`t know the code come from where, can you tell me the theory? Or paste a link? thanks

A _LOT_ of small touches to the first half of book 1. A couple of _big_ touches to chapter 8 of book 1 There are many issues which I documented...

Book 3 includes a modification to the `scene::render()` function to include stratified sampling inside pixels. The source code, however, does not reflect this change.

area: code
book 3: Your Life

The single letter variable is confused with the desired `s`/`t` image coordinate parameters.

status: in PR
camera

As the title says, wouldn't biasing rays towards a light in places located in the shadow of that light significantly increase the variance there, to the point it would need...

book 3: Your Life

The current code leaves the "scanlines" remaining message up with a count of one, and then prints "Done" on a subsequent line. Instead, have the "Done" line replace the "scanlines...

camera

The `camera` class is moderately complex, with lots of member and intermediate variables. Member variables `u, v, w` could use a comment indicating what they are and that they're unit...

camera

I'm not quite sure how the current equation was derived. But the case clearly fails for the case that the width and height are both equal to one, for example....

level: patch
camera

Currently the `camera::get_ray()` function performs depth-of-field lens jittering, and the `scene::render()` loops perform the pixel sample jittering. Both of these should be done in the `camera::get_ray()` function.

status: in progress
camera

Thus, arguments (0,0) should refer to the upper left pixel, and (1,1) should refer to the lower right pixel.

camera