Hi, wonderful video ! Could it be possible to get the test file with the tree ? It could seem stupid but i find that the backgroung colors (light grey + light green from the tree) + "white lighting" is very attractive. I tried to do mine but i can't manage to get the same effects ! Best. Francis
Next time when comparing one image against the other, please cut directly from one to the other and don't insert black frames. With a direct transitions, small changes seem to blink, which helps spot areas of difference.
I hve a pinned comment with all images on imgur. So you can check out at your leisure. Yes the quality is worse and yes the lighting changes! That’s why I tell everyone to choose whether or not the time is worth the tradeoff in quality. I (try) to hide nothing and be transparent!
@@KaizenTutorials I'm not blaming you, it's not your fault, but rather the complexity of the problem itself. However, increasing the noise threshold this much significantly reduces the quality of the image (as can be seen in the grass in the shade) and introduces extremely visible artifacts due to non-temporal denoising. Also, reducing the max bounce to 1 completely kills the global illumination and destroys the lifelike appealing of the image. I simply do not believe that the proposed one is a workable solution. Sure, you get an image out in 1/50th of the time, but that image is useless garbage. At that point you should rather use a non path tracing render engine, such as Eevee or Unreal, the latter being realtime and producing stunning images. Sawing off Cycles' legs is not the right anwers, it's a path that leads to trash images
One of the most helpful blender tips videos I've ever watched. I reduced the render time of the animation video I was working on from 2.5 hours to 10 minutes with no noticeable decrease in quality. Thank you!
One thing that was not mentioned: Go to SOLID VIEV in 3D Viewport when You start rendering. I sometimes catch myself on keeping Rendered View while rendering. That slows render time alot especially in animations.
That’s a very good one! Staying in rendered view when hitting the render button you are eating up VRAM, CPU and RAM, thus limiting your optimal render speed 👍🏻
Only if blender is still actively rendering in the viewport. I think they should just make it stop viewport rendering once an output render is started.
Something to note about Noise Threshold: if you have a clean daylight scene like the example, you can really go wild with it. But if you have any kind of higher key/darker shadows or just a lower light scene, increasing Noise Threshold is gonna kick your ass pretty quick. If your scene is fairly dark, even going from 0.01 to 0.05 could end up giving you horrible results. So keep that in mind. And remember, even if a single image has blotches subtle enough you think you can live with them, NONE of Blender's denoising options are temporal, so those "subtle" blotches are gonna get kind of obvious the moment you render an animation.
I don't think this is necessarily a noise threshold issue, but more of a denoiser issue. Once we get better temporal denoising, this should fix (or at least improve) this issue. But yeah all things considered using less samples (or a higher noise threshold) is always rough on darker scenes.
@@KaizenTutorials yeah, to be clear this is not a problem with Noise Threshold itself, it's just that this is how weaknesses with denoising can rear their head
For night scenes, you can put the threshold at 1.0 and double your resolution. Unless you have insane details that could potentially cause artefacts. It's a three component trick anyway: noise threshold + sample count + resolution to denoise. It's faster to shrink a render from a high resolution that denoising a small image with many details. As always, test yourself. Blender will stop rendering a pixel at the first limit reached (sample or noise threshold). Larger is the image, easier it is to not care about noise threshold.
Buddy, thanks. For us seasoned computer graphics artists it’s great to have you youngens ripping the hood off blender and diving into things we just don’t have time to explore in the studio. UA-camrs such as yourself are an invaluable resource for us, and this tutorial in particular is a great example of how you help the community improve our production flow.
This was one of the best blender tips videos I've ever seen. The tips in this video made a huge difference in the render time of my project. From 20 minutes to just 27 seconds, Woow. For me, this means that my project was saved from certain death because the project I am working on is only 1 day away from the deadline. Thank you so much for this useful video.
This is perhaps the most important Blender video that's out there... the sheer amount of the collective community time saved here would worth of millions for the artists in here... BIG BIG thanks man, you're awesome!! 👍🏽👍🏽👍🏽🙏🏼🙏🏼🙏🏼
If your scene is too dark after these settings, you can change it in post production or increase the light paths. With trasparent materials like glass, you can increase the relevant bounces to get rid of artefacts.
Yes, exactly! Always fit the Light Path Bounces to your scene. If you need more bounces, definitely use them. It would be a waste to create something awesome and for it to look ugly just to save a bit of time on rendering!
4 minutes in and already my render time is insanely fast without even doing the rest yet. This is awesome, thanks so much for making this video dude, saved me a ton of time and super simple to follow!!
Recap for those that want to use these settings in the future and want to copy paste in their notes 1. Make sure you use GPU Compute in your Render Properties tab (assuming you have a decent Graphics Card) & in your blender Preferences > System, make sure you're using your GPU. + additional note in my personal experience, sometime turning OFF your CPU completely and only rendering with your GPU instead of both can be faster (i have a 3080ti and a 5950x and this surprised me because I've never seen people discuss how using only GPU instead of both can be faster) 2. Increase noise threshold for the render (from 0.01 to 0.1 or 0.5) this makes the biggest difference out of all the settings but might reduce final image quality depending on how high you sent the value 3. in Render Properties > Light Paths, reduce max bounces for all (may reduces light bounce quality and only speeds up render a little bit) 4. in Render Properties > Performance > Acceleration Structure, if you have enough ram, turn ON "use curves bvh" and turn OFF "use compact bvh" 5. in Render Properties > Performance > Final Render, turn ON persistent data 6. (this one might actually increase render time so maybe don't use this tip lmao) World settings > Settings > Surface, decrease map resolution from 1024 to 512 (again this might make render speed worse so test and see what works for your scene) 7. in Render Properties > Light Paths > turn ON "Fast GI approximations" (will reduce light bounce accuracy and can can change how the final render lighting will look) Nothing is free in life so all those combined can and will reduce your render quality in exchange for render speed (example of before and after at 11:25)
Thanks for this concise summary! A great short version of what I’m explaining :-) also you can compare images via the link in the pinned comment. Here you can see all full res images!
About point 1: I have a 5600X and a (just bought) 3060 12GiB. Tested the GPU with Blender too - and found out the same: it is MUCH faster using only GPU render. With both CPU and GPU the thing gets quite slower.
Dude this is wild. With just Adaptive Sampling of 0.01 I decreased my render time from 3 mins to 13 seconds with no noticeable difference. Thank you so much for that. I would use the rest of the setting for my next renders. You deserve more subscribers.
i have watched many videos with this premise, and this is BY FAR the best one. lots of settings i had never heard of, and you showed the renders ad render time that each each change caused so i could decide what worked best!
Couple more ideas: Close Blender and render via command line. Will free up some GPU cycles and memory from not displaying Blender, especially if you have a busy viewport open. Learn to use the Light Paths node to take shortcuts through some objects. For example, using the Shadow Ray output on volumetrics or refractive objects to swap in a Transparent shader to let Shadow Rays through unimpeded.
Oh my goodness gracious me, my render was originally taking 17 minutes per frame and I was accepting my fate with a 4 day render but now I can look forward to seeing my render tomorrow morning which will be done in approximately 5 hours. This is really a godly tutorial and will help me achieve so much more in future
Thats one of the greatest tips video ever.For two days I have been struggling with lack of memory problems and big black squares in renders , this video helped me a lot!Thank you!
How much time did you manage to save on your render? Leave a comment! I made an oopsie; please disable CPU in the system preferences if that’s possible. It makes renders slower than having ONLY the GPU enabled. Also because the images in this video might be a bit small to compare, here are all the full size images per timestamp; imgur.com/a/mDzecBm
Nice vid, I'm using a 5800X with 64GB of RAM and a 6800XT. The biggest performance boost for my renders was switching to Linux. I'm not sure what's running in the background of windows but while doing 2000 frames animations it adds up! Linux runs super stable (I hadn't ANY crashes yet, which is awesome) and pretty fast as well. With the exact same settings and hardware I could reduce the render time from 1min and 35 sec to 38 sec. With the exact same render settings (migrated project file). That's huge!
Either this man is a human UA-cam algorithm or UA-cam itself is getting better at reading my mind. Just when I think that there is no video covering my particular problem, this man comes in and saves my day! Perhaps one of the best channels for me with the likes of Polyfjord, Blender Guru and Ducky3D
From 10 hours to 10 minutes. As a complete noob to blender this is just what I needed! It was super hard to find this information. Thank you so much man!
Thanks dude ! My render was on CPU, it took about 4 minutes to render a frame! I changed it to GPU (so it used my RTX 2070) and it took 30 secondes to render one single frame! I went from 4 days rendering to 2 days ! Thank you so much
Super useful. Literally see the picture rendered in a small fraction of the time before, no quality loss... This is dope work, Dude! Thank you for doing the research for us.
I think "Blender has a pretty good denoiser these days" is a bit of an understatement, the denoiser is good enough to reasonably use 16 max samples (for 1080p) without any clearly visible quality loss in some situations (although fine details might make 16 too little)
Haha, you might be right on that! The denoiser is great. But when doing volumetric stuff it can still result in very noisy animations with loads of artefacts in the final render!
thank you so much for this! it saves me a tons of time... i'd been waiting 12 hours to render 40 frames of animation... and i have 200frames now it's rendering a lot faster
Lowering the tiling size helps with any memory issues. Default is 2048 reducing this to 1024 alongside the tips here can greatly help speed up your renders.
Thank you so much. I am working on a animation for university and wanted to avoid using a render farm. With your tips and some fiddling around I got from over 2minutes per image to roughly 30seconds!
this helped me A LOT. I was rendering an animation that would take like 2 full days for render everything. Now I'm already rendering it all in like 3 hours and with now damage to the quality of it. thank you!!
And another point worth mentioning is that, even if not fully used (and abused) for the final render, this tip is crazy effective for iteration/interactive renders/viewport etc. See my post below for another example of render times using the tips in the video.
Exactly this! If you want to make a final render it's oftentimes (especially profesionally speaking) to just take the hit of having a 15 hour render or so. But for iteration/look dev, quick renders are a lifesaver in my opinion.
It should be added that rendering an animation with little sample (Or a large noise treshold) along with a denoiser will cause artifacts like flickering. There'sa new temporal OptiX denoiser that makes the flickering almost a thing of the past. I'd recommend to look into it if any of you want to render an animation with cycles.
I wholeheartedly agree with you. Nevertheless, for interior animations I recommend starting with 4096 samples and 0.01 Noise Threshold and decreasing this last value until it looks right. There's no magic bullet...
Excellent work. I always combine increasing the noise threshold with increasing the resolution. I go up to 4k from HD, for example, which I then down-sample to HD again for delivery. This helps sharpen any loss of detail from the higher noise threshold.
Very good tutorial on "under the hood" Blender tuning. You have made my subscription list. One request - a video on settings to speed up cycles viewport updates when modeling.
This is great I think I’ve heard most of these tips before, but this is by far the most concise, and easy to understand video on the subject. Will definitely be sharing.
If your Light Passes are set to only a total of 1 it doesn't matter if your Transmission and Transparency are at 2, you will only get one rendered Light Pass. The total should be equal to the highest number of passes, in your case- 2.
Yes! I added a text frame explaining this. I did change it in the render but apparently didn’t record that, so that’s why I had to add the text frame. Thanks for bringing extra attention to it since it is important to know though! 🙏🏻
You are the best, my friend. I watched dozens of videos trying to get my GPU to stop freezing and reduced my render time from 16 minutes to 1. Thank you so much."
Thank you very much, With your technics I could go from a ~18h long render to a 1 min and 27s fast rendering time UNBELIEVABLE!!! I have a GeForce GTX 750 (Display)
In your tip with the Noise Threshold, you lost a lot of detail in the grass. Probably not a problem in an animation, but I would very much prefer the first image as a still. But, as you told already, the artist has to choose which compromises are worth it.
Actually, increasing the Noise Threshold as a major impact in animation quality. Unfortunately, values like 0.01 and lower are needed to avoid excessive noise reduction artifacts (woobling) in animations.
2:10 you should uncheck the CPU, when it's checked with GPU it enables hybrid rendering, even if you select GPU compute on the render tab. It's way slower than just GPU rendering.
Well the Windows task manager is not really a good tool for monitoring your hardware. Please try to use a tool created by the manufacturer of your GPU. For example I use Aorus Engine, since I have a Gigabyte GPU. If then still you’re using 100%, you’ll have to lower the specs on your render settings and maybe texture quality, scene polygons etc. Hope that helps!
Tip for you! I think you may need to turn down gain a decent bit using the top knob on the back of your Yeti. Should make the mic a lot more crisp and clear :) Awesome tutorial, thank you so much!
I was so frsutrate because my renders were taking sooooo long, and it had been like 2 hours and only 11 frames had rendered, but the second tip you did literally saved me from the painful wait. Thank you SO much!!!
nice tips to try out. I noticed you used an 8k hdr though... if its just for lighting might I suggest a 1k version instead. Lighting info should be exactly the same & saves more on render time
I never knew about the gpu thing, when I saw youtubers move in cycles I thought they had like top notch hardware. And I never knew I just hadn't been using my 3080. Saved me from countless hours of overnight render, thank you.
I'll be honest, I don't understand why Cycles doesn't set to GPU by default when you have a compatible GPU installed. I bought myself an RTX card rather than AMD specifically because the built in raytracing ought to be great for rendering in Cycles, but because I wasn't aware of the preferences thing at first, I was a little disappointed in the results. Once I saw that though, switched the device over to OptiX and Cycles renders SOO much faster.
Yeah haha you're not the first ot mention this! I did it because the images were to similar in my opinion and I couldn't tell when the image changes myself lol. I've added a pinned comment containing a link to all high-res renders, so you can REALLY compare them!
I like the idea of starting all light paths on 1 then working your way up. I normally half all of them. Although transparency has caught me out a couple of times. Making sure all other programs are closed also helps. Kind of obvious but can forget when your busy.
Yeah I think it might me a bit more tweaking this way. But if you get everything set up nice you’ll gain a lot in speed! Good tip on the other software though! Definitely helps. E.g. chrome can be a major RAM glutton, so closing down chrome can help a lot!
Good question! As far as I know ALL versions of Blender, up from 3.0, come with Cycles X. Cycles X was just a complete rewrite of the render engine, making it tons faster. So using any of the newer Blender builds will automatically give you access to this newer version of Cycles. :-)
Thank you so much for covering all these settings. As someone learning blender and never made my preference settings,, I started with my landscape render at 1:40:00 (1 hour 40 minutes) and after your video it is now 0:00:28!! (28 seconds) LOL
quick sound tip: cut down on your mic gain and bump up the volume, consider adding a compressor (if you know how), and cut down on the mid range in EQ (definitely only if you know how).
Disable CPU If your CPU slower than the GPU So the GPU could Use it 100% capability. Learn about creating linked scenes layer. Where you can Render the character,mesh,prop,world,etc.. in different samples or Render engine (Eevee Useful for Transparent Bloom). So you won't have to bother to render everything or render viewlayer with 4096 samples With 8k textures all at once.
Great tips here! Especially seperating the objects and rendering each with it's own settings can save you a bunch of time. Just be wary of shadows and reflections though. These might not be included properly!
@@KaizenTutorials Best way for my Gtx1050ti to handle stuff around My Cpu is just useless. When camera doesn't move and only the character does I just use 512samples and the background 64samples. Or unlink Collection light to only affect the character faces.
Bro, you helped a lot, after accomplishing your instructions, it had me anxious when it said 21 mins remaining, and it seemed slow, but i looked away for like a sec and i saw it leap, from 12% to a 100% in like 2 mins
I'm running Blender on a machine with an i7 930 @2.80GHz, 32GIGs of ram and GTX 1650. I'm obviously not doing large scenes, but using some of these settings actually helped tremendously on the stuff I am doing.
I used to run a nearly similar setup before upgrading. It's a decent setup and works fine for 90% of things. Just always had issues with VRAM in larger scenes! That will sadly still be an issue with these tips, but glad I could atleast help you speed things up!
Ah, thankyou so much for this. Im quite new to blender so still learning quite alot especially with render speeds too. Ps.. You are very good looking so helps me concentrate and listen attentively too!
This video just got a major update with new settings, optimized for Blender 4.0+! Check it out here; ua-cam.com/video/Jv1vk8YWCsQ/v-deo.html
Hi, wonderful video ! Could it be possible to get the test file with the tree ? It could seem stupid but i find that the backgroung colors (light grey + light green from the tree) + "white lighting" is very attractive. I tried to do mine but i can't manage to get the same effects ! Best. Francis
Next time when comparing one image against the other, please cut directly from one to the other and don't insert black frames. With a direct transitions, small changes seem to blink, which helps spot areas of difference.
Noted, thanks for the feedback!
Agreed, or better still would be to slice them in half and put them side by side imo 👍
it's made on purpose to conceal the differences. at 12:00 you can see that the fast image is significantly worse in terms of lighting
I hve a pinned comment with all images on imgur. So you can check out at your leisure. Yes the quality is worse and yes the lighting changes! That’s why I tell everyone to choose whether or not the time is worth the tradeoff in quality. I (try) to hide nothing and be transparent!
@@KaizenTutorials I'm not blaming you, it's not your fault, but rather the complexity of the problem itself. However, increasing the noise threshold this much significantly reduces the quality of the image (as can be seen in the grass in the shade) and introduces extremely visible artifacts due to non-temporal denoising. Also, reducing the max bounce to 1 completely kills the global illumination and destroys the lifelike appealing of the image. I simply do not believe that the proposed one is a workable solution. Sure, you get an image out in 1/50th of the time, but that image is useless garbage. At that point you should rather use a non path tracing render engine, such as Eevee or Unreal, the latter being realtime and producing stunning images. Sawing off Cycles' legs is not the right anwers, it's a path that leads to trash images
One of the most helpful blender tips videos I've ever watched. I reduced the render time of the animation video I was working on from 2.5 hours to 10 minutes with no noticeable decrease in quality. Thank you!
That’s super awesome! Thanks a lot for sharing. This was exactly what I was hoping to achieve with this video :-)
wow
Wtf it's still the worst Render Engine I've ever Seen It only making shit uglier
Cycles??
@@佐久-b6k what lol
Just went from an 8 hours render to a 6 minutes one, thank you man.
Nice!
What are your PC Specs?
wow, nice!
One thing that was not mentioned: Go to SOLID VIEV in 3D Viewport when You start rendering. I sometimes catch myself on keeping Rendered View while rendering. That slows render time alot especially in animations.
That’s a very good one! Staying in rendered view when hitting the render button you are eating up VRAM, CPU and RAM, thus limiting your optimal render speed 👍🏻
Only if blender is still actively rendering in the viewport. I think they should just make it stop viewport rendering once an output render is started.
Yeah that makes sense to me aswell! Auto switch to solid view when you start a render.
I render in CLI. That's the fastest for me.
@@drkastenbrot There's a setting for this, "Lock Interface" under the Render dropdown in the top left corner.
Something to note about Noise Threshold: if you have a clean daylight scene like the example, you can really go wild with it. But if you have any kind of higher key/darker shadows or just a lower light scene, increasing Noise Threshold is gonna kick your ass pretty quick. If your scene is fairly dark, even going from 0.01 to 0.05 could end up giving you horrible results. So keep that in mind.
And remember, even if a single image has blotches subtle enough you think you can live with them, NONE of Blender's denoising options are temporal, so those "subtle" blotches are gonna get kind of obvious the moment you render an animation.
I don't think this is necessarily a noise threshold issue, but more of a denoiser issue. Once we get better temporal denoising, this should fix (or at least improve) this issue. But yeah all things considered using less samples (or a higher noise threshold) is always rough on darker scenes.
@@KaizenTutorials yeah, to be clear this is not a problem with Noise Threshold itself, it's just that this is how weaknesses with denoising can rear their head
For sure! Thanks for pointing it out 💪🏻
For night scenes, you can put the threshold at 1.0 and double your resolution. Unless you have insane details that could potentially cause artefacts.
It's a three component trick anyway: noise threshold + sample count + resolution to denoise. It's faster to shrink a render from a high resolution that denoising a small image with many details.
As always, test yourself. Blender will stop rendering a pixel at the first limit reached (sample or noise threshold).
Larger is the image, easier it is to not care about noise threshold.
@@kirkanos771 Great tips!
Buddy, thanks.
For us seasoned computer graphics artists it’s great to have you youngens ripping the hood off blender and diving into things we just don’t have time to explore in the studio.
UA-camrs such as yourself are an invaluable resource for us, and this tutorial in particular is a great example of how you help the community improve our production flow.
Wow, love the comment! Thanks a lot, appreciate the kind words and I’m glad this helped 🙏🏻
This was one of the best blender tips videos I've ever seen. The tips in this video made a huge difference in the render time of my project. From 20 minutes to just 27 seconds, Woow. For me, this means that my project was saved from certain death because the project I am working on is only 1 day away from the deadline. Thank you so much for this useful video.
No problem glad I could help!
This is perhaps the most important Blender video that's out there... the sheer amount of the collective community time saved here would worth of millions for the artists in here... BIG BIG thanks man, you're awesome!! 👍🏽👍🏽👍🏽🙏🏼🙏🏼🙏🏼
Wow, thanks! Appreciate that. 🙌
If your scene is too dark after these settings, you can change it in post production or increase the light paths. With trasparent materials like glass, you can increase the relevant bounces to get rid of artefacts.
Yes, exactly! Always fit the Light Path Bounces to your scene. If you need more bounces, definitely use them. It would be a waste to create something awesome and for it to look ugly just to save a bit of time on rendering!
4 minutes in and already my render time is insanely fast without even doing the rest yet.
This is awesome, thanks so much for making this video dude, saved me a ton of time and super simple to follow!!
Great to hear! Glad I could help 🤗
Recap for those that want to use these settings in the future and want to copy paste in their notes
1. Make sure you use GPU Compute in your Render Properties tab (assuming you have a decent Graphics Card) & in your blender Preferences > System, make sure you're using your GPU.
+ additional note in my personal experience, sometime turning OFF your CPU completely and only rendering with your GPU instead of both can be faster (i have a 3080ti and a 5950x and this surprised me because I've never seen people discuss how using only GPU instead of both can be faster)
2. Increase noise threshold for the render (from 0.01 to 0.1 or 0.5) this makes the biggest difference out of all the settings but might reduce final image quality depending on how high you sent the value
3. in Render Properties > Light Paths, reduce max bounces for all (may reduces light bounce quality and only speeds up render a little bit)
4. in Render Properties > Performance > Acceleration Structure, if you have enough ram, turn ON "use curves bvh" and turn OFF "use compact bvh"
5. in Render Properties > Performance > Final Render, turn ON persistent data
6. (this one might actually increase render time so maybe don't use this tip lmao) World settings > Settings > Surface, decrease map resolution from 1024 to 512 (again this might make render speed worse so test and see what works for your scene)
7. in Render Properties > Light Paths > turn ON "Fast GI approximations" (will reduce light bounce accuracy and can can change how the final render lighting will look)
Nothing is free in life so all those combined can and will reduce your render quality in exchange for render speed (example of before and after at 11:25)
Thanks for this concise summary! A great short version of what I’m explaining :-) also you can compare images via the link in the pinned comment. Here you can see all full res images!
About point 1:
I have a 5600X and a (just bought) 3060 12GiB. Tested the GPU with Blender too - and found out the same: it is MUCH faster using only GPU render. With both CPU and GPU the thing gets quite slower.
Ok, good to know! Thanks for sharing 🙌🏻
I can confirm disabling the CPU and only using the GPU shaved off 2-3 seconds of render time even with an Intel i7 12700K with 20 threads.
Yep, I added this to the pinned comment. Using only GPU is better!
When I was searching for this guide you weren't showing up. Now you just popped up into suggestions, better late than never!!!
Damn you YT algorithm! ;-) Well like you said; better late than never. Thanks!
Dude this is wild. With just Adaptive Sampling of 0.01 I decreased my render time from 3 mins to 13 seconds with no noticeable difference. Thank you so much for that. I would use the rest of the setting for my next renders. You deserve more subscribers.
Great to hear! Thanks.
i have watched many videos with this premise, and this is BY FAR the best one. lots of settings i had never heard of, and you showed the renders ad render time that each each change caused so i could decide what worked best!
Thanks a lot! Glad you found the setup like this useful 👍🏻
Couple more ideas:
Close Blender and render via command line. Will free up some GPU cycles and memory from not displaying Blender, especially if you have a busy viewport open.
Learn to use the Light Paths node to take shortcuts through some objects. For example, using the Shadow Ray output on volumetrics or refractive objects to swap in a Transparent shader to let Shadow Rays through unimpeded.
That’s some very deep knowledge! Thanks for sharing these insights 💪🏻
@@KaizenTutorials baking your stuff also helps with render time ^^
hi! Is there any video tutorial u recommend to learn how to render via command line?? thanks in advance!
@@JorgeSilva-ot1hq Would like to know as well :)
Oh my goodness gracious me, my render was originally taking 17 minutes per frame and I was accepting my fate with a 4 day render but now I can look forward to seeing my render tomorrow morning which will be done in approximately 5 hours. This is really a godly tutorial and will help me achieve so much more in future
Glad I could help!
Thats one of the greatest tips video ever.For two days I have been struggling with lack of memory problems and big black squares in renders , this video helped me a lot!Thank you!
How much time did you manage to save on your render? Leave a comment!
I made an oopsie; please disable CPU in the system preferences if that’s possible. It makes renders slower than having ONLY the GPU enabled.
Also because the images in this video might be a bit small to compare, here are all the full size images per timestamp;
imgur.com/a/mDzecBm
Being honest... the last image looks more realistic and all then the one at the beginning which took more than 6 mins.
Well that’s a BIG win then right, haha? Looks better + saves you well over 6 minutes in reder time! 💪🏻
@@KaizenTutorials for sure... tree bark and shadows are so real and it kinda gives that vibe onto the ground as well... so hands down awesome.
Nice vid, I'm using a 5800X with 64GB of RAM and a 6800XT.
The biggest performance boost for my renders was switching to Linux. I'm not sure what's running in the background of windows but while doing 2000 frames animations it adds up! Linux runs super stable (I hadn't ANY crashes yet, which is awesome) and pretty fast as well. With the exact same settings and hardware I could reduce the render time from 1min and 35 sec to 38 sec. With the exact same render settings (migrated project file). That's huge!
@@vishisht8688 I'd the the last before the last looks the best, super deep shadows :D
Amazing stuff!
Thank you!
Either this man is a human UA-cam algorithm or UA-cam itself is getting better at reading my mind. Just when I think that there is no video covering my particular problem, this man comes in and saves my day! Perhaps one of the best channels for me with the likes of Polyfjord, Blender Guru and Ducky3D
Wow, thanks for the big praise! Very kind of you and I'm glad you found my vid useful.
From 10 hours to 10 minutes.
As a complete noob to blender this is just what I needed! It was super hard to find this information.
Thank you so much man!
Glad it helped!
Thanks dude ! My render was on CPU, it took about 4 minutes to render a frame!
I changed it to GPU (so it used my RTX 2070) and it took 30 secondes to render one single frame!
I went from 4 days rendering to 2 days ! Thank you so much
Great to hear! I think you could get it down even further, if you want it to by using the other tips aswell!
Super useful. Literally see the picture rendered in a small fraction of the time before, no quality loss... This is dope work, Dude! Thank you for doing the research for us.
Glad it was helpful!
Wow this changes really increased my render speed so much, Thanks for great tutorial
Great to hear! Thanks
Essential video for all blender users. No hyperbole. Amazing stuff Kaizen thank you.
Thanks a lot! Appreciate the support 💪
Thank you, very helpful! I'm a 2D artist and I'm very noob with 3D software, my rendering went from 24 minutes to 40 seconds with your tips. 🙏❤
Glad to help! 🙌🏻
omg u helped me so much (using blender for over 3 yrs and never thought that it could be this quick thank you so much)
Glad I could help!
Awesome video and there are some awesome tips in the comments as well. This is a gold mine for render speed tips
Great to hear! Thanks for the kind words.
As a new learner who won't switch to cycles to rendering everything in cycles is crazy thanks man < 3
Happy to help!
I think "Blender has a pretty good denoiser these days" is a bit of an understatement, the denoiser is good enough to reasonably use 16 max samples (for 1080p) without any clearly visible quality loss in some situations (although fine details might make 16 too little)
Haha, you might be right on that! The denoiser is great. But when doing volumetric stuff it can still result in very noisy animations with loads of artefacts in the final render!
For still images I agree with you, but those are very few samples for animations, especially interior archviz animations.
This saved my ass. Thank you for giving an explanation and not just saying "move this, move that". I appreciate your effort!
That's great to hear. Glad this video was useful to you! :-D
thank you so much for this! it saves me a tons of time... i'd been waiting 12 hours to render 40 frames of animation... and i have 200frames now it's rendering a lot faster
Glad to help!
Lowering the tiling size helps with any memory issues. Default is 2048 reducing this to 1024 alongside the tips here can greatly help speed up your renders.
Good tip! Thanks for sharing.
Hello, I'm kinda confused, shouldn't cycles X work better without tiling?
@@ahmadzuhri6190 adjusting tiling is mainly for saving memory usage.
@@ahmadzuhri6190What these people forgot to mention is that it helps with the GPU vram memory not CPU ram memory
Wow your tree scene is beautiful. Right now I don't have such beautiful shadows inside the tree, for the part with leaves. So much things to learn.
Thank you so much. I am working on a animation for university and wanted to avoid using a render farm. With your tips and some fiddling around I got from over 2minutes per image to roughly 30seconds!
Glad I could help!
this helped me A LOT. I was rendering an animation that would take like 2 full days for render everything. Now I'm already rendering it all in like 3 hours and with now damage to the quality of it. thank you!!
Glad I could help!
And another point worth mentioning is that, even if not fully used (and abused) for the final render, this tip is crazy effective for iteration/interactive renders/viewport etc. See my post below for another example of render times using the tips in the video.
Exactly this! If you want to make a final render it's oftentimes (especially profesionally speaking) to just take the hit of having a 15 hour render or so. But for iteration/look dev, quick renders are a lifesaver in my opinion.
amazing video , amazing work ! thank you !!
Thanks a lot!
that's a massive tip, thankyou for even going into details man👊
Thanks, glad you like it!
Thanks!
Thank you for the support! 🖤
This was very useful for a starter blender user I finally can render things faster and won't wait 2 hole days thank you.
Glad it helped!
Finally a proper explanation of noise threshold!! Thank you finally know how to use it properly
You're welcome!
The main problem with noise threshold is artifacts. But if you turn up the resolution in output settings, you can seriously get better results
never thought i'd be able to use cycles like today. thank you.!!
Happy to help!
Doing an animation, you saved me one hell of a lot of time. THANKS!
That’s awesome to hear! Thanks for sharing 🙏🏻
I was doing passion projects and this saves me lots of time! Thank you
It should be added that rendering an animation with little sample (Or a large noise treshold) along with a denoiser will cause artifacts like flickering. There'sa new temporal OptiX denoiser that makes the flickering almost a thing of the past. I'd recommend to look into it if any of you want to render an animation with cycles.
Yeah thats true! And thanks for sharing this info.
Dont use the optix denoiser. Use the superimagedenoise addon instead. Its much better quality with less flickering
I wholeheartedly agree with you. Nevertheless, for interior animations I recommend starting with 4096 samples and 0.01 Noise Threshold and decreasing this last value until it looks right. There's no magic bullet...
@@kooale3252 Did you try the OptiX temporal denoiser? I got pretty good results last time I used it.
@@Layston yep and superimagedenoise still preserved more details.
Excellent work. I always combine increasing the noise threshold with increasing the resolution. I go up to 4k from HD, for example, which I then down-sample to HD again for delivery. This helps sharpen any loss of detail from the higher noise threshold.
That's a good trick! I use it too and really helps with the detail indeed, without increasing render time by a lot.
Very good tutorial on "under the hood" Blender tuning. You have made my subscription list. One request - a video on settings to speed up cycles viewport updates when modeling.
Thanks a lot, welcome to the club! 💪🏻 I’ll take it into consideration. Been thinking about doing a viewport performance increase video!
This is great I think I’ve heard most of these tips before, but this is by far the most concise, and easy to understand video on the subject. Will definitely be sharing.
Awesome, thank you!
If your Light Passes are set to only a total of 1 it doesn't matter if your Transmission and Transparency are at 2, you will only get one rendered Light Pass. The total should be equal to the highest number of passes, in your case- 2.
Yes! I added a text frame explaining this. I did change it in the render but apparently didn’t record that, so that’s why I had to add the text frame. Thanks for bringing extra attention to it since it is important to know though! 🙏🏻
You are the best, my friend. I watched dozens of videos trying to get my GPU to stop freezing and reduced my render time from 16 minutes to 1. Thank you so much."
Glad I could help, thanks for the kind words.
Thank you very much, With your technics I could go from a ~18h long render to a 1 min and 27s fast rendering time UNBELIEVABLE!!! I have a GeForce GTX 750 (Display)
That’s awesome! Thanks for sharing 💪🏻
4 hours to 2:30 mins for a fluffy .3ds file. Hardly noticeable. Thanks! You're a life saver :)
You love to see it!
In your tip with the Noise Threshold, you lost a lot of detail in the grass. Probably not a problem in an animation, but I would very much prefer the first image as a still. But, as you told already, the artist has to choose which compromises are worth it.
just decrease the threshold much lower then, 0.001 or 0.0001
Actually, increasing the Noise Threshold as a major impact in animation quality. Unfortunately, values like 0.01 and lower are needed to avoid excessive noise reduction artifacts (woobling) in animations.
Do studios do that compromise?
@@mrlightwriter wobbling can now be reduced by temporal optix denoising
@@axe_fx As far as I know, only SID uses temporal optix denoising, or am I wrong?
thanks man the setting you show is really good and it really pretty fast with my animation. thanks man
Glad I could help
I rendered one of my scenes according to your tips and the render time decresed 2 times even when I used 256 render samples 👍👍😁😁 good job
Nice work! The best thing I could've hoped for; saving all of you some rendering time!
the noise threshold tip ALONE dropped my render times from 2 minutes to 30 seconds
Awesome! Love to hear it :-)
I suppose the 11 seconds per frame result is very much usable if you’re animating a toon/anime style scene.
Nicely done bro. Thanks for the tutorial.
Yes it does! It can save you hours on longer animations :-)
dude seriously thank you for this video, it took my render for a music video 4 days (at 41% LEFT) to getting to that point in less than an hour!!!
2:10 you should uncheck the CPU, when it's checked with GPU it enables hybrid rendering, even if you select GPU compute on the render tab. It's way slower than just GPU rendering.
I just checked and you’re right! Thanks for letting me know. I will add it to the 📌 comment! :-)
I have CPU unchecked, but when rendering the Windows task manager shows CPU & GPU usage, CPU actually hits 100%...any suggestions? 🤔
Well the Windows task manager is not really a good tool for monitoring your hardware. Please try to use a tool created by the manufacturer of your GPU. For example I use Aorus Engine, since I have a Gigabyte GPU.
If then still you’re using 100%, you’ll have to lower the specs on your render settings and maybe texture quality, scene polygons etc.
Hope that helps!
@@KaizenTutorials Thanks! 👍
Thankyou so much, I've been able to reduce my animations renders by an hour or two which this so thank you so much ❤
Your tips make my 3070Ti work as fast as 4090, and save me a ton of money. Thanks a lot!
Yeah! Super happy to hear that. :-)
Like everyone else, saved me hours. Thank you for making this!!
Glad to help :-)
Tip for you! I think you may need to turn down gain a decent bit using the top knob on the back of your Yeti. Should make the mic a lot more crisp and clear :)
Awesome tutorial, thank you so much!
Thanks! Yeah not sure what went wrong in recording the audio for this vid. I'll try to get it sorted for the next one!
I was so frsutrate because my renders were taking sooooo long, and it had been like 2 hours and only 11 frames had rendered, but the second tip you did literally saved me from the painful wait. Thank you SO much!!!
Glad to hear it! You’re welcome! 🙌🏻
nice tips to try out. I noticed you used an 8k hdr though... if its just for lighting might I suggest a 1k version instead. Lighting info should be exactly the same & saves more on render time
Thanks! Yes if you were to optimize it it’s definitely worth using a lower res HDRI. Great tip!
IT WORKS went from a render time of 1:53:00:00 to 00:01:48:00 Thank you!
Awesome!
I keep coming back to this video every time I experience slow renders, cuts a lot of render time out. Thank You!@@KaizenTutorials
subbed & liked! You save my ass. Went from an hour render to 4 minutes. Holy shit bro.
Haha awesome! Glad I could help :-)
I never knew about the gpu thing, when I saw youtubers move in cycles I thought they had like top notch hardware. And I never knew I just hadn't been using my 3080. Saved me from countless hours of overnight render, thank you.
Yeah it's a common issue but glad this helped you prevent all that frustration haha!
I'll be honest, I don't understand why Cycles doesn't set to GPU by default when you have a compatible GPU installed. I bought myself an RTX card rather than AMD specifically because the built in raytracing ought to be great for rendering in Cycles, but because I wasn't aware of the preferences thing at first, I was a little disappointed in the results. Once I saw that though, switched the device over to OptiX and Cycles renders SOO much faster.
Yeah don’t know why either. You can overwrite the default startup file though to save you from switching manually all the time.
Great tutor, but it would be better to stack render shots together without black screen to understand the difference)
Yeah haha you're not the first ot mention this! I did it because the images were to similar in my opinion and I couldn't tell when the image changes myself lol. I've added a pinned comment containing a link to all high-res renders, so you can REALLY compare them!
Thank you so much for this! You saved my final architecture project 🙏🏽
Glad I could help!
I like it so much sir thank you so nice man
Thanks a lot! Appreciate the kind words. 🙏🏻
I like the idea of starting all light paths on 1 then working your way up. I normally half all of them. Although transparency has caught me out a couple of times.
Making sure all other programs are closed also helps. Kind of obvious but can forget when your busy.
Yeah I think it might me a bit more tweaking this way. But if you get everything set up nice you’ll gain a lot in speed!
Good tip on the other software though! Definitely helps. E.g. chrome can be a major RAM glutton, so closing down chrome can help a lot!
Do you know if cycles-x rendering is faster or slower than the newest 3.2.2 version? I want to download the version with the faster cycle render time.
Good question! As far as I know ALL versions of Blender, up from 3.0, come with Cycles X. Cycles X was just a complete rewrite of the render engine, making it tons faster. So using any of the newer Blender builds will automatically give you access to this newer version of Cycles. :-)
Thanks again, my Brother, you are Awesome. Wishing you your Best Year Yet for 2023, my Friend!! 🙏🏾
Thanks a lot my friend! 🖤 all the best to you as well.
@@KaizenTutorials Hey man, very welcome, and many thanks!! Much Love, Bro
super helpful..
Awesome to hear!
You are a savior man, you just saved me a hell lot of time in rendering my animation. I loved it
Glad to help 🙌🏻
Cool tips ! Would've been nice to see a zoomed in part of the tree when comparing the images though
That’s a good idea. I’ll upload all images separately somewhere and put a link in a pinned comment. Thanks!
@@KaizenTutorials thanks for following up!
@@FrancisBourgouin Just added an imgur link containing all high-res images with timestamps and settings per image :-)
Wow this changes really increased my render speed so much, Thanks for great tutorial I like so much I love it
You're welcome!
Great tips ! I'm gonna try use them in my Backrooms video and upgrade my quality !
Awesome! Let me know how that turns out 💪🏻
THANK YOU Just changing the noise threshhold improved it alot
Awesome! Glad to hear it :-)
MY RENDERER WAS SET TO NONE!!!
Damn, such a common issue but it always sucks to hear!
Mine too lamo, I got to know it after my motherboard got some issues from overheating
Mine too LAMO!!! Should make that a lot clearer in software.
bro this is the first vid I saw for you and you're amazing thank you so much this helped a LOT like hell A LOT
Thank you! Glad you found the video useful.
I think you should increase transparency path to 8 when rendering leaves
That's definitely an option which can increase the realism!
Thank you so much for covering all these settings. As someone learning blender and never made my preference settings,, I started with my landscape render at 1:40:00 (1 hour 40 minutes) and after your video it is now 0:00:28!! (28 seconds) LOL
Haha wow that’s crazy fast compared to the original! Glad these tips helped you :-)
When you compare, pls don’t fade to black. Just immediately cut or, better yet, wipe back and forth. Thanks
I had that at first but there was so little change that it was impossible to notice when the image changed haha especially after YT compression 😂
quick sound tip: cut down on your mic gain and bump up the volume, consider adding a compressor (if you know how), and cut down on the mid range in EQ (definitely only if you know how).
Yeah the sound was f-ed up in this video. I've since gotten a new mic with way better audio and audio settings. Thanks for the tips though!
nice one, straight to the point, really useful - thank you man
Thanks, glad to hear it!
Disable CPU If your CPU slower than the GPU So the GPU could Use it 100% capability.
Learn about creating linked scenes layer. Where you can Render the character,mesh,prop,world,etc.. in different samples or Render engine (Eevee Useful for Transparent Bloom).
So you won't have to bother to render everything or render viewlayer with 4096 samples With 8k textures all at once.
Great tips here! Especially seperating the objects and rendering each with it's own settings can save you a bunch of time. Just be wary of shadows and reflections though. These might not be included properly!
@@KaizenTutorials Best way for my Gtx1050ti to handle stuff around My Cpu is just useless. When camera doesn't move and only the character does I just use 512samples and the background 64samples. Or unlink Collection light to only affect the character faces.
@@KaizenTutorials My english suck. soz
No worries, you good! Thanks for the insights 💪
Bro, you helped a lot, after accomplishing your instructions, it had me anxious when it said 21 mins remaining, and it seemed slow, but i looked away for like a sec and i saw it leap, from 12% to a 100% in like 2 mins
Sound is heavily clipping. Great video though
Yep, sorry about that. Can’t seem to get my audio balance right :-(
i know the video is 2 years old, but you just safed me soooooooooo much time :D i want to say THANK YOU!
And here's some better news still; there's an updated version of this vid that will further improve it for sure! ;-)
Thank you so much man, From 10 hours to 2 hours this save me a lot of time !
You're welcome!
I'm running Blender on a machine with an i7 930 @2.80GHz, 32GIGs of ram and GTX 1650. I'm obviously not doing large scenes, but using some of these settings actually helped tremendously on the stuff I am doing.
I used to run a nearly similar setup before upgrading. It's a decent setup and works fine for 90% of things. Just always had issues with VRAM in larger scenes! That will sadly still be an issue with these tips, but glad I could atleast help you speed things up!
Great tips. My 55,000 verts render went from 1m 32.62 to 4.53 seconds. Very happy with that, thanks @Kaizen Tutorials!!
Glad it helped! 🙌
What a great demonstration, thank you for sharing
Thanks for watching!
Ah, thankyou so much for this. Im quite new to blender so still learning quite alot especially with render speeds too. Ps.. You are very good looking so helps me concentrate and listen attentively too!
Thank you! Appreciate the kind words, haha. 🤗
Wow, your video has given me back the desire to use blender, nobody gave me solutions as good as you. Thank you
Thanks a lot! Appreciate the kind words :-)