Clouds Test

[Kadri]

Same 100x56 image took 16:51 to finish(Still/Very high). That is quite a difference.
Your original would take probably at least 16 hour or so to render. With my computer of course.
I used 7 threads for example...
I would take out one cloud layer if you can-want of course.

[yossam]

You were right...........I didn't wait long enough. I didn't see the first dot until 5 minutes into the render. The pic below is at .25 detail and 2AA. It took 13 minutes to render on a 16 core i7(8 physical). Is defer atmo on by default? Anyway, as the old saying goes,go big or go home. I'm gonna try a render at 2K and .6 detail and 6AA...........see you tomorrow some time. 

[Kadri]

The same very high render at that small size with only one cloud was very fast by the way 01:51 .

[bobbystahr]

You were right...........I didn't wait long enough. I didn't see the first dot until 5 minutes into the render. The pic below is at .25 detail and 2AA. It took 13 minutes to render on a 16 core i7(8 physical). Is defer atmo on by default? Anyway, as the old saying goes,go big or go home. I'm gonna try a render at 2K and .6 detail and 6AA...........see you tomorrow some time. 

Heh heh, no doubt. Although I've been noticing some speed ups when I have tried clouds I pay the price....it's like crack for terrain artists ....

[yossam]

Wasn't as bad as I thought it was going to be................almost 5 hrs.    Render was at .65 detail and 6 AA and GI was very high on the clouds. No post except conversion to 8 bit.

[DannyG]

The voxels at 29 Million & defer checked set with quality is over 1 are whats bumping the render time. Thats excessive

[yossam]

That's why I asked if defer was supposed to be checked...............default was checked. All I did was create the cloud layers and rendered. 

[AP]

Curious as to what would be the preferred voxel count?

[yossam]

Me 2.....................

[Matt]

We don't know what the ideal voxel count is. It is going to depend on the shape and density of your clouds, and other parts of the scene affect how long it takes to calculate lighting for the voxels too.

The default in the Beta is 30 million. Sometimes you can use smaller numbers without seeing any difference. But sometimes you need to use more, particularly with clouds that have a very high "cloud density".

Matt

[Matt]

For most still renders, Cloud GI quality of "Still / Very high" is overkill. Your renders will go much faster if you reduce this to "Still / Medium", and in many scenes you won't notice the difference.

Matt

[yossam]

Matt,


Is defer atmo supposed to be checked or not at default?

[AP]

Alright, so voxel count is trial and error. Noted.

[Oshyan]

Yes, Defer Atmo is intended to be enabled by default now. This does mean that your renderer Antialiasing then affects cloud quality! The Quality slider in the cloud layer is a relative quality adjuster that operates with the number of AA samples to determine final cloud quality (noise level). If you need to use high AA, for example 6 or above, you might want to reduce cloud quality a bit to compensate (unless you find that the cloud still renders noisy). Just remember that AA4-6 or so is usually adequate for *cloud only* scenes with cloud quality 1 (with Defer enabled).

- Oshyan

[Mr_Lamppost]

Handy to know.