Problem summary
ScanlineRender sometimes fails to render all the geometry correctly
It varies between machines, but normally at least 1 in 1000 frames fails, though can be more like 1 in 100
This has been reproduced with a fresh Nuke script and simpler 1 ScanlineRender node setup, but happens less frequently, the below case happens more consistently.
This reproduction case uses the frame server, but it also happens on render farms.
Customer reported version
nuke.14.1v1
Customer reported platform
rocky8
Steps to reproduce
1) Launch Nuke
2) Open the attached Nuke script
3) Render the Write node, for with a frame range of 1-1000 and use the frame server to render
4) Read in the rendered footage and check all the frames, some are incorrect
Expected behaviour
For all of the frames to be the same, as the 3D scene has no movement in the scene, and render the following image:
Actual behaviour
On random frames, the render fails, with either geometry being stretched, missing or having holes in it:
Workaround
Limiting the number of thread Nuke uses with -m 1 can help, which can be done for the frame server in Edit>Preferences...>Performance>Threads/Processes, enabling customize renderer limits and setting the number of threads to 1
Reproduced by support
This bug has been reproduced in:
Nuke 15.1v2 - macOS Sonoma, Rocky 9.3
Nuke 15.0v1 - macOS Sonoma, Rocky 9.3 - macOS regression
Nuke 14.1v5 - Rocky 9.3
Nuke 14.0v1 - Rocky 9.3 - Linux regression
Unable to reproduce bug in:
Nuke 15.1v2 - Windows 10
Nuke 14.1v5 - macOS Sonoma
Nuke 13.2v8 - Rocky 9.3
Earliest version tested
Nuke 13.2v8 - This issue doesn't appear in this version and has regressed
