Hey! Sneaky double post on my part
I’m assuming referenced keys are not implemented in the templated workfile builder, this would be super handy to have.
Here’s what I’ve tried, attempting to set up separate workfile templates per-sequence:
path to template: {root[work]}/{project[name]}/_templates/nuke/{parent}/Lighting.nk
The root[work] key works fine, but all references to project, hierarchy, parent etc give “could not solve key” errors in nuke. The {parent} is the important part that would ideally return the sequence name.
My dream uber-template system would have a per sequence template, with different segments added or removed on build, based on shot tags
In the meantime I think I’ll just make one huge template file that contains the setups for multiple sequences. This is okay for Nuke but not so great for blender or maya etc