Project

General

Profile

Actions

Feature #106

open
SS DM

reusable templates / referenced template sections / switch node

Feature #106: reusable templates / referenced template sections / switch node
1

Added by Sebastian Schierwater 1 day ago. Updated 1 day ago.

Status:
In Progress
Priority:
Normal
Start date:
2026-09-30
Due date:
% Done:

0%

Estimated time:

Description

upfront i need to apologize for this being rather a description of a problem i'm facing, than a fully thought through feature request...

what i would like to be able to do is reuse common parts of a stacking template in multiple templates.
at the moment i am managing multiple templates for the various shot types we are dealing with. still exterior backplate, still exterior full cg, still range, still ext studio, still interior, .... you get the idea.
these templates share many identical sections. for example the env renders of a range shot or a interior shot are no different to a single car full cg exterior. same goes for many utility / mask layers.
if i want to tweak anything in our env rendersetup that affects stacking i need to update multiple templates. this can be quite tideous and error prone. what i'd love to have is a way to reference or share sections in multiple templates.
there are a few ways i could think of how this could be done.

1. switch node. a single template that covers everything. this would require some sort of switch node that lets you branch off your stacking tree, based on some input variable. and the corresponding "merge" node as well in order to combine different branches again for common shared parts in the stacking tree.

2. sub sections, smart sections, or whatever you want to call it. similar to photoshop smart objects you would have a template within a template. it would need a defined entry and exit point. coming back to my example the env section could be a subsection that is then used in the various templates that are stored in the same master template as individual trees next to each other. any change you make to the subsection is the automatically carried into any tree that uses it.

3. same as 2. but the subsection are actual stacker projects that you can reference into other stacker projects.

Actions

Also available in: PDF Atom