OTOY Forums

Hi
2022.1.1 R5
Was there a bug where Object Layer Colour doesn't render? Did a search and didn't find much.
I can see it in the LV, and in PV when I click the "layer" tab, then the radio button for "single pass"
But in the file on disk, opening in AE or Pshop, it's black.
Rendering passes to separate files/folders.

Seems to work OK if I set up a new file and add a cube and add new render settings, but on all my existing files and render settings, it's coming out black.
I can't use cMnn because particles/clones complicate getting clean mattes. Object layer colour is much better in this instance but I can't make it render out.
Any help appreciated.

I have also noticed, that when using child takes (for example, to render out various takes of motion or various still frames) that adding AOVs to the parent take does not add them to the child takes. Child takes should inherit all parent render properties. In old versions, like 2020, back when AOVs were radio buttons, setting passes in a parent render setting always flowed down when children render settings were set to "inherit from parent". The new AOV system seems to not work. But of course, Redshift (which has a similar "list" of AOVs and no doubt where Octane took inspiration from for new AOV setup) works fine for children settings to inherit from parent.

Is this something that can be looked at for future releases? Takes system is absolutely integral to many people's workflows, and if render parents AOVs can't flow down to children this can leave a LOT of room for oversight and mistakes.

And circling back, any help on black object layer color output appreciated please.
Thanks

Deleted all render settings and redid
Still can't get an RGB Object layer colour pass out
But weirdly I can access the R, G or B matte via Extractor effect in AE.
But the RGB is black.
So what if you want to use a channel combiner or set mattes to get a matte of R+G, for example, in AE? You can't do this if the passes are coming out as exr mattes rather than colours in RGB.

The main use people do here is having various objects with octane object tags, and object layer color set to 100% R, or G, or B. Basically traditional RGB mattes. Really good for putting a group of objects under one matte, instead of using crypto and selecting a ton of objects or materials, and if using clones that could get super complicated. RGB via Ocol really simplifies.

At what point did Ocol stop being an rgb pass?
Why does it show up as rgb colours in LV but renders from PV as exr layers needing EXtractoR to pull out?

Is there a way to get back that kind of functionality?

Cheers

Bueller
Why doesn't the Ocol pass render in RGB any more, and when did that happen?
Is there a way to make the Ocol pass render in RGB instead of it appearing black visually and needing EXtractoR in AE to pull out the various mattes/layers.

There are so many releases and notes to read on each one I am not sure if this was an announced change or I am seeing a bug in 2022.1.1 R5.
Could not see a specific fix or citation in the following version for this so we have not updated yet (middle of project render).

Thanks

I'm suck here too - on a DEADLINE! FFS

ScottSub wrote:Bueller
Why doesn't the Ocol pass render in RGB any more, and when did that happen?
Is there a way to make the Ocol pass render in RGB instead of it appearing black visually and needing EXtractoR in AE to pull out the various mattes/layers.

There are so many releases and notes to read on each one I am not sure if this was an announced change or I am seeing a bug in 2022.1.1 R5.
Could not see a specific fix or citation in the following version for this so we have not updated yet (middle of project render).

Thanks

Could you please send e-mail to support for help? Or send me your project!