Hello! Just started with ayon and i have manged to set up the work template with a custom token but when i try and acsess the token/ setup in the work anatomy from the temporary rendering path template location in the nuke addon can not seam to acess it with the error " is unsolved.keys with invalid data type: work , while the ayon core can acess it fine can anybody help
have tried naming the template directly in it as well as doing work[template name]
How does the create template looksl ike on your side?
On my side, I’ve the default template
{root[work]}/{project[name]}/{hierarchy}/{folder[name]}/work/{task[name]}
it is the same directoery pathm but with a added folder beteen folder name and work, the work template works and validates fine in the core settings when setting the same locations its just the nuke write node one it dossnt like bythe looks of it
as within the temport render location adress you can use {work} which defults to the defultwork template filepath but i want to use my custuom defined one if possible pls
These templates support the available template keys
.
About root, when adding a new root in ayon+anatomy://{project_name}/roots
you should refer to it as {root[root_name]} e.g. {root[work]}
on my side e.g. I’ve configs and I used use it in templates as follows root[configs].
so with the defuly tempoery work render location in the nuke addon, i can use the {work} key as itsthere by defult, and then that uses the defult work path in the template antomy, is there no way to specify to use a added work template, eg like {work[myownone]} ?
if it helps just putting {root[work]} into the create write renders tempoery path template returns the error template"{root[work]}/normalpath" is unsolved.missing keysb"root"
We indeed use {root[work]} in multiple places like anatomy templates and workfile builder templates.
But, sorry I missed you were referring to this particular setting:
- Temporary rendering path template:
ayon+settings://nuke/create/CreateWriteRender/temp_rendering_path_template
Basically, this setting refers to a relative location and file name in your default work area{work}/renders/nuke/{product[name]}/{product[name]}.{frame}.{ext}.
Where {work} refers to your work area set in anatomy template.
Unfortunatly, this key is expected and its value is hard coded.
Would it be much sense to you if Temporary rendering path template setting changed to:
This is a mock up, it won’t work without implementing that in the addon.