Hi,
I need a different publish path template for a specific versioning nuke task. Is there a way to define by task, or family, or something else, which template will be used for a given nuke render / publish?
In core settings you can specify which publish template applies to a publish using profiles ayon+settings://core/tools/publish/template_name_profiles:
This is purely as an example.
And depending on your setup and anatomy, you may want to set this as a project override if it only applies to a single project.
Then in project anatomy make sure the template exists: ayon+anatomy://PROJECTNAME/templates/publish:
Note that the publish name profiles support regex, so that for example the task name filter could also be .*BG$ to match any task name ending with capitals BG.
Can you provide some more details on your use case? Why do you want that specific task to render to a different publish path?
Hi and thanks for the response!
The use case is that a particular job has special versioning needs and editorial wants them organized in a specific way that differs from normal projects.
This solution seems to work, thanks.
This is working as expected, thanks.
I was wondering if it is possible to add a custom key to the template structure to create a sub-variant.
The need is to define a variant and sub variant at write-node creation time, and have that propagate through to folder creation and publishing.
For example:
{root[work]}/{project[name]}/{hierarchy}/{folder[name]}/publish/{product[type]}/{product[name]}/{@version}/{sub_variant}
Where sub_variant is provided alongside variant
Can this be achieved? Perhaps with a modified creator plugin?
These are the avialable template keys.
https://help.ayon.app/articles/3815114-project-anatomy#ko8k2dx8wtf
There’s a possiblity to implementing dynamic template keys that added on run time. we already have renderlayer and aov (not sure if they work in Nuke though)
from on top of my head, I can’t remeber the exact steps you need. but you can try doing something like this:
I’m not sure if that will work for farm render without additional work, but anyways here are the linked PRs to the mentioned PR above for additional info.