ID 235326 - Live Render updates are cooked using a node graph evaluated with the default 'maxTimeSamples' of 1

Problem summary:

All Live Render updates are the result of cooking an Op graph derived from the current node graph evaluated without incorporating the render settings time sampling information.  Any attributes that are dependent on this information, such as those driven by parameters animated in Katana, will be incorrect.  Typically this results in updates for multisampled attributes being sent with only a single time sample.

Steps to reproduce:

1. Use the attached reproduction project, or create one containing a CameraCreate node with an animated transform, some geo, and a RenderSettings node with maxTimeSamples > 1 and shutterClose > 0.0.  The attached repro case uses the Arnold renderer.
2. Ensure the Viewer is not looking through the camera (the Viewer can introduce other multisampling related issues).
3. Trigger a Live Render from the RenderSettings node.
4. If necessary, alter the camera transform using the Parameters tab.

Expected behaviour:

Motion blur due to camera movement is maintained.

Actual behaviour:

Motion blur disappears - the image is rendered with a static camera.

Workaround:

No known workaround.

Reproduced versions/platforms:

• 1.6v3
• 2.5v3

This has almost certainly never worked.

Customer version/platform:

Not supplied.