Does the config file exist on your farm machine?
This is “built in” config that ayon provides. Problem is that if mashine performing publish task is different from one whitch was originaly used for publishing ayon cant find ocio because it looks at oroginal mashine user name not in publishing mashine
u can see: it lauches oiio on cg3 user folder but looking for ocio config inside timse folder. Of course cg3 has confing inside cg3 folder and timse has its inside timse)
Hi! No movement in here or am i missing something?)
the documentation tells me that if i choose two confings ayon will pick first awaliable but it not happens.
with this configs
my remote workers have this message
so only first one is picked up
but documentation tell me that
so this happens on farm too as i wrote erlier
Unfortunatly, I was not able to reproduce.
Firstly, I added an OCIO path on top as users. and it was set accordingly in Nuke.
And, as soon as I moved it to the bottom, AYON Nuke reported that OCIO set doesn’t match settings.
You are testing the wrong thing @mustafa_jafar - what you should test is set the PATH one at the top, but set it to an invalid path. According to those docs, if the first matching profile fails because the path is invalid - then the next one would be considered for your machine that matches your current context.
I suspect, since it’s profile based - that it doesn’t actually work like that and that the docs are wrong (or that it’s a bug).
Looking at the code - it just picks the first matching profile, regardless of whether the ‘path’ exists from the current client machine.
Yeah, that won’t work.
the profile filtering logic is generic and has nothing to do if the values in the selected profile are wrong.