Hi everyone,
we’re experiencing problems when submitting Fusion composition files to Deadline which have animated savers in them. In our workflow it is not uncommon that we have different savers in our comp that need to write files for different framelengths (e.g. Saver1 only writes frames 1-5, Saver2 writes frames 4-16 etc.). When rendering locally, the solution for this is to animate the Saver’s “Blend” slider, so that it is set to 0 when it isn’t supposed to render something.
I know that Deadline ignores disabled Savers. Undofortunately you cannot animate the “disabled” status of a Saver, only the “Blend”. But when we submit a Blend animated Saver to Deadline, Deadline reports an error for the given framerange (“The Saver did not produce an output file”) and requeues the task.
Is there any way to modify the Fusion job handling in Deadline so that it doesn’t just ignore “disabled” Savers, but also Savers with “Blend = 0”?