New post
0

{project} not resolved for Nuke in Project context

Avatar
Marijn Eken
None
Follow

I'm probably being stupid here, but I can't figure out how to solve this problem.

I've changed the templates.yml to include a "nuke_project_work" template for saving Nuke scripts when in the "Project" context. So, these are meant to be global scripts concerning the whole project, rather than a shot. I've defined this template to have {project} as part of the name, but I end up getting this error when I go to the Save As.. dialog:

Unhandled exception in worker thread: Tried to resolve a path from the template <Sgtk TemplatePath nuke_project_work: work/globals/creators/comp/nuke/{project}_comp_{name}_v{version}_{initials}.nk> and a set of input fields '{'version': 0, 'name': 'full', 'initials': 'mek'}' but the following required fields were missing from the input: ['project']

So, I'm launching Nuke from the "Project Actions" pulldown on the website. And I've changed the "project.yml" file to have the "tk-multi-workfiles" configured to point to the templats. I thought that {project} would always be available in the current context and should just work. It works for the Hiero template, but not for Nuke.
What simple thing am I missing?

Thanks,
Marijn

Date Votes

4 comments

  • 0
    Avatar
    Permanently deleted user

    Hello!

    Sorry for not getting back sooner!

    Thanks for reporting this – your setup looks right, I think this may be a bug in toolkit! The template system normally doesn't really handle the project token since that sits above the template path definition - except in your case where you want to add a reference to it as part of the filename. Which makes complete sense and of course should work.

    I'll ticket it up on our end so it can get prioritized and fixed. In the meantime, do you have an acceptable workaround?

    Thanks!
    Manne

  • 0
    Avatar
    Marijn Eken

    Ah, good to know it wasn't me going crazy. In the mean time our pipeline setup has changed and we're not doing this at the project level anymore. But, it would still be good if this was fixed. Thanks.

  • 0
    Avatar
    Dashiel Bivens

    Has this problem been resolved? I am having a similar issue when launching against a Sequence's task, the Sequence template is not resolved in the tk-multi-workfiles app...

    Unhandled exception in worker thread: Tried to resolve a path from the template <Sgtk TemplatePath hiero_project_episode_work: hiero_project_episode_work_area/{project_shortname}_{Sequence}_{name}_v{version}.hrox> and a set of input fields '{'project_shortname': 'devs', 'version': 1, 'name': 'a'}' but the following required fields were missing from the input: ['Sequence']

    I'm launched against a task on the Sequence entity... shouldn't the context be able to resolve this token?The entity's display name is Episode, could that be the issue?

  • 0
    Avatar
    Dashiel Bivens

    Interestingly, I just fixed it. I had forgotten to use the @includes syntax on the 'hiero_project_episode_work' template:

         hiero_project_episode_work_area: '{parent_season}/{Sequence}/tasks/{PipelineStep}/{Task}/hiero'

         hiero_project_episode_work: 'hiero_project_episode_work_area/{project_shortname}_{Sequence}_{name}_v{version}.hrox'

    Fixing this resolved the issue.

         hiero_project_episode_work_area: '{parent_season}/{Sequence}/tasks/{PipelineStep}/{Task}/hiero'

         hiero_project_episode_work: '@hiero_project_episode_work_area/{project_shortname}_{Sequence}_{name}_v{version}.hrox'

Please sign in to leave a comment.