ID 359605 - Incorrect frames are visible while rendering from the command line or within Nuke GUI with the frame server disabled when using render_order on Write nodes.

Problem summary
Incorrect frames are visible while rendering from the command line or within Nuke GUI with the frame server disabled when using render_order on Write nodes.

Customer reported version
nuke.11.1v4

Customer reported platform
n_a_linux

Steps to reproduce
1) Launch Nuke and load the attached script.
2) Set the Write/Read nodes to be for relative paths for your desktop.
3) Open the Command Prompt and change directory to Nuke's installation path.
4) Render the comp using the command line with the following command Nuke13.1.exe -x -F 1-50 "path/to/script.nk"​
5) In Nuke, select the Read3 node for "checker03_###.exr" and reload the file.
6) Scrub the timeline for the first few frames, observing the output.

Alternative rendering - press F5 to write all Write nodes in the GUI with frame server unchecked.
 

Workaround
The current workaround is to use the Frame Server to render the comp or on the command line with the --sro flag: Nuke13.1.exe --sro -x -F 1-50 "path/to/script.nk"​

Reproduced by Support in:
Nuke 13.2v1 - Windows 10, CentOS 7
Nuke 13.1v1 - Windows 10
Nuke 13.0v1 - Windows 10
Nuke 12.0v1 - Windows 10
Nuke 11.0v1 - Windows 10
Nuke 10.0v1 - Windows 10
Nuke 9.0v1 - Windows 10, CentOS 7

Earliest version tested
Nuke 9.0v1 - This issue appears to be in all versions of the product

Expected behavior
The frames should be consistent and render in the proper order with render_order set while writing all nodes at once.

Actual behavior
The frames become corrupt when rendering all write nodes with render_order using the command line or Nuke GUI render prompts.