Error could not read '<MAYA_RESOURCES>/OCIO-configs/Maya2022-default/config.ocio' OCIO profile

[asundaysmonday]

Hi, I recently updated to the latest update for Maya2023 and V-Ray

Maya: 2023.3
V-ray: 6.20.02

Everything is working fine local but when I use the same computer on deadline I'm getting this error:
V-Ray error: Error could not read '<MAYA_RESOURCES>/OCIO-configs/Maya2022-default/config.ocio' OCIO profile

Does anyone know where I can set this variable? I have tried to point it to a custom .config, but it seems like V-Ray ignores this and still tries to use the path above.

I have also tried to tried to inject some code in the userSetup.py

cmds.colorManagementPrefs(e=True, configFilePath=ocio_config)
cmds​.vray('vfbControl', '-ocio',1)
cmds​.vray('vfbControl', '-loadocio', ocio_config)
cmds​.vray('vfbControl', '-ocioinputcolorspace', "ACEScg")​

This could well be a deadline problem, but it was working before I updated both software.

Thanks!

[asundaysmonday]

Hi, I recently updated to the latest update for Maya2023 and V-Ray

Maya: 2023.3
V-ray: 6.20.02

Everything is working fine local but when I use the same computer on deadline I'm getting this error:
V-Ray error: Error could not read '<MAYA_RESOURCES>/OCIO-configs/Maya2022-default/config.ocio' OCIO profile

Does anyone know where I can set this variable? I have tried to point it to a custom .config, but it seems like V-Ray ignores this and still tries to use the path above.

I have also tried to tried to inject some code in the userSetup.py

cmds.colorManagementPrefs(e=True, configFilePath=ocio_config)
cmds​.vray('vfbControl', '-ocio',1)
cmds​.vray('vfbControl', '-loadocio', ocio_config)
cmds​.vray('vfbControl', '-ocioinputcolorspace', "ACEScg")​

This could well be a deadline problem, but it was working before I updated both software.

Thanks!

[Morbid Angel]

There could be an issue how your maya is being launched and the environment variables it's reading. If on a render machine you open maya and run this mel command: getenv MAYA_LOCATION; See what path it prints? Then compare that with the same command on your workstation there could be a clue there. I would check if you have a custom maya.env where the environment is declared.
I found this thread it could be helpful:
https://forums.autodesk.com/t5/maya-...g/m-p/10185722

[tobiasroesli]

Hello,

have you tried using the windows environment variable "OCIO".

I think it's supported from most programs. And its very handy when you have additional nodes. Just put your OCIO stuff on a network drive and set the environment variable from every node to it.

Cheers

[Morbid Angel]

I would advise against using this workflow. The aces actually is a different build shipped with maya, nuke and other software. We had many issues for example in nuke when we used this workflow. It's best to declare aces path through the maya.env if you had to do that. However I would suggest figuring out why the default installation path is not found, since if you do go the custom windows environment path, then you have to always maintain that for all render nodes / workstations and it becomes pain in the butt.

[tobiasroesli]

ok, good to know what I could try if it will not work one day. I never had problems but I didn't update my OCIO 1.2 since 3-4 years .

I think in nuke I always used the nukes provided OCIO configs but in Maya and Houdini I used the environment Var which points on a network drive. Always worked but I only have 3-4 render nodes


Cheers

[asundaysmonday]

Hey Dmitry, I tried printing the MAYA_LOCATION through Maya local and when deadline picks up the task. At both instances it prints the same.
C:/Program Files/Autodesk/Maya2023 //

Also tried adding the OCIO path, and getting the same result. I'm going to try to uninstall/reinstall both software, since it was the updates that brought in the issue. I will let you know what happens.

[asundaysmonday]

Yesterday I did huge purge of software. I un-installed all maya versions, trashed preferences and deleted the autodesk folder. I also removed V-Ray.

Then I installed Maya2023.3 and V-Ray 6.20.02. Even after that the problem still occurred.

But then I installed V-Ray 6.1 and now it works as expected on the farm. I might try creep up the versions and see when it breaks.

I think we will be updating to the latest Maya soon, we are quite far behind there, hopefully these things are ironed out..

[seq]

There is a post in the thinkbox forum:

https://forums.thinkboxsoftware.com/...l-render/31326