LuxCoreRender Forums

Introduction

I have added few new options and chages with the aim to improve the Intel OIDN denoiser output. This is a rendering with v2.5:


and this with v2.6:


Albedo AOV new specular reflections and transmissions settings

It is now possible to define how ALBEDO AOV will handle reflections and transmissions:
The is the result of NO_REFLECT_TRANSMIT setting:


This is the result of REFLECT_TRANSMIT setting:


New Intel OIDN plugin option for auxiliary buffers pre-filtering

It is now possible to enable/disable auxiliary buffers pre-filtering:
This is Albedo without/with pre-filtering:


I doubt it is necessary to expose this setting in Blender because having pre-filtering should always be better.


Pixel filtering to preserve details

As some recent test has shown, pixel filtering should be enabled (with path tracing) even when using Intel OIDN:


It can be enabled only for path tracing and not for BiDir because BiDir pixel filtering drives OIDN crazy while it seems to tollerate path tracing pixel filtering. Some further test may be required.

Super cool!

I’ll test it ASAP, having the transmissible option is awesome

I added support in BlendLuxCore, in the denoiser settings in the render properties.

Some test images:
"old" = like 2.5, with albedo being NO_REFLECT_TRANSMIT and prefiltering off
"new" = albedo is REFLECT_TRANSMIT and prefiltering on

It looks good to me.

B.Y.O.B. wrote: ↑Tue Jun 29, 2021 9:59 pm Some test images:
"old" = like 2.5, with albedo being NO_REFLECT_TRANSMIT and prefiltering off
"new" = albedo is REFLECT_TRANSMIT and prefiltering on

Have you tried to re-enable pixel filtering (only for path tracing) even with OIDN ? The difference should be visible on a scene with bump mapping

Pixel filtering was already used with OIDN.
In the Blender addon, it was only disabled when using Bidir or Path + Light Tracing (because light traced caustics are not properly denoised by OIDN when they have pixel filtering).

In the test scene above, pixel filtering is not used because of light tracing.

B.Y.O.B. wrote: ↑Wed Jun 30, 2021 7:10 am Pixel filtering was already used with OIDN.
In the Blender addon, it was only disabled when using Bidir or Path + Light Tracing (because light traced caustics are not properly denoised by OIDN when they have pixel filtering).

In the test scene above, pixel filtering is not used because of light tracing.

With this new addition. Do user have something to setup or it is done internally according to render engine setting.

These new features are enabled by default.

B.Y.O.B. wrote: ↑Wed Jun 30, 2021 8:23 am These new features are enabled by default.

Great

HI, we are experiencing some strange behaviour with Lux 2.6 alpha 0 + oidn 1.4.
In some cases results are worst as with the previous. What are we doing wrong?

albedo reflect+transmit on, treshold 0.5
this is the old luxcore and old oidn
albedo reflect+transmit on, treshold 0.5
this is the old luxcore and old oidn
this one is with higher sampling level:

daros wrote: ↑Fri Jul 02, 2021 11:06 am albedo reflect+transmit on, treshold 0.5

Have you misread the default value ? You should use 0.05, not 0.5.

It is a glossiness threshold used here like on other contexts of LuxCore: it is a roughness threshold under which a glossy material will be considered as specular (i.e. nearly like a mirror and/or glass if it is a transmitting material).