HUGE SALE! You can save 50% on all my courses until the end of Christmas with the code XMAS - The Essential Topology Guide - decoded.gumroad.com/l/ESSENTIALTOPO Also available on Blender Market - blendermarket.com/products/essentialtopo The Interior Masterclass - decoded.gumroad.com/l/interiormasterclass Also available on Blender Market - blendermarket.com/products/the-interior-masterclass The Exterior Masterclass - decoded.gumroad.com/l/exteriormasterclass Also available on Blender Market - blendermarket.com/products/the-exterior-masterclass
You can also run out of GPU memory if you have enabled rendering in the viewport at the same time while rendering the final image. When you have this combination AND you render an animation, in addition performance will drop significantly.
@@DECODEDVFX It really is. I hate myself for giving Nvidia money, but my ability to get things done is effing amazing. I just wish it had more VRAM I bump the limit all the time. WHich is where tiles comes into play.
According to my experience tiling is also important on big size renders. Let's say you are taking an 8K render with bunch of geometry and textures in the scene, in this case if you dont use tiling the whole frame rendered at once is much slower than multi tile rendering and it might result in crash or not responding status. Leaving it at 2048 with tiling enabled usually works good for me.
regarding tiles, gpu is faster with big tiles, cpu is faster with small tiles. if you do a lot of rendering, like a mult animation, maybe it is a good reason to test performance with different tile sizes
That used to be true, but it isn't really the case since cycles X was released. Before I made this video I tested various tile sizes on CPU. It was always faster to use the default tile size of 2048 when rendering at 1080p. A tile size of 250 was a few seconds slower. A tile size of 50 added an additional minute to the render time per frame.
Thanks for the breakdown. You skipped very fast on the film section, but I realize that you changed the default "blackmann-Harris" to Gaussian, is there a reason for this? BH should work pretty much like Gaussian, but with a little bit more respect for high frequency noise and patterns, in other words, at least as far as I understand, BH should be better (true or not??). also, the Width of the filter is quite important. You let the default 1.5px, it works well, but personally I decrease this a bit to 1.25 or even 1px when I have very fine details to keep them alive, then I add a soften filter in compositor anyway after if needed. this setting is here to prevent aliasing, and it is worth messing up with it sometimes. the guys making pixel art decrease it all the way down and use the box type to keep line completely aliased and pixelly (I never tried though). other point to be aware : the noise threshold should be avoided as much as possible in animation. I extensively tested this, and even with crazy low values, I always end up with area with very noticeable temporal noise. for still, it is very good though. For what I have tested, Fast GI approx will result in about 10% render time boost with 3 steps, and another 10% boost with 2. Pretty good, and almost no change, and interresting bonus : better AO for using in compositor if needed (at least for what I found). Using volumetric will at least almost double your render time, even if you use an emissive shader as volume. probably heavily graphic card dependant, but for me, deactivating rendering tiles is always faster that having it ON. You may need a lot of graphic card memory if you render big though (I have 16GB, never had any memory problem)
Hmmm. Lower shutter speed "decreases motion blur"? I mean. I don't know a lot about blender or rendering. But in photography lower shutter speed would increase motion blur, not reduce it, higher shutter speed would decrease motion blur but some how in Blender's render settings it's the opposite? That seems weird to me.
@DECODEDVFX I see no worries. Like I said I am just starting to learn about blender and rendering. Just wanted to make sure that it wasn't like a "counter" slider like put it low to counter the low shutter or something.
I was not enough informed and I bought a laptop in February, it has 8gb VRAM... 😬 I can render 10 seconds of animation and it crashes... Buy 16gb VRAM or more if you want to create larger animations.
yet another copy paste video with the same exact, surface level shallow afs """""""tricks"""""" to render faster (basic knowledge). The blender youtube scene is cooked. Everything seems to be made only for newcomers. There are almost no advanced tutorials or videos on actually interesting topics.
@@DECODEDVFX nowhere. just sick of getting recommended beginner blender videos, because that's literally all there is. Also, my main complaint is that there is basically no reason to make a "how to render faster in cycles" if you're just gonna make a compilation of basic tips. I could recite the whole video by memory at the first watch, beacuse this same video has been made over and over again over the years by every blender youtuber. This video adds no value. Would be interesting to see maybe a "definitive guide to faster rendering, scene optimization and desnoising, both inside and outside blender" video. Showing stuff like: - baking lights to textures for rough static objects/materials - using render layers, holdouts etc. with different sample values for different parts of the scene - temporal denoising techniques (even using Davinci Resolve's Temporal NR on top of denoised renders to reduce artifacts - compositing EEVEE volumetrics on top of cycles renders, or faking volumetrics in the compositor - using the best AI upscalers and frame interpolation to render (potentially) in a quarter of the time - analyzing scene complexity, baking procedural materials to textures, using the correct shaders etc And these are only a few thing i can come up with on the spot right now. That would be actually useful to intermediates and beginners alike, and actually be original and valuable information
@@ShoryYTP I made one of the oldest comprehensive guides to speeding up cycles almost five years ago. I made this update video after receiving several comments complaining that it was out of date. Damned if you do, damned if you don't.
HUGE SALE! You can save 50% on all my courses until the end of Christmas with the code XMAS -
The Essential Topology Guide -
decoded.gumroad.com/l/ESSENTIALTOPO
Also available on Blender Market - blendermarket.com/products/essentialtopo
The Interior Masterclass -
decoded.gumroad.com/l/interiormasterclass
Also available on Blender Market - blendermarket.com/products/the-interior-masterclass
The Exterior Masterclass -
decoded.gumroad.com/l/exteriormasterclass
Also available on Blender Market - blendermarket.com/products/the-exterior-masterclass
Note: OptiX takes more GPU memory so if you get 'Out of GPU memory' use CUDA instead
You can also run out of GPU memory if you have enabled rendering in the viewport at the same time while rendering the final image. When you have this combination AND you render an animation, in addition performance will drop significantly.
@@karlpelzer9485 Yes, and make sure to select 'Lock Interface' in the Render menu
Nice flex with that 4090 lol
It's a great GPU.
@@DECODEDVFX It really is. I hate myself for giving Nvidia money, but my ability to get things done is effing amazing. I just wish it had more VRAM I bump the limit all the time. WHich is where tiles comes into play.
Wow, I helped me reduce render time from 7 seconds to 4 seconds on Mac. Thanks
According to my experience tiling is also important on big size renders. Let's say you are taking an 8K render with bunch of geometry and textures in the scene, in this case if you dont use tiling the whole frame rendered at once is much slower than multi tile rendering and it might result in crash or not responding status. Leaving it at 2048 with tiling enabled usually works good for me.
in my experience light tree improves render time more often than not ethen when there is not that many lights in the scene
Mixed results for me. I use it sometimes, but I always leave it off in the viewport and it can make things very sluggish.
very timely video, my render settings were bad and i was thinking I needed to buy a new graphics card :) thank you
regarding tiles, gpu is faster with big tiles, cpu is faster with small tiles. if you do a lot of rendering, like a mult animation, maybe it is a good reason to test performance with different tile sizes
That used to be true, but it isn't really the case since cycles X was released.
Before I made this video I tested various tile sizes on CPU. It was always faster to use the default tile size of 2048 when rendering at 1080p.
A tile size of 250 was a few seconds slower. A tile size of 50 added an additional minute to the render time per frame.
@@DECODEDVFX good to know, thanks.
Hey man, really enjoyed your coke Christmas ad reaction. Madness!
Is that Time Limit option in cycles a new feature or did I miss it?
@@sadhappy8860 it's quite old now.
Thanks for the breakdown. You skipped very fast on the film section, but I realize that you changed the default "blackmann-Harris" to Gaussian, is there a reason for this? BH should work pretty much like Gaussian, but with a little bit more respect for high frequency noise and patterns, in other words, at least as far as I understand, BH should be better (true or not??). also, the Width of the filter is quite important. You let the default 1.5px, it works well, but personally I decrease this a bit to 1.25 or even 1px when I have very fine details to keep them alive, then I add a soften filter in compositor anyway after if needed. this setting is here to prevent aliasing, and it is worth messing up with it sometimes. the guys making pixel art decrease it all the way down and use the box type to keep line completely aliased and pixelly (I never tried though).
other point to be aware :
the noise threshold should be avoided as much as possible in animation. I extensively tested this, and even with crazy low values, I always end up with area with very noticeable temporal noise. for still, it is very good though.
For what I have tested, Fast GI approx will result in about 10% render time boost with 3 steps, and another 10% boost with 2. Pretty good, and almost no change, and interresting bonus : better AO for using in compositor if needed (at least for what I found).
Using volumetric will at least almost double your render time, even if you use an emissive shader as volume.
probably heavily graphic card dependant, but for me, deactivating rendering tiles is always faster that having it ON. You may need a lot of graphic card memory if you render big though (I have 16GB, never had any memory problem)
if you have environment fog, turn on light tree
Have to disagree with choosing only GPU. On pretty much all of my renders there's a noticeable speed increase when both GPU and CPU are selected.
Command line still faster?
Hmmm. Lower shutter speed "decreases motion blur"?
I mean. I don't know a lot about blender or rendering. But in photography lower shutter speed would increase motion blur, not reduce it, higher shutter speed would decrease motion blur but some how in Blender's render settings it's the opposite? That seems weird to me.
I misspoke.
@DECODEDVFX I see no worries. Like I said I am just starting to learn about blender and rendering. Just wanted to make sure that it wasn't like a "counter" slider like put it low to counter the low shutter or something.
this may be a silly question, but does any of this apply to apple silicon users?
@@monk333 yes.
I was not enough informed and I bought a laptop in February, it has 8gb VRAM... 😬
I can render 10 seconds of animation and it crashes... Buy 16gb VRAM or more if you want to create larger animations.
❤ GOLD ❤
Tiny tiles produces less noise probably. it is not fact but who knows please give me a feedback.
Tile size shouldn't affect render quality.
Where is the L in the alphabet above the blackboard?
im now questioning the universe!
No idea. I didn't make this scene. It's a blender demo file.
4090.....
Old soup boiled up anew
Half this stuff is fairly new. At least since I last made a video on this topic four years ago. But okay.
yet another copy paste video with the same exact, surface level shallow afs """""""tricks"""""" to render faster (basic knowledge). The blender youtube scene is cooked. Everything seems to be made only for newcomers. There are almost no advanced tutorials or videos on actually interesting topics.
Where was the advertised as an advanced tutorial?
@@DECODEDVFX nowhere. just sick of getting recommended beginner blender videos, because that's literally all there is.
Also, my main complaint is that there is basically no reason to make a "how to render faster in cycles" if you're just gonna make a compilation of basic tips.
I could recite the whole video by memory at the first watch, beacuse this same video has been made over and over again over the years by every blender youtuber. This video adds no value.
Would be interesting to see maybe a "definitive guide to faster rendering, scene optimization and desnoising, both inside and outside blender" video. Showing stuff like:
- baking lights to textures for rough static objects/materials
- using render layers, holdouts etc. with different sample values for different parts of the scene
- temporal denoising techniques (even using Davinci Resolve's Temporal NR on top of denoised renders to reduce artifacts
- compositing EEVEE volumetrics on top of cycles renders, or faking volumetrics in the compositor
- using the best AI upscalers and frame interpolation to render (potentially) in a quarter of the time
- analyzing scene complexity, baking procedural materials to textures, using the correct shaders etc
And these are only a few thing i can come up with on the spot right now. That would be actually useful to intermediates and beginners alike, and actually be original and valuable information
@@ShoryYTP I made one of the oldest comprehensive guides to speeding up cycles almost five years ago. I made this update video after receiving several comments complaining that it was out of date.
Damned if you do, damned if you don't.
@@ShoryYTP do it yourself then lmao. The fuck is this rant