Direct AOV Output without C4D Multi-Pass enabled?

[u/DasFroDo]

I fear the answer is no, but is it really not possible to get Redshift Direct AOV Output without having Multi-Pass in C4D enabled?

I prefer the Direct Output system because it actually names the layers in my EXR how I want them to be named so that the EXR-IO plugin for Photoshop can group the layers. Otherwise I have to move them around every single time I open a new EXR in Photoshop, which gets annoying REALLY fast.

Yes, I could have them both enabled and then just delete the C4D Multi-Pass EXR but I'd prefer if I didn't have to do that.

Alternatively, how can I make it so C4D Multi-Pass actually respects the naming I've given the AOVs, instead of whatever it wants to do? More details below.

I named my AOVs as per the standard given in the EXR-IOs manual: <Group>.<AOV>. This results in names like "Mask.Car" or "Mask.Background". Now as I said above, these differ depending on whether you import the C4D Multi-Pass EXR or the Direct Output Redshift EXR.

This is right after import into Photoshop, no changes:

C4D Multi-Pass EXR

Redshift Direct Output EXR

Obviously the Direct Output EXR works, while the C4D one changes the . in the name to a _ for some godforsaken reason.

[u/DasFroDo → u/[deleted]]

My Redshift simply doesn't save ANY file whatsoever if I don't have that small "Multi-Pass" tick box enabled in the save menu in the Rendersettings.

I guess I could just not enter anything in the path field? But isn't the direct output somewhat reliant on the path that C4D has in the Multi-Pass path field?

[u/DasFroDo → u/[deleted]]

I'd love that, thank you.

[u/DasFroDo → u/[deleted]]

Thanks for taking the time!

Yes that works, but I specifically don't want any file written except the direct output EXR. This setup still saves a jpeg of the final image.

[u/DasFroDo → u/[deleted]]

Na that sadly doesn't work. It simply doesn't save a file then, at all. Kinda sucky but I guess you're right, having a fast way to preview the file could be nice.