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

Nuke: Rendered Frame validation is triggered by multiple collections #156

Closed
antirotor opened this issue May 18, 2020 · 2 comments
Closed
Labels
host: Nuke type: bug Something isn't working

Comments

@antirotor
Copy link
Member

Problem

rendered frame validator is now checking if files are rendered correctly by using clique.assembly() and failing when there are more collections then expected. But those other collections are of no importance now as we are working with explicit list of files and sometimes Deadline (or other software) is leaving behind .tmp files or other garbage that should not trigger this validator as it is safely ignored (or should be).

https://github.com/pypeclub/pype/blob/64da0039538139a3149956a82d6c1b928427f42e/pype/plugins/nuke/publish/validate_rendered_frames.py#L47

@antirotor antirotor added type: bug Something isn't working host: Nuke LOW labels May 18, 2020
@antirotor
Copy link
Member Author

Relates to #170

@mkolar
Copy link
Member

mkolar commented Jun 1, 2021

temporarily fixed during 3.0 development. will be resolved fully when reworking integrator

@mkolar mkolar closed this as completed Jun 1, 2021
Tilix4 added a commit to Tilix4/OpenPype that referenced this issue Dec 8, 2023
* Fix: Switch transfer custom properties

* format line too long
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

No branches or pull requests

2 participants