In past versions of the plugin both the beauty pass and the denoised beauty would be exported to snapshots. Currently, when using the DenoisedPathTracer Renderer only denoised beauties are outputted to snapshots. The option the Save beauty pass within the Denoiser Tab only applies to the beauty .pfm.There are a multitude of benefits from having the option to still export the noisy snapshots.
1) #33 shows that denoising behaviour is mixed and that when using the Denoise Current Render button both the noisy and denoised beauty are snapshotted. Ideally we would want consistency with how denoising works.
2) The options listed within the Denoiser Tab lack clarification as to what they do. Expanding the visible descriptions or adding tooltips would help clear things up.
3) Disabling or redirecting inbuilt functionality without having an option to retain defaults and to export the denoised output with a suffix, as was done in the past with .denoised, should be avoided.
Tested on
Chunky 2.4.0with #30In past versions of the plugin both the beauty pass and the denoised beauty would be exported to
snapshots. Currently, when using theDenoisedPathTracerRenderer only denoised beauties are outputted tosnapshots. The option theSave beauty passwithin theDenoiser Tabonly applies to the beauty.pfm.There are a multitude of benefits from having the option to still export the noisy snapshots.1) #33 shows that denoising behaviour is mixed and that when using the
Denoise Current Renderbutton both the noisy and denoised beauty are snapshotted. Ideally we would want consistency with how denoising works.2) The options listed within the
Denoiser Tablack clarification as to what they do. Expanding the visible descriptions or adding tooltips would help clear things up.3) Disabling or redirecting inbuilt functionality without having an option to retain defaults and to export the denoised output with a suffix, as was done in the past with
.denoised, should be avoided.