Thanks for watching! ❤️ Who else is super excited for this series? I’ve left some resources and extra info for you to check out in the description box. To brush up on your math, I highly recommend you take a look at Brilliant! I deliberately chose them as the sponsor for this series because they’ve got so many relevant courses and they’re really well made and engaging; visit brilliant.org/TheCherno to get started learning STEM for free, and the first 200 people will get 20% off their annual premium subscription.
I'll offer my tidbit here in case it's useful for the series, you can use the original 2d cell ray tracing thing on 3d cells if you split the 2 angles into their own normalised x/y axis first then multiply the 2 y axis against each other to get the actual y destination point, then the x axis for one angle's result is to be treated as the z axis, from there the usual whichever is lower (assuming I remembered that right) should be usable on the 3 values, plan to do my own experiments with it as soon as I get my instanced triangles on screen with just the uniforms I'm sending the GPU (all my vertices are set to 0 to eliminate them as a variable). **Edit:** I would convert 3d non-cellular scenes to cells with on the fly arrays 9 with pre-allocated memory for the cell I would work with, do a spiral fill of the max objects I'll process (anything outside the range will just get drawn normally as they'll be using low resolution textures), filling each cell's array with a list of objects that fall into said cell, then simply decided what to do non-cellular ray tracing on based on what cells are caught from the cellular ray tracing.
I already started my own copy of the code to learn this! I'm very excited! ray tracing rendering is something I always wanted to try, but the amount of boilerplate and complexity to even show something simple on screen always kept me back, I'm really glad you did awesome by providing us a workable template. Thank you!
For naming, I like "Halide". Silver halides are the chemicals used in analog film photography which capture the light on the film. It doesn't quite fit into the nut-based naming scheme, but it's a vague riff off the word Hazel.
random fact: in brazil, whenever we read "excited" it immediately brings "sexual excitement" to mind, because that's the only meaning of this word over here 🕺💃 ( "i am excited" ("eu estou excitado") is interpreted by all brazilians as "i have a boner")
Cherno, I really love what you've been doing. You somehow manage to be extremely clear in your explanations while also being quite concise. Now if only someone would cover compiler writing in the same way :)
For anyone confused at 17:56 the reason we store it seemingly backwards is because of endianess. Modern computers store data in little endian, meaning that the low bits, or the last digits we write will be stored first, effectively flipping it in memory. I would highly recommend anyone to play around with this concept
Been waiting for a series like this! A colleague mentioned Path Tracing to me a few days ago but I felt it was too complex to jump into. This will be a great start :)
Hello Cherno. You're making very interesting and useful videos. What series I mostly want to continue is the Game Engine Series.I really miss that series.I hope you will continue with that because you're doing a great job.Thank you for these wonderful tutorials
Maybe he will continue this series but in complete different format, because the more the engine grows, the more things are added, the more difficult it becomes to tell and the more to make a video and eventually it just becomes impossible. Jan seemed to say on the stream that in December or January he would do mono integration for C# scripting, but this did not happen. Then I started implementing scripting for my engine from scratch, I've never worked with something like this at all. It took me about 3 months, of course, in my free time from studying, to integrate Mono and scripting, and now there are bugs with some components, especially with physics. So here I understand Jan)
i found the second edition of physically based rendering just last night in my friends apartment and bought it home with me! a quick skim by itself made my head spin but im really excited to scratch the surface this summer
Hello, Cherno. Thanks for the series, I love your videos lot! Can you create a lesson about hybrid rendering and how to use ray trasing and rasterization at the same time for example about bvh tree, and how to work with it, because I think this structure also can help solve collision detection problem?
This is perfect!! I'm already about 35% through the RT in a weekend tutorial, taking my time with it to understand exactly what's going on and make subtle changes.
I know you said you wont reveal any more secrets in the video, but are there any plans on taking advantage of constexpr/consteval for something like creating shader tables or something similar at compile time? I've been messing around with compile time stuff recently, but only for some small const array population; if you plan on using those features I will be absolutely stoked lol I've been struggling with their usage in templates and could gain to glean some insight from ya lmao Anyways, super stoked for this new series and as always, thank you for the time you spend on putting these videos together!!
I just worked trough the raytracing in one weekend series. Perfect timing. I really didn't know how to make it faster/run on the gpu. Totally hyped for this series. 👍
@@yuppieyup8188 yes. Took some time though because i only have a laptop and it's not the best. I finished the second course too. Just had some problems with the third.
ok... this is sick. thanks for making this series. I've always wanted to get into computer graphics but was scared and didn't really know where to start/how.
Dear IMGui and GLFW, YES! I was about to start learning these, please do not skip aaany of the tiny tiny details :) I am hungry not only for basics how to use, how to start with, but for variety of use cases, traps, patterns, optimizations and other real life world stuff, especially once we want to play with Vulkan which is another big YES from me! If you want to consider multi-hours long streams? Yes, please!
Hi Cherno! Thanks a lot for the Ray-tracing series. Its just something at the back of my head, I am not very clear with. At 13:54 you used a shared_ptr. I wonder why and why not a unique_ptr?
I made a project, prepared everything I needed, and in the end I realized that in the entire series there is no way to run this on a video card or, especially, to render objects consisting of polygons... And what kind of "Walnut" is this? I didn’t find any documentation or anything to explain work with shaders, maybe i need to work with the Vulkan... I dont know. But if the videos are called "Ray Tracing", it must be performed on the video card, at least in a regular fragment shader!... Maybe someone in the comments can help?
Hey great idea for a series, thank you! However, is it possible to get an introduction to wallnut? I would have loved for such a series to really feel like it's from scratch, so that we can really understand everything that's happening. Thank you for considering it ;)
Not the first of your videos I watched, but this one got me excited and prompted to subscribe. Gonna follow with a Qt application at first, at least for the CPU part, already set up the skeleton project!
Well I'm not really a graphics/rendering guy, more of a hardware guy actually, but I think the series will be very interesting. Also I think it was by far the best sponsor section I have seen done by him up until now :D
Many many thanks. I recently started (again) on the Raytracing In One Weekend CUDA version, and I've been trying to figure how to integrate IMGUI, etc., so this is great timing (since CUDA was giving me a headache). BTW, I cloned the code and it works perfectly, and I've been tweaking the Application.cpp "Select GPU" section to allow me to select either of my 2 GPU's (GTX1080ti and RTX2070Super) using VkPhysicalDevice. FWIW my render time for the random image is about twice yours (10mSec vs. your 5mSec), no matter which GPU I chose. EDIT: Oh, wait...I forgot that it depends on the size of the window/image you're rendering. DOH!!! Just made it a bit smaller and got 5mSec. Anyway, thanks again.
I'm quite excited to go through this series! I'm honestly still a newb here but I love content. I'm a year two CS student and these series are just so insanely interesting!
How about BunyaNut for the RT section of Hazel? Bunya trees kinda have a lot of straight branches, like rays, from the central trunk and matches the nut theme with some Aussie flavour.
I remember I made a ray tracer in pure javascript with coloring points in canvas. I learned how we see things, how light works etc. There were cubes and spheres, I made mirrors and glass.
Question: The 'Ray tracer in one weekend' series, end up creating a static ray tracer - not a real time one, is that correct? In your approach you will create a completely real time, dynamic one?
Mate you HAVE to do a reaction video on the unreal engine 5 train station video, it’s a serious game changer, the best anyone has seen up to now, please, it’s terrifyingly real.
Hi TheCherno, I discovered your series and love it! I've been writing a Ray Tracer in Java for the past few years, just as a little pet project. I'm struggling with optimization though, my latest barebones raytracer attempt is hitting ~600ms render times for a 1000x1000 image with one sphere and nothing else. Is this just Java being weighty? or is there a way to get into the tens-of-milliseconds render times using Java?
Ligatures in programming, in my opinion may ruin readability sometimes. Interestingly, you have != convert into the symbol for not equals, but -> isn't converted into a right arrow symbol.
I dont remember if in the code review or other raytracers you saw but most likely a lot didnt use accelerations structures like octrees or ray direction grouping
sorry for being a noob about all of this include and dependencies thing. despite installing vulkan sdk, when i run walnut.sln and try to build it it cant find vulkan header. what should i do?
You basically wrote a shader rendering program on CPU, try rendering mandelbrot set in the next video as it's shader code is quite simple and makes for a cool thumbnail
Since one of my questions was answered by others, quoting my comment to make sure that you ( @The Cherno ) won't miss it. Thank you so much for your videos. Nice new topic. One comment and one question. 1. “The RayTracing in one weekend” book is a little bit shallow and short. And the “Physically Based Rendering” book could be on the contrary is over complicated for beginners. I would recommend consider the ”Ray Tracing from the Ground Up” by Suffern, Kevin, which is the best for such start-ups. 2. Do you plan to cover the most exciting and hard part which is hardware support for RayTracing like in DXR which is covered in the “Ray Tracing Gems High-Quality and Real-Time Rendering with DXR and Other APIs” by Eric Haines, Tomas Akenine-Möller?
22:43 maybe i got something wrong but as of the logic on line 42 the actual render code gonna be run only once unless the viewport size changes or m_Image become null. but on your video its rendering every frame even when you click the render button after a complete render without changing the viewport size. can some help me understand this?
Line 42-47 is only used to create the m_Image & m_ImageData array. If the size of the screen (aka the size of the array) doesn't change then we can use the existing one (we don't need to delete a re-create it) as it is stored as a private field. It is lines 46-50 that change the data in the array, if the line 42 condition isn't met then it will be updating the existing array, then line 52 sets the m_Image data to m_ImageData. Think of it like a bottle of water, if I always need the same amount of water, I can just reuse the same bottle over and over again, it's only when the amount of water (aka screen size) changes that I'd need to get a new bottle.
@@TheGubble Thank you so much, now I know what I did wrong. I put the loop which fills the m_ImageData var inside the condition which caused it to only render when I change viewport size. Fixed it and now it working flawlessly :)
I started doing my raytracer once & got axed by pulling my hair out over how to implement the function to rotate around the object's z coordinate - Blender style. So random :) But then I got other things to take care of. Well, maybe this series will make me return to my project and conquer my obstacles ))
Thanks for watching! ❤️ Who else is super excited for this series? I’ve left some resources and extra info for you to check out in the description box. To brush up on your math, I highly recommend you take a look at Brilliant! I deliberately chose them as the sponsor for this series because they’ve got so many relevant courses and they’re really well made and engaging; visit brilliant.org/TheCherno to get started learning STEM for free, and the first 200 people will get 20% off their annual premium subscription.
;)
I'll offer my tidbit here in case it's useful for the series, you can use the original 2d cell ray tracing thing on 3d cells if you split the 2 angles into their own normalised x/y axis first then multiply the 2 y axis against each other to get the actual y destination point, then the x axis for one angle's result is to be treated as the z axis, from there the usual whichever is lower (assuming I remembered that right) should be usable on the 3 values, plan to do my own experiments with it as soon as I get my instanced triangles on screen with just the uniforms I'm sending the GPU (all my vertices are set to 0 to eliminate them as a variable).
**Edit:** I would convert 3d non-cellular scenes to cells with on the fly arrays 9 with pre-allocated memory for the cell I would work with, do a spiral fill of the max objects I'll process (anything outside the range will just get drawn normally as they'll be using low resolution textures), filling each cell's array with a list of objects that fall into said cell, then simply decided what to do non-cellular ray tracing on based on what cells are caught from the cellular ray tracing.
Hey Cherno! please, enable the "Thanks" button, just below the video, for us to "pay a cup of coffee"! 😀☕
I already started my own copy of the code to learn this! I'm very excited! ray tracing rendering is something I always wanted to try, but the amount of boilerplate and complexity to even show something simple on screen always kept me back, I'm really glad you did awesome by providing us a workable template. Thank you!
For naming, I like "Halide". Silver halides are the chemicals used in analog film photography which capture the light on the film. It doesn't quite fit into the nut-based naming scheme, but it's a vague riff off the word Hazel.
@@RandomUser2401 Nut Tracing
@@RandomUser2401 as opposed to nut traces
So excited for the series. Was just trying to learn ray tracing!
random fact: in brazil, whenever we read "excited" it immediately brings "sexual excitement" to mind, because that's the only meaning of this word over here 🕺💃 ( "i am excited" ("eu estou excitado") is interpreted by all brazilians as "i have a boner")
Such an amazing timing for me as i was looking for something like this to start in the next couple of days.. thank you so much
Cherno, I really love what you've been doing. You somehow manage to be extremely clear in your explanations while also being quite concise. Now if only someone would cover compiler writing in the same way :)
who knew math was good for game dev lmfao
I use Brilliant on the daily, highly recommend
True story, saw you mention Brilliant (being brilliant) in yesterday's changelog. Hope that linear algebra is going well!
@@altblock + Discrete Mathematics
computers do math, so yeah.
@@anders5611 understanding something is also crucial for later ideas and implementations
Wonderful, as always.
Signed up for Brilliant - it really is, thanks!
Great timing, just wanted to learn ray tracing im excited for this series
+1 haha
For anyone confused at 17:56 the reason we store it seemingly backwards is because of endianess. Modern computers store data in little endian, meaning that the low bits, or the last digits we write will be stored first, effectively flipping it in memory. I would highly recommend anyone to play around with this concept
whoa I did not expect a raytracing video having not a single word about raytracing :)
Thanks for doing this, just set it up and rendered my sweet noise, looking forward to see the progress!
Been waiting for a series like this! A colleague mentioned Path Tracing to me a few days ago but I felt it was too complex to jump into. This will be a great start :)
Hello Cherno. You're making very interesting and useful videos. What series I mostly want to continue is the Game Engine Series.I really miss that series.I hope you will continue with that because you're doing a great job.Thank you for these wonderful tutorials
Maybe he will continue this series but in complete different format, because the more the engine grows, the more things are added, the more difficult it becomes to tell and the more to make a video and eventually it just becomes impossible. Jan seemed to say on the stream that in December or January he would do mono integration for C# scripting, but this did not happen. Then I started implementing scripting for my engine from scratch, I've never worked with something like this at all. It took me about 3 months, of course, in my free time from studying, to integrate Mono and scripting, and now there are bugs with some components, especially with physics. So here I understand Jan)
for some odd reason TH-cam didn't notify me bruh , I AM LOOKING FORWARD TO THIS SERIES SOO MUCH
i found the second edition of physically based rendering just last night in my friends apartment and bought it home with me! a quick skim by itself made my head spin but im really excited to scratch the surface this summer
Always when I start learning something and I am struggling, TheCherno comes to save the day :D
Loved this series! Can't wait the next video. Kudos!
Hello, Cherno. Thanks for the series, I love your videos lot! Can you create a lesson about hybrid rendering and how to use ray trasing and rasterization at the same time for example about bvh tree, and how to work with it, because I think this structure also can help solve collision detection problem?
This is perfect!! I'm already about 35% through the RT in a weekend tutorial, taking my time with it to understand exactly what's going on and make subtle changes.
Ray tracing was the reason I learn programming! Thanks Cherno!
Me too!
funny to find you here too :)
I know you said you wont reveal any more secrets in the video, but are there any plans on taking advantage of constexpr/consteval for something like creating shader tables or something similar at compile time? I've been messing around with compile time stuff recently, but only for some small const array population; if you plan on using those features I will be absolutely stoked lol I've been struggling with their usage in templates and could gain to glean some insight from ya lmao
Anyways, super stoked for this new series and as always, thank you for the time you spend on putting these videos together!!
heck yeah! i've been waiting for this for a while. nice to see you finally do it :)
this is much more than a series on RayTracing. Can't wait for the next episodes :D
I just worked trough the raytracing in one weekend series. Perfect timing. I really didn't know how to make it faster/run on the gpu. Totally hyped for this series. 👍
Hey, were you able to generate the image shown on the cover of Raytracing in the weekend first course?
@@yuppieyup8188 yes. Took some time though because i only have a laptop and it's not the best. I finished the second course too. Just had some problems with the third.
I'm really excited Cherno! Good luck 👍👍
ok... this is sick. thanks for making this series. I've always wanted to get into computer graphics but was scared and didn't really know where to start/how.
Fantastic! I have been waiting for this series for years!
Dear IMGui and GLFW, YES! I was about to start learning these, please do not skip aaany of the tiny tiny details :) I am hungry not only for basics how to use, how to start with, but for variety of use cases, traps, patterns, optimizations and other real life world stuff, especially once we want to play with Vulkan which is another big YES from me! If you want to consider multi-hours long streams? Yes, please!
Oh boii does this series come at the right time! I'm really hyped!
Keep it going man, I wondering if there is a nice and motivated guy like you in TH-cam!
Hi Cherno! Thanks a lot for the Ray-tracing series.
Its just something at the back of my head, I am not very clear with. At 13:54 you used a shared_ptr. I wonder why and why not a unique_ptr?
I made a project, prepared everything I needed, and in the end I realized that in the entire series there is no way to run this on a video card or, especially, to render objects consisting of polygons... And what kind of "Walnut" is this? I didn’t find any documentation or anything to explain work with shaders, maybe i need to work with the Vulkan... I dont know.
But if the videos are called "Ray Tracing", it must be performed on the video card, at least in a regular fragment shader!... Maybe someone in the comments can help?
good video man! looking forward to this one for sure. walnut seems very interesting too... love the imgui docking branch :)
I’ve been waiting for this series, thanks 🙏
You could name it "TRACENUT"
Hey great idea for a series, thank you! However, is it possible to get an introduction to wallnut? I would have loved for such a series to really feel like it's from scratch, so that we can really understand everything that's happening. Thank you for considering it ;)
I think naming it "Macadamia" or maybe "MacadamiaRT" would be a pretty cool name!
So happy to finally see this series. Do you guys know any good material to learn vulkan or is it ok just with opengl knowledge!?
How don't you have 1 trillion views? Your content is incredible.
Not the first of your videos I watched, but this one got me excited and prompted to subscribe. Gonna follow with a Qt application at first, at least for the CPU part, already set up the skeleton project!
So excited for this series :) is there any vs theme you use? Or is it like really customized? I really like the colors
It comes with Visual Assist which costs money
@@masterjj1 F, thanks!
I have already complete this 1st book but i like the way you explained, keep it up.
Well I'm not really a graphics/rendering guy, more of a hardware guy actually, but I think the series will be very interesting. Also I think it was by far the best sponsor section I have seen done by him up until now :D
that sponsor integration was super smooth. it makes perfect sense here too
Many many thanks. I recently started (again) on the Raytracing In One Weekend CUDA version, and I've been trying to figure how to integrate IMGUI, etc., so this is great timing (since CUDA was giving me a headache). BTW, I cloned the code and it works perfectly, and I've been tweaking the Application.cpp "Select GPU" section to allow me to select either of my 2 GPU's (GTX1080ti and RTX2070Super) using VkPhysicalDevice. FWIW my render time for the random image is about twice yours (10mSec vs. your 5mSec), no matter which GPU I chose. EDIT: Oh, wait...I forgot that it depends on the size of the window/image you're rendering. DOH!!! Just made it a bit smaller and got 5mSec. Anyway, thanks again.
Can't wait for the next videos!!
I’m not great at math or am I a game dev but I watch these videos every time they drop and watch them in it’s entirety.
I'm quite excited to go through this series! I'm honestly still a newb here but I love content.
I'm a year two CS student and these series are just so insanely interesting!
I am so excited for this series and thank you for giving references to these resources it will be very helpful
How about BunyaNut for the RT section of Hazel? Bunya trees kinda have a lot of straight branches, like rays, from the central trunk and matches the nut theme with some Aussie flavour.
I remember I made a ray tracer in pure javascript with coloring points in canvas. I learned how we see things, how light works etc. There were cubes and spheres, I made mirrors and glass.
ha, yea. I prototyped my first one in JS. Boy that was slow.
Question: The 'Ray tracer in one weekend' series, end up creating a static ray tracer - not a real time one, is that correct? In your approach you will create a completely real time, dynamic one?
Can't wait for the episode 2, hurry pls 😜
Mate you HAVE to do a reaction video on the unreal engine 5 train station video, it’s a serious game changer, the best anyone has seen up to now, please, it’s terrifyingly real.
Awesome video mate. Any update on when the next one is coming out? Love your content. :)
This is so exciting! Great work!
Another awesome series thanks Cherno, you rocks
Very much excited to learn this ❤️😇❤️. Thank you cherno master!
Oooh a new series, imma tune in
Hell yeah it's about time Ray Tracing In One Weekend got the limelight!
I'm not even interested in the graphics side of programming, but still somehow interested in this series.
This series is going to be so cool!
This is awesome ! Really interested !
really excited!
Hi TheCherno, I discovered your series and love it!
I've been writing a Ray Tracer in Java for the past few years, just as a little pet project.
I'm struggling with optimization though, my latest barebones raytracer attempt is hitting ~600ms render times for a 1000x1000 image with one sphere and nothing else.
Is this just Java being weighty? or is there a way to get into the tens-of-milliseconds render times using Java?
Super excited for this series
Ligatures in programming, in my opinion may ruin readability sometimes. Interestingly, you have != convert into the symbol for not equals, but -> isn't converted into a right arrow symbol.
This was highly motivating. Looking forward to the new ray tracing videos.
Considering is ray tracing and the sun sends out a tonne of rays, and sunflower seeds are considered to be nuts...
"Sunflower" might be a nice name.
"RayNutter" is obviously the only acceptable name.
"I'm not sponsored by this book. I just really like it"
I laughed so hard for no reason on this 😂
Thanks for your work man :)
Name suggestions:
- RailNut
- AllYouHadToDoWasToFollowTheF*ckingRayCJ
I dont remember if in the code review or other raytracers you saw but most likely a lot didnt use accelerations structures like octrees or ray direction grouping
Call it Dietznut
Dietz Nuts have two meanings - A fanatic of a particular brand of lanterns, and a brand of sausage bites.
Please make a video on recommend books on modern CPP?
Hi @Cherno, thanks for all the videos. Please enable the Thanks button.
sorry for being a noob about all of this include and dependencies thing.
despite installing vulkan sdk, when i run walnut.sln and try to build it it cant find vulkan header. what should i do?
Spasibo Cherno
you should call it 3DzNuts
You basically wrote a shader rendering program on CPU, try rendering mandelbrot set in the next video as it's shader code is quite simple and makes for a cool thumbnail
My engine isn't anywhere near ray tracing, but I'm still gonna watch this
Thank you so much for sharing!!
We are still waiting :)
My dream of measuring exactly how much slower my computer is then Cherno's is finally realized!
Can i do this with a MacBook 2020 pro?
Cheers Cherno for the great video!!
very excited for this series 🌹
"Why don't we do it every frame"
** Video codec exited the chat **
How about calling it Tigernut? They're hard and sweet. Tiger nuts, water, and a little cinnamon make an excellent horchata.
Amazing new series!
Since one of my questions was answered by others, quoting my comment to make sure that you ( @The Cherno ) won't miss it.
Thank you so much for your videos. Nice new topic. One comment and one question.
1. “The RayTracing in one weekend” book is a little bit shallow and short. And the “Physically Based Rendering” book could be on the contrary is over complicated for beginners. I would recommend consider the ”Ray Tracing from the Ground Up” by Suffern, Kevin, which is the best for such start-ups.
2. Do you plan to cover the most exciting and hard part which is hardware support for RayTracing like in DXR which is covered in the “Ray Tracing Gems High-Quality and Real-Time Rendering with DXR and Other APIs” by Eric Haines, Tomas Akenine-Möller?
22:43 maybe i got something wrong but as of the logic on line 42 the actual render code gonna be run only once unless the viewport size changes or m_Image become null. but on your video its rendering every frame even when you click the render button after a complete render without changing the viewport size. can some help me understand this?
Line 42-47 is only used to create the m_Image & m_ImageData array. If the size of the screen (aka the size of the array) doesn't change then we can use the existing one (we don't need to delete a re-create it) as it is stored as a private field.
It is lines 46-50 that change the data in the array, if the line 42 condition isn't met then it will be updating the existing array, then line 52 sets the m_Image data to m_ImageData.
Think of it like a bottle of water, if I always need the same amount of water, I can just reuse the same bottle over and over again, it's only when the amount of water (aka screen size) changes that I'd need to get a new bottle.
@@TheGubble Thank you so much, now I know what I did wrong. I put the loop which fills the m_ImageData var inside the condition which caused it to only render when I change viewport size. Fixed it and now it working flawlessly :)
The one we have been waiting for!
Finally, this is what I have been waiting for.
Awesome! Just wanted to start learning computer graphics!
My god it's gonna be a fun series isn't it
I started doing my raytracer once & got axed by pulling my hair out over how to implement the function to rotate around the object's z coordinate - Blender style. So random :) But then I got other things to take care of. Well, maybe this series will make me return to my project and conquer my obstacles ))
Will you ever complete the LAPSIS series? We have been waiting for 8 years. Give us Episode 9.