OCIO AcesCG workaround so far...

[javierluisbravo]

After some tests...

(i always talk about saving animations as exr files to comp later using 32 bit workflows)

1=> paride method => saving from max with those settings (it clamps the pixels to 1!) as the ODT is saved into the exr file .. which is not good.
when i turn on ACES: SRGB in the camera in OCIO VIEW... that ODT is saved into the exr... that should not happen as that should be only for viewing.

2=> using OCIO 1.2 or 1.0.3 is the same.. i just tested both

3=> with my first post workflow i managed to save ACES2065 from Octane (NOT ACESCG) it can't be done... it seems a bug really..

4=> with this setup... what i have in my comp soft (nuke or after) is totally different from what i see in the octane viewport/3dsmax viewport.
The only way to make that MATCH is like this:
==> just while working to TURN ON => gamma hack and to TURN ON in the camara paride settings in OCIO VIEW
=> ACES: SRGB.

This way viewport and post/comp softare (nuke or after) matches perfectly..
but when i render i have to TURN OFF gamma hack and OCIO VIEW in the camera...

I am getting tired of having to do all this to make it work.. this should be a click..
I was used to a workflow that worked perfectly.. and now with OCIO all got complicated when it should be super simple.

if this is not clear i can make a little video...

thanks for you time!