State:New|TargetRelease:No Target|icon_bug|icon_nuke|database:public|Resolution:Fixed|BugID:395254|
Problem summary
nuke.execute() will skip any errored frames and continue to render when continueOnError=False.
This issue does not occur when unchecking 'Continue on error' in the GUI.
Customer reported version
Nuke 11.3v3
Customer reported platform
Fedora
Steps to reproduce
1) Open Nuke.
2) Create a Read node and bring in some footage that has some missing frames.
3) Ensure that the 'Missing Frames' knob is set to 'error' on the Read node.
4) Create a Write node and give it a path to render to, etc.
5) Run the following code in the Script Editor, where [first_frame] and [last_frame] are the first and last frame numbers to be rendered:
nuke.execute('Write1', [first_frame], [last_frame], 1, continueOnError=False)
Result: The missing frames are skipped and the rest of the sequence is rendered.
Expected behaviour
If an error is thrown on the current frame, Nuke should stop rendering.
Actual behaviour
The frames which are throwing an error are skipped, and the remaining frames are rendered.
Reproduced by support
This bug has been reproduced in:
Nuke 11.3v4 - Windows 10 - Linux CentOS 7 - macOS 10.13 (High Sierra)
Nuke 11.3v1 - Windows 10
Nuke 11.2v1 - Windows 10
Nuke 11.1v6 - Windows 10
Nuke 11.1v5 - Windows 10
Nuke 11.1v4 - Windows 10
Nuke 11.1v3 - Windows 10
Nuke 11.1v2 - Windows 10 - Linux CentOS 7 - macOS 10.13 (High Sierra) - Regression
Unable to reproduce bug in:
Nuke 11.1v1 - Windows 10 - Linux CentOS 7 - macOS 10.13 (High Sierra)
Earliest version tested
Nuke 11.1v1
- This issue no longer appears in this version and has regressed
We're sorry to hear that
Please tell us why