[REQ]: display pathes/pixel

[nlo]

when rendering in production mode or without the statistic information embedded in the image, it would be helpful to get the current state of pathes per pixel.
we typically don't like to render a specific amount of time because it makes a difference in the noise level if one or more computers crash or not in dr mode.
to render up to a certain number of rays per pixel, we need to know which number is ok in terms of noise.
so what we like to do is, keep both numbers at zero and go for lunch
now what would be good, is to know how many rays per pixel have been casted, when we think the image reached an acceptable noise level.
so in case we need to rerender we know the magic number of pathes necessary.

another strategy would be to render only a small region (typically where the noise is the strongest) and take the pathes per pixel from that area.
at the moment, there is no way to get the pathes per pixels in that case.

kind regards, clemens.

[Alan Iglesias]

Hmmm... I typically pre-render a representative frame or two, note the PPP number that has an acceptable amount of noise, enter it in, hit render and go to lunch!

Yes, it might be nice to have something more automatic. Since noise amount is such a subjective decision (that would of course differ greatly depending if the animation was a motion/lighting test, or somnething more final) I wonder if there is a way to automate it... If there was a way to actually measure noise in a finished render (??) that would be a cool way to pre-set it...

-Alan

[particlerealities]

I would like the "XX paths/pixel reached" to continue to be updated when the "Draw Region" mode is active in the ActiveShade viewport. That would allow for faster feedback of acceptable levels of noise in selected problem areas.

[Delineate]

Good idea.

I would like the "XX paths/pixel reached" to continue to be updated when the "Draw Region" mode is active in the ActiveShade viewport. That would allow for faster feedback of acceptable levels of noise in selected problem areas.

[vlado]

We can't do that for the time being though. We could put that information somewhere in the ActiveShade renderer dialog or in the V-Ray messages window.

Best regards,
Vlado

[3LP]

Nice!

This would be realy handy Vlado!

Stan