Problem summary An Ocula generated Disparity pass differs from original Viewer result when rendered or copied and re-calculated.
This issue has been found to occur in several situations, from copying the identical setup and re-running the solver, or when the node is rendered.
This issue occurs within all Ocula 4 release versions over all three major operating systems.
Customer reported version nuke.11.2v4
Customer reported platform fedora
Steps to reproduce
1) Read in stereo footage
2) Create an O_Solver node, setting a 'Key Frame' on the first frame
3) Create an O_DisparityGenerator node downstream from the O_Solver node, selecting the preset function to 'Aligned'
4) Change the Viewer to view as the Disparity pass
5) Select an area of pixels in the Viewer using the ctrl+shift drag selection box and take note of the colour values.
6) Create a Write node, selecting all channels, 32-bit float and render as an exr.
7) Compare the result of the O_DisparityGenerator and the Write node in the Viewer Result: Colour difference
8) Read in the render and compare to the O_DisparityGenerator Result: Colour difference (matching the Write node before export)
Expected behaviour There should not be a colour difference between the render and nodal result
Actual behaviour There is a colour difference between the render and nodal result
Workaround As this appears to be related to caching, clearing the cache after the render alters the nodal result to the rendered result.
Reproduced by support This bug has been reproduced in: Nuke 11.3v6 - Windows 7 - MacOS 10.14.5 - CentOS7 Nuke 11.3v1 - Windows 7 Nuke 11.2v1 - Windows 7 Nuke 11.1v1 - Windows 7 Nuke 11.0v1 - Windows 7 Nuke 10.5v1 - Windows 7 Nuke 10.0v1 - Windows 7 Nuke 9.0v1 - Windows 7 Nuke 8.0v1 - Windows 7 - MacOS 10.14.5 - CentOS7
Earliest version tested Nuke 8.0v1 (Ocula 4.0) - This issue appears to be in all versions of the product
