two drivers produced the same output path. AOV merging is only supported using a single driver node: "defaultArnoldDriver@driver_exr_denoise", "defaultArnoldDriver@driver_exr.RGBA" //

[Anonymous]

Hola all,

I preparing for a major re-rendering campaign and wondering what to do in order to get rid of the two drivers error message, I must admit, I do not fully understand what it means.

I am using

N

RGBA

z

Diffuse Albedo

for an interior scene made with arnold lights (one IES group) and AistandardMaterials.

Another one while I am at it, it has been said that one should not use Optix for final renders, wondering why and how does one make sure it is not on? I presume it is the Optix Denoiser, Denoise Beauty AOV tickbox?

Thanks for the support!

Rob

[Stephen.Blair]

You have two EXR drivers, and Merge AOVs is enabled for both drivers. You can't do that.

[Anonymous]

Stephen,

With you onboard this one should be a doodle, er, how do I get rid of the extra bugger?

Cheers,

Rob

[Stephen.Blair]

You must have something like this:

exr instead of <exr> creates a second driver node in the scene

Set the driver back to <exr>

[Anonymous]

Stephen,

i went through the AOV's and could not spot one like that exr. So I removed all of them added them back carefully while checking all of the tabs. No joy!

I did one frame render to see what error messages would I get and I got the same error again.

I deleted all four AOV's one by one, rendered, without finding one that is clearly causing this error message.

Then I added RGBA first and then Diff, Z and finally N.

I did a full frame render without the error message popping up.

Go figure...

Tonight's render might prove whether the rootcause was sorted.

Until then, thanks for the help once again!

Cheers,

Rob

[Stephen.Blair]

Here's some things I would do:

• Get an debug Arnold log for a render (render with aa=-3 so it's fast).
• Export an ASS file and then look at the outputs in the option node.
• Use the Node Editor to look at what aiAOV nodes are connected to what aiAOVDriver nodes

[Anonymous]

Stephen,

I sort of understand the aim of your 3 bullet points but I don't know how to follow them. Is the Debug Arnold log in the Render Settings diagnostics?

I had what first appeared to be a clean render run which produced 26 .EXRs in 9 hours however when I setout to denoice them I got an error:

Denoising RGBA Could not find AOV with source RGBA and filter variance_filter

The .exr did not appear denoiced either.

Cheers,

rob

[koaleksa]

Hi Roope,

You have optix denoiser turned on on RGBA AOV which is causing problems.

Turn it off if you want to be able to output multilayer exrs (optix does not support merged AOVs output).

In version 3.0.0 of mtoa this checkbox was labeled simply "Denoise" which may have confuzed you it is related to noice (other, CPU denoiser) which you are trying to figure out.

For noice to work, disable Optix denoiser on all AOVs, enable Merge AOVs in render settings Common tab, enable "Output denoising AOVs" (or "Output Variance AOV" as it was called in mtoa 3.0.0) in AOVs tab, and make sure N, Z and defuse_albedo AOVs are being outputted.

Hope this helps.

Cheers