Compositor AOV Output issues Tweet

[J.C]

Hi,

1. The naming of compositor Output node should be named "Output AOVs" as it is now in Standalone. In Blender this is "Output AOV group Output".
2. There are Projection, Transform, Texture nodes that should not appear in add menu when editing in Compositor nodes.

[jobigoud]

2. There are Projection, Transform, Texture nodes that should not appear in add menu when editing in Compositor nodes.

These can be used with the `Texture` Output AOV layer in 2024.1.

[linograndiotoy]

Hi,

1. The naming of compositor Output node should be named "Output AOVs" as it is now in Standalone. In Blender this is "Output AOV group Output".

That's the naming in Standalone:

That's the naming in Blender:

Node names are exactly the same.

[J.C]

Ok, my mistake, there is no Output AOVs node but "Output AOVs" input in render target node.

The naming for output is a unnecessary name dubling. We don't have this in Standalone. The last node is "Output AOV group" which is connected to "Output AOVs" input.
In Blender instead of naming Output node "Output AOV group Output" I would call it "Compositor Output" as we are in Compositor window. It should follow the general rule used in Blender eg. in material we have "Material" output" in world we have "World output" etc.

The naming should go like this:
Output AOV group out > Compositor out
Output AOV group Output > Compositor output
OutpuAOVGroup > Output AOVs

[linograndiotoy]

Yes, that makes sense.

[linograndiotoy]

Actually changing the name is going to create some back-compatibility issues that will need to be solved to make it happen.