The iterations is an Iray thing (not sure about other unbiased renders like reality) But it is not a 3Delight thing, which is why you don't see it.
1. Reality is NOT a renderer...it's an interpreter/translator for Luxrender (the renderer).
2. Yeah, they've got them, but more often than not, they are called something else. Luxrender calls them passes. Even 3Delight has them...if you do progressive rendering. Each time through the image is roughly the same as an iteration. But without using Progressive, you are only doing a single pass, so I guess you can say it's just doing 1 iteration, so no need to track those separately.
ok I took all the settings and info you guys gave me and applied them. The graininess is gone, not sure just what settings solved it but heres a test render with those settings. While DS is not telling me how many iterations were used, it did go from a 2-5 min render to exactly 47 mins & 49 secs. Btw, this is NOT a wip, this is just a test for me to understand options and settins within DS.
That's because your shading rate was set to 0.01, which is very time consuming.
I usually set the shading rate to 0.8 for test renders, and 0.1 for the final renders.
Comments
.
.
.
The iterations is an Iray thing (not sure about other unbiased renders like reality) But it is not a 3Delight thing, which is why you don't see it.
.
1. Reality is NOT a renderer...it's an interpreter/translator for Luxrender (the renderer).
2. Yeah, they've got them, but more often than not, they are called something else. Luxrender calls them passes. Even 3Delight has them...if you do progressive rendering. Each time through the image is roughly the same as an iteration. But without using Progressive, you are only doing a single pass, so I guess you can say it's just doing 1 iteration, so no need to track those separately.
That's because your shading rate was set to 0.01, which is very time consuming.
I usually set the shading rate to 0.8 for test renders, and 0.1 for the final renders.
Got it. Thanks