r25 OCIO Config field behavior

[Anonymous]

Choosing OCIO from the Color Manager dropdown autofills the Config field with $OCIO as with previous C4D versions. Deleting $OCIO to leave the Config field blank would change the Narrow and Linear fields Auto to sRGB and AcesCG automatically which through trial and error is what's required when rendering on a farm. In r25 C4DtoA 3.3.9, deleting $OCIO from the Config field auto populates the field with "/" and doesn't allow for profile picking of the Narrow and Linear fields making scenes created with r25 unable to render using OCIO on the farm.

Here it is in r25.

Same in r23.

[Stephen.Blair]

I don't have R25 installed yet. I'll set it up tomorrow...

[Stephen.Blair]

I don't understand why the Config has to be left blank. Don't you need an OCIO config file to use OCIO ?

I get

00:00:01   127MB WARNING | [color_manager_ocio] could not find a valid config

[Anonymous]

The farm's admin told me he found documentation / bug ( can't remember ) stating earlier versions of C4DtoA ( 3.3.7.1 ) needed a blank config field, saying it couldn't find the config file despite the environment variable being set properly on every node. Leaving the field blank caused the two profile selectors to default to sRGB and ACEScg. While I still don't understand why deleting the field auto fill with "/", the problem now seems to be solved. C4DtoA v3.3.9 has fixed this problem for both r23 and r25, so leaving the field filled with $OCIO now works on the farm.