ID 418331 - CameraImagePlaneCreate: imagePath parameter doesn't import image sequence correctly, which makes the frame parameter redundant

Follow

Problem summary
The documentation for the "imagePath" parameter (within the CameraImagePlaneCreate node) suggests that you can specify an image sequence to be displayed in the image plane using frame padding. However, there is no example demonstrating the frame padding format to use, and when using either #### or %04d frame padding methods the image sequence is not imported.

Due to not being able to import the image sequences, the "frame" parameter can not specify the frame number of the image sequence, therefore making this parameter unusable. 

Customer reported version
Katana.3.2v1

Customer reported platform
Windows10

Steps to reproduce
1) Create a CameraCreate node and then create and connect a CameraImagePlaneCreate node below it.

2) Select the CameraImagePlaneCreate node, and then expand the Scene Graph (by double-clicking the root folder).

3) In the CameraImagePlaneCreate parameter tab, set the "cameraLocation" parameter to the camera in the Scene Graph.

4) Use frame padding to set the directory of an image sequence to the "imagePath" parameter. (e.g. C:/my/directory/image.####.jpg)

5) Open the Legacy Viewer tab
Result: The image plane is not visible in the Legacy Viewer

Note: When changing the value of the frame parameter, there is no image sequence to iterate through, which also makes the frame parameter redundant.

Expected behaviour
An image sequence should be imported and displayed as an image plane in the Legacy Viewer. The frame parameter then should select the image from the sequence to be used as the image plane.

Actual behaviour
The image plane is not visible in the Legacy Viewer suggesting that the image sequence was not imported correctly. This makes the frame parameter redundant.

Workaround
Unknown.

Reproduced by support
This bug has been reproduced in:
Katana 3.2v3 - Windows 10 - CentOS 7
Katana 3.2v1 - Windows 10
Katana 3.1v7 - Windows 10
Katana 3.1v1 - Windows 10
Katana 3.0v1 - Windows 10
Katana 2.5v1 - Windows 10 - CentOS 7

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

    We're sorry to hear that

    Please tell us why