Do aov use MRT now?

This would make it a lot easier to implement blender into a pipeline, and getting renders to compers working in other software like Nuke, fusion etc.

No activity for more than a week. As per the tracker policy we assume the issue is gone and can be closed.

Looks like the defaults were broken when the new socket builder was used: rB5ef5a9fc2466. I tried going through the diff again to spot other differences but this seems like the only node that got lost in translation.

would this be used with stuff like FSR or DLSS?

Set as first good issue as there is already some work done. Should just be extended as noted in the patch

Passing meta data using the compositor isn't supported yet. The metadata that are set are read from the scene afterwards.
There is an experiment that would add this, but isn't ready yet. D14924: Compositor Use file meta data in composior.

thanks for the fix! this is working as expected on latest build.

@Philipp Oeser (lichtwerk)
From Natron 2.4.3 I get from the info tab:

N.xyZ, P.xyZ

But from the fileInfo button:

Seems like blender writes these with "XYZ" (so all capitals)

@Brecht Van Lommel (brecht), @Sergey Sharybin (sergey), @Jeroen Bakker (jbakker), any of you guys has an idea about those passes names/what's exactly happening here?

Just to clarify, how should it look like?

No, the problem was that data passes were being written twice, and that included the Cryptomatte pass. If you look at the matte pass in a version without the fix, its values are over 1.

Intresting. I can confirm that this bug is fixed in the current 3.2 Beta.

Fixed by rB1b566b70c1636c9b95f55e2fc84ef4f714306d19.

Hm, can confirm actually.
Natron or Krita can show the normal layer without problems.

Could you also check the Saving File Extensions option in the render tab of the specific scene. This could perhaps influence this as intended behavior.