Original subtitles

I hope it was a lot of fun rather than frustration to use the Cycles path tracing right within

the viewport, there is definitely a performance gradient depending on the gpu.

anyway, denoising should help with lowering the render times greatly, so we have the denoising

turned on.

and as for the light bounces, I think for the final render we can crank it up ever so

slightly, it will make a minor visual difference if any, but anyway we can do it.

than as a precation to not lose the precious raytraced lighting details I usually increase

the indirect light clamping amount, this is my kind of personal superstition in Cycles

because the default value of 10 more often than not is no different than 50 or 100, the

indirect light intensities or values pretty rarely go above the threshold of 10 anyway,

so nothing really gets clamped, but if it was, it would look like that.

see?

probably that's why I feel that typing in 50 there is safer.

0 completely removes the limit so feel free to with 0 instead if you feel like it.

filter glossy at its default value...

what else do we have here worth talking about?

the number of samples for the final render can obviously be slightly more ambitious,

256.

currently the resolution is set to 1920 by 816 wide, the percentage field can be used

to increase or decrease this amount.

I think we should be good to go, we can hit this render button!

oh yes :) we will wrap it up here and have a look at the compositor and where we can

take this lighting setup in the next tutorial.

it'll be all about taking this scene-referred lighting information that we are rendering

out currently and passing it over to the Blender compositor, adding post-processing to it,

maybe color grading it a bit to extend our Cinematic Lighting workflow into the post-processing

zone ever so slightly.

and now let's do a quick recap.