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
I have searched the existing issues and added correct labels.
Description
Current Behavior
Deadline now ignores Nuke slate, and offsets the published exr sequence.
Expected Behavior
Nuke slate should be published.
Steps To Reproduce:
make Nuke script, add Slate node, range 1001-1010
Publish on farm
Slate is extracted correctly, and added as frame 1000 in work folder
Publish ignores the slate, exr files are offseted (no exr slate published, frame 1001 becomes 1000)
Additional context:
Version
Server 1.5.4, core 1.0.10, deadline 0.5.0, nuke 0.2.6
What platform were you running when you found the bug?
Windows 10
You can also provide any additional information relevant to the issue.
The slate exr frame file is now not present in json instances.representations.files
Relevant log output:
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
Description
Current Behavior
Deadline now ignores Nuke slate, and offsets the published exr sequence.
Expected Behavior
Nuke slate should be published.
Steps To Reproduce:
Additional context:
Version
Server 1.5.4, core 1.0.10, deadline 0.5.0, nuke 0.2.6
What platform were you running when you found the bug?
Windows 10
You can also provide any additional information relevant to the issue.

The slate exr frame file is now not present in json instances.representations.files
Relevant log output:
The text was updated successfully, but these errors were encountered: