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

Nuke: render family integration consistency #3576

Conversation

jakubjezek001
Copy link
Member

@jakubjezek001 jakubjezek001 commented Jul 26, 2022

Brief description

Families are integrating to the same family from any render target.

Description

Any chosen render target should now produce the same result in published folder.

Additional info

Integrator is using anatomyData keys for filling up templates and choosing what template to use from Anatomy. So family has to be correct.

Testing notes:

  1. Nuke render local, farm, existing frames from render and prerender node
  2. published versions should be the same family

closes #3568

@jakubjezek001 jakubjezek001 self-assigned this Jul 26, 2022
@ynbot
Copy link
Contributor

ynbot commented Jul 26, 2022

@jakubjezek001 jakubjezek001 added host: Nuke type: bug Something isn't working labels Jul 26, 2022
@jrsndl
Copy link
Collaborator

jrsndl commented Jul 27, 2022

Farm publish doesn't make an anatomy {output} for thumbnail, local publish does.
image

Copy link
Collaborator

@jrsndl jrsndl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Family consistency is fixed.
I tested farm and local publish, with clean and "dirty" work folder.

@jakubjezek001 jakubjezek001 merged commit 0492f01 into develop Jul 27, 2022
@jakubjezek001 jakubjezek001 deleted the bugfix/OP-3642_Nuke-Local-vs-Farm-Publish-family-inconsistency branch July 27, 2022 10:58
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
host: Nuke type: bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Nuke: Local vs Farm Publish family inconsistency
3 participants