OCIO issue in 5.2 update

[alessandro_consonni]

After having reopened the saved max file, the profile view transform profile saved from the previous file is not recognized even if I reset the entire OCIO config. For example, if I save my file view transform with Rec.709 profile, at reopening rec.709 is not recognized and it appears like "raw" color profile is applied (or display correction is set to none), the same if I save with sRGB or any other profile in view transform.

Hope that my explaination is pretty clear.

Thanks

AC

[matanov]

I've tried on couple of machines but couldn't reproduce it. Can you attach a simple file that we can open here with 5.1 and then with 5.2 to see the issue?

[alessandro_consonni]

I did some tests and randomly the error appear, sometimes at the first setup, sometimes after saving.

In attachment you can find a simple scene, just open it and hitting render for cause the issue on my machine.

Thanks

AC

[matanov]

Still, if you have some repro scenes and steps will be very helpful.

[atanasbak]

I have similar problem when using OCIO environment config and 3ds Max 2022 + V-Ray 5, update 2.2:
OCIO=C:\OpenColorIO-Configs\aces_1.2\config.ocio

When ACESsg to sRGB is selected(image 1) the result is the same as None option is selected in Display Correction(image 2).
If I select anything else then sRGB, P3 for example the image is updated correctly(image 3).
If I copy the folder with OCIO config, same files as in environment config but different location then ACESsg to sRGB will work (image 4).
Just for a test using OCIO map with environment config is updated correctly (image 5).

Same setup works as expected in 3ds Max 2021 + V-Ray 5, update 1.3.

[matanov]

Can you try with ACES 1.3?

[atanasbak]

I can not find download link for ACES 1.3 config.ocio files.
I've tested with ACES 1.1 as OCIO environment and the result is the same - ACESsg to sRGB selection is ignored in V-Ray 5, update 2.2.

[matanov]

Sorry, I meant 1.0.3 - https://github.com/imageworks/OpenColorIO-Configs/

[atanasbak]

1.0.3 is working as expected, the problem is with 1.1 and 1.2.

[matanov]

As far as I know, 1.0.3 is the latest official version. 1.2 seems like a branched version from another place. Anyway -

1. Can you pack your config and send it together with a simple scene?
2. Is there any particular reason for using 1.2 over 1.0.3?

[atanasbak]

My config is exactly the same as in this repository: https://github.com/colour-science/OpenColorIO-Configs
The result is the same for any scene with the config from my screenshots.My 3ds Max 2022 and VRay are the latest versions, no other plugins installed.
I just assume that 1.2 will be better (newer version) and it's shown in your docs: https://docs.chaos.com/display/VMAX/...Workflow+Setup

[gaara the nightmare]

I'm having the same problem as alessandro_consonni since 5.2.
It doesn't matter if I try with 1.0.3 or another one. Every time I restart 3dsmax and open a scene with ocio setting applied, the visual result in the vfb look like "none" in display correction.
I found a way to overcome the result, I just have to reload another OCIO file, for example, if the scene was using 1.2 I load 1.1 but If I save and restart 3dsmax and open the scene, I need to reload another OCIO file again from 1.1 to 1.2
It's very annoying and super confusing, I can add another problem, the properties tab in the VFB is hidding all the layers every time I restart 3dsmax 2021, I need to slide it down to be able to see the layers.

[matanov]

We found a machine where we can reproduce the problem locally and there is a dev already investigating.

[matanov]

Can you try setting your Windows decimal separator to comma if it's a dot at the moment?

[gaara the nightmare]

matanov Thanks for the update, this seems to fix my problem for the OCIO and properties panel!
Do you think this problem between dot and comma would be fixed in the future ?