Problem summary When trying to render particles via terminal, that have multiple geometry as colliders, you get an error message similar to the following:
Total render time: 0.27 seconds Traceback (most recent call last):
File "stdin", line 1, in <module>
RuntimeError: Write1 was disabled for all the frames
However, this seems to only happen the first time you run the execute command.
Customer reported version nuke.11.1v3
Customer reported platform centos7
Steps to reproduce
1) Open the attached script in terminal mode. Use:
2) Run the following lines of code in the terminal:
writer = nuke.toNode("Write1")
nuke.execute( writer, 1005, 1012, 1 )
3) Notice that the render fails and you get the following message in the terminal:
RuntimeError: Write1 was disabled for all the frames
Reproduced by support This bug has been reproduced in: Nuke 11.1v3 - Linux CentOS 7 - Windows 10 - Mac OSX El Capitan Nuke 11.1v1 - Linux CentOS 7 Nuke 11.0v4 - Linux CentOS 7 Nuke 11.0v1 - Linux CentOS 7 Nuke 10.5v7 - Linux CentOS 7 Nuke 10.5v1 - Linux CentOS 7 Nuke 10.0v6 - Linux CentOS 7 Nuke 10.0v1 - Linux CentOS 7 Nuke 9.0v9 - Linux CentOS 7 Nuke 9.0v1 - Linux CentOS 6 - Windows 10 - Mac OSX El Capitan
Unable to reproduce bug in: Nuke 8.0v7 - Linux CentOS 6 - Windows 10 - Mac OSX El Capitan
Earliest version tested Nuke 8.0v7 - Linux CentOS 6 - Windows 10 - Mac OSX El Capitan - This issue no longer appears in this version and has regressed. This may be caused by changes to the ScanlineRender node.
Expected behaviour The script should render once the commands are executed.
Actual behaviour The render fails and you get the following message in the terminal:
RuntimeError: Write1 was disabled for all the frames
However, this seems to only happen the first time you run the execute command.