Skip to content
This repository has been archived by the owner on Sep 20, 2024. It is now read-only.

Maya + Redshift: Deadline render duplicates <aov> in output render #3953

Closed
BigRoy opened this issue Oct 7, 2022 · 0 comments · Fixed by #3954
Closed

Maya + Redshift: Deadline render duplicates <aov> in output render #3953

BigRoy opened this issue Oct 7, 2022 · 0 comments · Fixed by #3954
Assignees

Comments

@BigRoy
Copy link
Collaborator

BigRoy commented Oct 7, 2022

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:

afbeelding

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 submission

But 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:
afbeelding

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:

  1. Render with Redshift from Maya without merge AOVs / multilayer through Deadline.
  2. Publish of rendered images fails.

Example settings:
afbeelding

Expected behavior

Output from Deadline should not deviate from scene settings.
And above all, publishing must work.

Desktop (please complete the following information):

  • OS: Windows
  • Host: Maya 2022.3, Redshift 3.5.06

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]

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants