ID 152248 - An error occurs when using a Particle Emitter with .EXRs using various-sized bounding boxes.

Follow

Problem summary:
The error message "Reader did not set bounding box" appears on Read nodes when EXRs are used with various-sized bounding boxes.

In versions prior to 11.0v1, the error will read as "Read error: too many open files"


Customer reported version:
nuke.11.3v2


Customer reported platform:
windows10


Steps to reproduce:
*Requires EXRs with different sized Bounding Boxes.*
 

1) In NukeX, create a ScanlineRender node.

2) Create a Camera and attach it to the ScanlineRender.

3) Create multiple Read nodes with *EXR* files of at last 10 frames each.

4) Select all Read nodes and create a Particle Emitter node

5) View the ScanlineRender node and save the script.

6) Close the script and then re-open it, observing any Read nodes for errors. 


Expected behavior:
The script should open without errors on the Read nodes.


Actual behavior:
Multiple Read nodes appear with an error "Reader did not set bounding box" or "too many open files" when loading a script with multiple Read nodes that include various-sized bounding box .EXRs.


Workaround:
In Nuke versions above 11.0v1, selecting the affected Read node and choosing Reload corrects the issue.
In versions 10.5v8 and below, full caching the affected .EXRs by playing in the Viewer removed the error.


Reproduced by Support in:
Nukex 11.3v3 - Windows 10, CentOS 7, macOS 10.13 High Sierra

Nukex 11.3v1 - Windows 10

Nukex 11.2v1 - Windows 10

Nukex 11.1v1 - Windows 10

Nukex 11.0v1 - Windows 10

Nukex 10.5v1 - Windows 10

Nukex 10.0v1 - Windows 10

Nukex 9.0v1 - Windows 10, CentOS 7, macOS 10.13 High Sierra


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

    We're sorry to hear that

    Please tell us why