Blender 3.0 - Cycles X Comparison & BEST Render Settings

today we're going to render tests for the new cycles x and blender 3.0 we'll be comparing full feature scenes animations and more including the new sampling features cyclezx and the updated open image denoiser this video is sponsored by msi so in this video we'll be covering viewport performance do noise comparisons architectural renderings product running stylized scenes animated sequences hair simulations volumetrics and subsurface scattering i'm just going to tell you the numbers right now overall things are two to eight times faster depending on the type of scene and then if you use open image denoise that can reduce it to mere seconds meaning it's sometimes hundreds times faster depending on the type of scene you have however this video is more than just a quick number i actually want to deep dive into each type of scene and see what types of scenes are really benefiting from this new update and do comparisons compared to the previous versions of blender with blender 3.0 we also have a new sampling system so we're going to talk about that and the noise threshold and what that means and what that looks like visually we'll be focusing on render percentage increases not just render times that way hopefully this is applicable to a wider range of hardware for the hardware i'll be using i'll be using the msi sponsored provided ws76 workstation despite how light and tiny it is it is actually very powerful which is why i chose to render on this computer my desktop has a 2070 rtx card which is actually meant for gaming so it's the 3000 series whereas the rtx cards actually meant for rendering with this laptop it's been built to be optimized for nvidia studio overall so i'm hoping that i get a bit more consistent render performance out of it as opposed to my own computer which is kind of cobbled together with some parts that are outdated and it might not be as reliable for render results with that being said let's dive in so a lot of people talked about cycles x but they didn't talk about the new sampling system so if we twirl this down here you see that we have viewport render in advance so i'm going to go ahead twirl down render a lot of these settings apply to the viewport as well so we have this noise threshold option on here by default i'm going to go ahead and toggle that off for now and you'll see that this looks a lot more like what we're used to with sampling you enter the amount of samples you want and it renders until that's done no matter how long it takes but below we have a time limit here if you leave this at zero it will just active as it is disabled but we can go ahead and set 60 seconds here if we want and it won't render past 60 seconds so you could just set a high sample number and limit it by time limit per frame so this is incredibly useful for animations if you don't want a frame to go over 30 second renders you need to set this to 10 000 up here and then go ahead and set this to 30 seconds and then it'll just kind of render out and stop at 30 seconds per frame up here if we toggle on noise threshold you see a couple options change so the noise threshold here is a number that kind of lets you determine how much noise you're willing to allow in the image and then it is going to render between the minimum and maximum number of samples so that it will determine what is best for the noise level in your scene now i know that this number is kind of hard to tell you know what does a noise threshold of 0.01 look like so here's a couple examples renders from a real world scene i have at different noise threshold settings to give you an idea of what those look like and then of course down here we have our denoise option which has been updated to 1.4 open image denoise so we'll go ahead check this on twirl this down we have different options here now we have the denoiser open image denoise we have our pass options which you want albedo and normal on and then you have a pre-filter which you can change to fast or accurate i'm leaving mine on accurate so interesting enough when i was testing out tile sizes i noticed that when you know in blender 2.9 things traditionally rendered better around 256 or 512 for my tile samples that here in blender 3.0 that larger tile samples rendered better the default settings are set to 2048 i found for myself and my render resolution that 1080 was working best so maybe play with those tile samples and try some larger ones out and see if those are working better for you in 3.0 i wanted to test adapt to sampling versus normal sampling rates and in my test i found it to be a tiny bit slower but where i found adaptive sampling to be more helpful was determining the sample rate i should be rendering at i'm a bit curious to see this in more of a variety of scenes when i tested it on my own these were the results but i'd like to hear in the comments below if you've seen more success with adaptive sampling and save time i wanted to test cuda versus optics rendering within blender 3.0 and the results were that it was a bit faster at 174 whereas in 2.9 i remember getting around 140 i'm not sure if this is with blender 3.0 or if it's with the nvidia studio drivers but it certainly seems to be also speeding up renders even a bit more than before i wanted to compare denoising to non-denoising render times in blender 3.0 and in my experiments trying to figure out what i felt were good enough results to share online with the denoising artifacts i found that i was saving about 400 percent time which is about what i was getting in 2.9 but the advantage in 3.0 is that it's been updated to the 1.4 denoiser which now yields better results with accurate sample rendering and a little bit more normal details which you can see here if i zoom in and compare this blender 2 comparison to the blender 3 comparison using the new optics denoiser update now according to the blender developer notes the viewport performance is better in 3.0 when working with high kind of volume meshes so heavily detailed single meshes are supposed to perform better in the viewport so what i did is a couple viewport tests here i have the one test where i just kind of played through one of my animated scenes with a lot of particles that usually caused me a lot of lag and i was kind of surprised to see that in blender 2 i was actually getting about one extra frame per second though that's a pretty minut result so not really worth mentioning there it is worth noting that when viewing live render mode in cycles that 3.0 greatly outperformed 2.0 and this is kind of something hard to show in a video it's something more you feel as you're moving around but it was lagging less and loading a lot quicker and then also i wanted to test out that kind of high volume mesh so what i've made here is a mega cube and this mega cube has been subdivided an insane amount of time so that we have millions of vertices and you can see here in the 2.0 comparison versus the 3.0 comparison that it's entering edit mode quicker and then if i take a circle select and kind of drag across here you can see that it's lagging a lot more in 2.0 whereas in 3.0 it's picking up a lot more of those vertices so definitely some improvements there and the performance that'll be great if you do a lot of sculpting i also just want to take a moment and say how great this laptop handled these renders i'm always concerned with thermals when working off a laptop but the ventilation on this thing is pretty great and actually handled everything really well so next up i wanted to test what it was like rendering kind of product comparison so if you do like product rendering videos and things like that and you'll notice that it's only about a 30 increase on 3.0 now first of all let me just say that 30 is quite a bit but compared to the kind of two to eight times like faster render ranges we could be getting it doesn't seem like that much so i dug into the dev notes and into the blogs a bit and it seems that a large portion of cycles x speed is actually for more complex scenes specifically when it comes to kind of hair simulations and things like that but also light bounces so light bounces you know are going to be much more prevalent in architectural visualizations or kind of like caves and volumetric scenes whereas in product renderings when you just have a single object or two out in the open you're not measuring as many light rays bouncing around so i think that's why the render times here although better are not as extreme so next up i wanted to actually test out that arc kind of vis rendering and see how it did with more light bounces around in the scene now this is one of my stylized rooms and i still have some open walls here so there's kind of less light bounces than there could be but you see that it brought it up to 271 percent bringing the rim rumor time down from 211 to 48 seconds so you can see that there's quite a big increase there as there are more light bounces that it actually saves you a lot more render time really impressive now the hair was a huge increase coming in at 383 percent going from 421 to 108 and it just rendered so much faster but i think what's most notable here is that not only did it render faster but where really saved a ton of time was in the bvh loading process so it actually got to rendering much much quicker and i think that's really important to note because i've had a lot of scenes getting hung up when i'm trying to do hair on the scene where it just won't even start rendering it just gets hung up there forever in 2.9 but in 3.0 that's much better and it loaded in much quicker now volumetrics are where i saw the biggest increase coming in at 446 percent coming down from eight minutes and 34 seconds to one minute and 55 seconds and it's also worth noting that in this scene this scene is almost entirely encapsulated so it's in a cave so there's a lot of kind of light bounces around there even though this is really low poly simple geometry you can see that with kind of the light bounces and the volumetrics that it really kind of ranked up the render time and on 3.0 we saw a huge time saving increase now one of the tests subsurface scattering as we all know that can be very time consuming to render now it's worth noting that 3.0 not only has some improvements in terms of its render time with subsurface scattering but also the material itself has more options now and looks a little bit better in my opinion and here we had 427 percent difference going down from two minutes and four seconds to just 29 seconds to render out the scene with my character the ws-76 workstation is built for those who need every ounce of power you can get from your computer i never thought i'd say this but i may start rendering on this instead of my desktop i measured thermals during my runner test and i was impressed at how well it did it has an intel i9 processor an nvidia rtx a5000 graphics card support for omniverse drivers plenty of ram for large scenes wi-fi 6e 99.9 watt per hour battery life this is a top of the line workstation for professionals if you're interested in something cheaper for a hobby i'll list some of those in the description as well as msi has a wide range of options that accommodate all creatives as usual i'm so grateful for you watching and i love seeing what you create tag me in your creations and stay up to date on instagram and twitter at southern shoddy you

Channel: SouthernShotty

Views: 31,387

Keywords: blender 3.0, blender, cycles x, blender cycles x, blender 3.0 cycles, cycles, blender 3d, blender cycles, blender 3.0 tutorial, cycles x blender, blender 3.0 beta - cycles, blender 3, render, blender tutorial, blender 3.0 alpha, cyclesx, blender 3.0 cycles x, cycles render, cycles x render, blender 2.9, comparison, blender 2.93 cycles vs blender 3.0 cycles x, blender comparison, cycles x comparison, blender comparison 2021, blender 2.92, render comparisons

Id: AXr3HocHVGE

Length: 10min 48sec (648 seconds)

Published: Fri Dec 10 2021