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
Please describe the feature you have in mind and explain what the current shortcomings are?
The Extract Intermediate Files Publishing plugin needs to check if any viewers in the scene are not referencing existing input process (IP) nodes. If these nodes exist, they are used for baking the look into intermediate files.
In Nuke's viewer workflow, multiple viewers can be part of one node graph. These viewers might be copied from a different workfile with incorrect or nonexistent node references in the input process (IP). Currently, if this issue occurs, the Extract Intermediate plugin fails to process and gives the user a cryptic message, making it unclear what happened.
How would you imagine the implementation of the feature?
We should collect viewers and validate them for existing IP-referenced nodes. If any fail validation, we can offer a repair action. This action would remove the IP node name from the viewer.
Are there any labels you wish to add?
I have added the relevant labels to the enhancement request.
Describe alternatives you've considered:
No response
Additional context:
No response
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
Please describe the feature you have in mind and explain what the current shortcomings are?
The Extract Intermediate Files Publishing plugin needs to check if any viewers in the scene are not referencing existing input process (IP) nodes. If these nodes exist, they are used for baking the look into intermediate files.
In Nuke's viewer workflow, multiple viewers can be part of one node graph. These viewers might be copied from a different workfile with incorrect or nonexistent node references in the input process (IP). Currently, if this issue occurs, the Extract Intermediate plugin fails to process and gives the user a cryptic message, making it unclear what happened.
How would you imagine the implementation of the feature?
We should collect viewers and validate them for existing IP-referenced nodes. If any fail validation, we can offer a repair action. This action would remove the IP node name from the viewer.
Are there any labels you wish to add?
Describe alternatives you've considered:
No response
Additional context:
No response
The text was updated successfully, but these errors were encountered: