OTOY Forums

As a long time user of Octane, I cannot beleive I am writing this post. I have been away from 32bit for a while. I came crashing back to it this weekend. I tried to save a rendering as a 32bit EXR for post Photoshop work and exposure balancing. Although it was saved as a 32bit Floating Point EXR, the image wase clamped at 8bit standard. It could not be adjusted. And yes, my render and viewport tone mapping was set to "HDR".

The problem that unless you specifically right click from the Octane ViewPort and "SAVE AS EXR", any other workflow is clamped. If you "SAVE CURRENT RENDER PASS" or "SAVE ALL RENDER PASSES" and you specify 32bit FP EXR it is still clamped !!

Here is where it gets way worse. Even if you just render out normally through 3dsmax output and specify 32bit FP EXR, it again is still clampled !! So for final multi-frame production you are not getting 32bit workflow !!

The only other solution that does work is to use the "SAVE ALL PASSES AS MULTI PASS EXR FILE" option in the PASSES OUTPUT tab. That at least is not clamped.

I found out NOW after an extensive morning session troubleshooting this. I honestly a) cannot believe this is an issue b) no user has found it c) no dev has found it.
I don't know how far back this goes, but it is BUSTED BIG TIME !!

One more thing... Are we supposed to be able to save as 32bit with TONE MAPPING applied ?? Because I thought they fixed that long long ago. If you add any kind of LUT tone mapping on top, it also kills the 32bit save. Either you get it tonned mapped at 8bit or its save 32bit untonned. Not both.

Hi richardyarlett,
Would you like to try this test file?
Regards
Paride

Ok, downloaded and CONFIRMED. See these 4 EXRs as the four menu options here, 1,2,3,4

It is definately not working with 32bit unless you use those last two options. Same for regular rendering out of 3dsmax. Not working unless you add the MULTI_OUT.EXR option.

Also I thought we were able to save TONED MAPPED images as 32bit now. I thought that got fixed a long time ago. It used to be that you had to use LINEAR/NONE to get 32bit and any "camera response" made it 8bit, but I thought you changed that so that it can stay as 32bit. Can you confirm ?

the last few Octane plugins for MAX are broken

Hi Richard,

There are 2 different ways to save as EXR, and the recommended one is the Octane exr, saved from Octane engine. (the last 2 options from the viewport button context menu, and the options in Kernel/Passes output)
Using Octane exr ensure that you'll get the same result if you export your scene for stand alone and save as octane exr.

When saving with 3dsmax exr (the first 2 options), the colors are currently clamped to 1.0 to be displayed on the viewport.
I believe it has always been the case, so there's nothing broken there..

As elsksa pointed out, I understand that the tone mapping is not supposed to be applied in the exr output.

In the next release, I'll add an option to keep a linear color space (un-clamped colors), that seems to work when saving max exr..
I'm not fully sure it will always give the the same result as Octane exr, but it seems fine with the few scenes I tried..
Hopefully that will help for your workflow.

Thanks

any update ?

Hi Richard,

The saving as 3dsmax EXR is possible with non clamped values if you use a linear raw ocio view.

For example, unzip this
https://github.com/sobotka/filmic-blend ... master.zip
and, in Octane preferences / Main, set 'OCIO: Specify config file' to the ocio file, like
C:\ocio\filmic-blender-master\config.ocio
and enable 'OCIO: Use specified config file'

Then, in your current Imager, set the OCIO view to 'sRGB: Linear Raw'

That will keep the image as un-clamped 32 bits float per pixel, and will be saved by 3dsMax EXR.

I hope that helps.

The option I will add in the next release will do the same thing, without any ocio settings..

Thanks

how do I save a "responsed" image as a 32bit EXR ?