You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 20, 2024. It is now read-only.
Redshift renders through Deadline with Merge AOVs (= Multilayer EXR) disabled will render with a double <aov> (RenderPass) in the filename. Like this:
Publishing will fail since the metadata will expect the AOV / RenderPass token to exist only once (and for the Beauty layer by default to not be there at all - hence why it has a single token in the screenshot)
Running version
3.14.4-nightly.1
Describe the bug
Redshift renders through Deadline with Merge AOVs (= Multilayer EXR) disabled will render with a double
<aov>
(RenderPass) in the filename. Like this:Publishing will fail since the metadata will expect the AOV / RenderPass token to exist only once (and for the Beauty layer by default to not be there at all - hence why it has a single token in the screenshot)
This issue originates from the Deadline submitter taking the file prefix from the layer metadata from
lib_renderproducts
and assign that as the file prefix for the Deadline submissionBut the Layer Metadata in
lib_rendersettings
collects the file prefix that matches what the renderer produces as output - and doesn't necessarily match the input setting.Hence you get an
_<aov>
token forced in that:The Deadline submitter thus should not take the prefix from the layer metadata but from the scene render settings instead.
To Reproduce
Steps to reproduce the behavior:
Example settings:
Expected behavior
Output from Deadline should not deviate from scene settings.
And above all, publishing must work.
Desktop (please complete the following information):
Additional context
Issue likely has been introduced with the implementation of the new deadline submitter which uses the Abstract Deadline Submitter as base.
[cuID:OP-4208]
The text was updated successfully, but these errors were encountered: