I enjoyed watching this, seeing your thought processes and how they translate into Rust changes. In your YAML for transforms, I think “by:” would be a better term than “to:”, as the former sounds relative and the latter sounds absolute.
In chapter 14 - groups. I'm struggling to add the Group in the parent attribute within my shapes without giving the error "field does not implement `Copy`". Looks like I'm going to have to refactor all the code to support this 🥲 Get ready.
Thanks for the hint. Should it come to that I will deal with it, when the problem arises. Refactoring can be fun too, as it means always learning better ways to do things. I try and always such things positive.
Chapter One. The explanation of "w" is super confusing. The author says it should be 0 or 1 for vector or point. He says 2 is invalid. THEN goes on to show it getting values like -14 or -2 during multiplication on Page 8. Other times he completely drops w entirely and shows points and vectors as only 3 values.... Can anyone clarify if w should ALWAYS be 0 or 1? Thanks.
As questions about the 4x4 matrices as well as 4 dimensional vectors are coming up quite often, I decided to make a video about, why and how those are used. Currently I am hoping to have some time this week to produce such a video. But to answer your question quickly, the w component can be something different than 0 or 1 in certain situations. However those situations are not really relevant within the current raytracer implementation.
Thanks for the feedback; you are correct, i created the stripes different than what the book asked for and i thought my implementation was wrong. Thank you, it helped me a lot to understand where I was going wrong; because the stripes were getting wrong when I put them in a Cone. My github -> ViniciusSJV
this is actually ALL i was looking for ! Great Work ! :D
I enjoyed watching this, seeing your thought processes and how they translate into Rust changes.
In your YAML for transforms, I think “by:” would be a better term than “to:”, as the former sounds relative and the latter sounds absolute.
Thanks for your kind words. You might be right. I will consider this, when I start working on this again in the future.
In chapter 14 - groups. I'm struggling to add the Group in the parent attribute within my shapes without giving the error "field does not implement `Copy`".
Looks like I'm going to have to refactor all the code to support this 🥲
Get ready.
Thanks for the hint. Should it come to that I will deal with it, when the problem arises. Refactoring can be fun too, as it means always learning better ways to do things. I try and always such things positive.
@@MrJakob no pain no gain hahaha
Indeed
Chapter One. The explanation of "w" is super confusing. The author says it should be 0 or 1 for vector or point. He says 2 is invalid. THEN goes on to show it getting values like -14 or -2 during multiplication on Page 8. Other times he completely drops w entirely and shows points and vectors as only 3 values.... Can anyone clarify if w should ALWAYS be 0 or 1? Thanks.
As questions about the 4x4 matrices as well as 4 dimensional vectors are coming up quite often, I decided to make a video about, why and how those are used. Currently I am hoping to have some time this week to produce such a video. But to answer your question quickly, the w component can be something different than 0 or 1 in certain situations. However those situations are not really relevant within the current raytracer implementation.
Thanks for the feedback; you are correct, i created the stripes different than what the book asked for and i thought my implementation was wrong.
Thank you, it helped me a lot to understand where I was going wrong; because the stripes were getting wrong when I put them in a Cone.
My github -> ViniciusSJV