Cycles AOV Output

[aurora]

Hola!
Does anyone know how to setup Cycles Custom AOV Output? Have tried a few things without success.
Cheers!

[Alex Fuller]

Hey Aurora,

The way I intended it was to make the data-type as `aovc myColorAOV` and `aovv myValueAOV`  similar to LightGroups, and then match the name to an `aov_output` node and do a separate ShaderAssignment to the object. You should have the attribute `cycles:aov:myColorAOV` or `cycles:aov:myValueAOV` assigned.

There was a bug pre-Cycles X where only SVM was supported and OSL didn't work with this:

https://developer.blender.org/T73266

I just did a test here with both OSL and SVM and I can't get it to work anymore so I'll go digging and fix this one, at least for SVM.

Cheers

[Alex Fuller]

I got a fix here: https://github.com/GafferHQ/gaffer/pull/5044

Unfortunately the Blender developers haven't addressed getting custom shader AOVs to function in OSL mode yet, only SVM.

[aurora]

Thank you Alex. Looking forward to the new release with this fix.

A

[statix vfx]

Hi Alex and Aurora,

Have there been any updates to this ? Is is it feasable to render custom AOVs in 1.3.2 ?

I have a basic setup that looks like it should work, but returns all black.

stx

[aurora]

Do you have a specific example you can show?
Working as expected here:

[Theodor Flo-Groeneboom]

Turns out of im rendering with SVN instead of OSL it works.

[Vahan Sosoyan]

Hi Alex,

Any chance to get this working with OSL? 

I'm using Gaffer 1.3.4.0 

Thanks,

[Murray Stevenson]

Hey Vahan,

Unfortunately I'm fairly sure this is a limitation in Cycles itself, and from the looks of the Blender issue Alex linked earlier in the thread, it's still not possible. I've tried in a recent Blender 4.0 alpha build, and custom AOVs don't work in OSL mode there either...

Cheers,

M