Answers!
In what program are you seeing this issue? After Effects/Fusion etc?
- Nuke
What render settings did you use (Layered? What compression setting (DWAA/ZIP etc?)
- DWAA
What hardware are you on (GPU)?
- 2x 3090 GPUs
Would you mind sharing the exr file?
Sure. Sent it to you on Discord.

If you ...

They would not output at all. I could see them in the Solaris viewport when isolating AOVs, but then nothing upon rendering.

I opened a seen that had previously been made with Karma and Octane wasn't installed when that was made. All the lights that had existed in the scene then don't have the Octane Parms tab. This causes the lights to not work with the light mixer, but still work with Octane. It's very odd.

In short ...

Exported Z pass shows striations throughout when normalizing its values in a compositor.

Base Light IDs will be written fine. Light ID direct and indirect will not be written to file even though they show in the Solaris AOV dropdown.

The Octane Parms in a dome light has to visibility tabs with additional cast shadows and light pass id check box. This is causing Dome Lights to not work with light passes.

Post processing is triggering the scene the render again/restart. As a post process, it should process after the render.

Octane won't use a light mixer if it doesn't have Octane parms already. Can't add octane parms from the shelf tab, so that means recreating existing lights.

Correction, it doesn't work with any LOPs.

Trying to Add or remove ObjParms to an existing camera does nothing.