normal render
octane 2024.1 r3
4090 565.90
denoiser darkens images with custom bokeh
Moderators: ChrisHekman, aoktar
Forum rules
Before posting a bug report, please check the following:
1. That the issue has not already been disclosed
2. That the issue is specific to this plugin, and not Octane in general (Try reproducing it in Standalone)
Bugs related to the Octane Engine itself should be posted into the Standalone Support sub-forum.
All bug reports should include the information below, along with a detailed description of the issue and steps to reproduce it.
A. Operating System, including version (i.e. Win 7, OSX 10.11.2, Ubuntu 14.04, etc.)
B. Graphics Card(s) model (i.e. GTX 580 - 3GB, TITAN, etc.)
C. RAM Capacity (i.e. 6 GB)
D. Nvidia driver version (i.e. 7.50, 7.5.22)
E. OctaneRender Standalone version, if installed (i.e. 2.24.2, 2.23, etc.)
F. OctaneRender plugin version (i.e. v2.25 - 2.21)
G. Host application version, including build number if available (i.e. 3ds Max 2016 Build 18.0)
H. A detailed description of the issue and steps to reproduce it (Include Screenshots or video capture), as well as an example scene if applicable.
I. Copies of the Octane Log window and Console window outputs (full text attached as a file to your post is recommended).
Please note that reports of issues inside existing threads will be ignored/removed, and reports may be closed if the reporter does not respond to subsequent queries in the thread.
Before posting a bug report, please check the following:
1. That the issue has not already been disclosed
2. That the issue is specific to this plugin, and not Octane in general (Try reproducing it in Standalone)
Bugs related to the Octane Engine itself should be posted into the Standalone Support sub-forum.
All bug reports should include the information below, along with a detailed description of the issue and steps to reproduce it.
A. Operating System, including version (i.e. Win 7, OSX 10.11.2, Ubuntu 14.04, etc.)
B. Graphics Card(s) model (i.e. GTX 580 - 3GB, TITAN, etc.)
C. RAM Capacity (i.e. 6 GB)
D. Nvidia driver version (i.e. 7.50, 7.5.22)
E. OctaneRender Standalone version, if installed (i.e. 2.24.2, 2.23, etc.)
F. OctaneRender plugin version (i.e. v2.25 - 2.21)
G. Host application version, including build number if available (i.e. 3ds Max 2016 Build 18.0)
H. A detailed description of the issue and steps to reproduce it (Include Screenshots or video capture), as well as an example scene if applicable.
I. Copies of the Octane Log window and Console window outputs (full text attached as a file to your post is recommended).
Please note that reports of issues inside existing threads will be ignored/removed, and reports may be closed if the reporter does not respond to subsequent queries in the thread.
If a universal camera is used with a custom depth of field bokeh aperture texture, enabling the denoiser will cause the image to render darker than without it.
normal render denoised render c4d 2025.1.2
octane 2024.1 r3
4090 565.90
normal render denoised render c4d 2025.1.2
octane 2024.1 r3
4090 565.90
- Attachments
-
- denoisebrightness.zip
- (5.23 MiB) Downloaded 538 times
It's likely not a "darkening" issue/bug in the "pictorial exposure" sense, but simply the byproduct of denoising on "poorly sampled" output from the renderer. In other words, the rendered output requires more samples and optimizations.
A denoiser, any, relies on sampling optimization to "do its job properly", otherwise results can look unsatisfactory or "funky".
This Octane Sampling page goes in more details when it comes to kernel sampling and project file optimizations. There are some "techniques" beyond the Kernel settings.
Edit: the link with the "Custom bokeh" is sampling related. As any element during rendering is not sampled equally, some elements will be "more difficult to samples efficiently". This is why there are "best practices" when it comes to sampling optimization, i.e. as avoiding this and that (things that will be more tricky to efficiently samples).
A denoiser, any, relies on sampling optimization to "do its job properly", otherwise results can look unsatisfactory or "funky".
This Octane Sampling page goes in more details when it comes to kernel sampling and project file optimizations. There are some "techniques" beyond the Kernel settings.
Edit: the link with the "Custom bokeh" is sampling related. As any element during rendering is not sampled equally, some elements will be "more difficult to samples efficiently". This is why there are "best practices" when it comes to sampling optimization, i.e. as avoiding this and that (things that will be more tricky to efficiently samples).
To complement, one denoiser may "perform" better than the other in certain situations. If this was Open Image Denoise, then it would be judicious to test Octane's native denoiser.
This demo from the suggested page is the latter (Octane's)
This demo from the suggested page is the latter (Octane's)
This is unrelated to samples, the full final shots rendered here are on 8000 samples and render cleanly with no noise. They go darker. The images attached to this bug report use fewer samples to show the problem quickly.
It is literally a darkening bug caused by the denoiser.
It is literally a darkening bug caused by the denoiser.
In the absence of any further information (required for proper diagnosis), it was speculatively suggested as such (hence the "likely").
With the newly provided information, it is indeed suggesting a core bug or flaw.
However, at 8000 samples on a relatively lightweight project file, the "normal" (undenoised) render output seems more noisy than expected.
Circling back to sampling optimizations, which includes materials (e.g. gaussian spectrum instead of RGB color node), post processing, etc. or the texture bokeh file, perhaps?
As a suggestive workaround: it should be possible to reproduce (close enough) the result of that bokeh texture file via the Universal Camera, given all the options, covering a vast range of "bokeh renditions".
With the newly provided information, it is indeed suggesting a core bug or flaw.
However, at 8000 samples on a relatively lightweight project file, the "normal" (undenoised) render output seems more noisy than expected.
Circling back to sampling optimizations, which includes materials (e.g. gaussian spectrum instead of RGB color node), post processing, etc. or the texture bokeh file, perhaps?
As a suggestive workaround: it should be possible to reproduce (close enough) the result of that bokeh texture file via the Universal Camera, given all the options, covering a vast range of "bokeh renditions".
