Cfrgtkky

This is NOT about asking how to speed up cycles renders. I am just confused to why a scene has taken so long to render.

Here we go:

I have a camera (WOW) looking up into treetops. Pretty simple. These leaves have subsurface scattering with a black/white texture to apply some change in the colour/subsurface. The trees are a bunch of vertices with a skin modifier, textured. Some simple volumetric clouds. I have a weak volumetrics box to apply a light beam effect surrounding my camera reaching to just above the trees.

For the render settings, I used CPU (I know, kill me. But I started one on GPU and got different results and was just as slow!). Rendered at 4,096 samples at 2,800 x 1,800 (W x H).

I was rendering on a single iMac, which in the past, has done more complex scenes with higher settings within 6 hours easy.

Now for the render time:

99 hours and 52 minutes.

NEARLY 100 HOURS!!! Is it me or is that WAY too long!?!

I would upload the image but it is over 2mb :(

Any reasons into why it is taking so long would be grateful.

I'm not too sure about the implementation of volumetrics in Cycles, but roughly speaking:

1. without volumetrics, a ray direction must be evaluated only once every time it hits a surface. So the ray virtually travels freely (no computations) through the empty space, then it hits a surface and (if it hasn't bounced back and forth too many times, depending on your "Bounces" settings), it triggers a single new calculation to decide where the ray should move next. Repeat a few times (up to a dozen) until it finally hits a light or the sky.




2. with volumetrics, every little interval of space the ray travels, the path tracer has to flip a coin to decide whether it will be scattered or not (until it finally gets scattered enough times to reach the "Volumetric bounces" cap). So along its trip there's a LOT of calculations involved.

If your scene is covered for the most part by volumetric regions, this will require a lot of extra calculation per each single ray (and you are casting 20 BILLION rays in your setup!).

Subsurface scattering is also very computationally intense.

So the reason why your render takes so long is that, even if your geometry and your shaders are "simple" (meaning: it took not too long for you to set them up), they are all over the place and are requiring a ton of calculations per ray (meaning: it takes a lot for the renderer to evaluate them)!