ID 334303 - No Live Render update when adding Prune or Isolate node immediately before Render node in the node graph

Follow
  1. The Foundry SANDBOX
  2. Bug Tracker
  3. Katana

Problem summary
When a Live Render is started from a Render node a Prune node is added into the node graph immediately upstream of that Render node, no update is sent to the Live Render. This is not the case if the Live Render is started from any other node type, e.g. RenderSettings.

Customer reported version
Katana 2.6v4 and 3.0v1.010001a

Customer reported platform
Linux

Steps to reproduce

  1. Create a CameraCreate node and a PrimitiveCreate node and connect them both to a Merge node.

  2. Add a Render node downstream of the Render node.

  3. Include all locations in the Live Render Updates Working Set.

  4. Start a Live Render from the Render node.

  5. Open a Live Render Monitor tab (note: this is a Foundry internal tab).

  6. Add a Prune node between the Merge node and the Render node and set its CEL statement to match the primitive location.

  7. Result: No Live Render update appears in the Live Render Monitor tab.

  8. Disable the Prune node.

  9. Add another Prune node between the PrimitiveCreate and the Merge node and set its CEL statement to match the primitive location.

  10. Result: Live Render updates appear in the Live Render Monitor tab.

Workaround
Insert the Prune or Isolate node above another type of node instead of directly upstream of the Render node.

Reproduced by support
Katana 2.6v4 - Windows 7 - CentOS 7
Katana 3.0v1.01005a - Windows 7 - CentOS 7

Unable to reproduce bug in:
Katana 2.6v1
Katana 2.6v2
Katana 2.6v3
Katana 2.5v7

Earliest version tested
Katana 2.6v3 - This issue no longer appears in this version and has regressed

Expected behaviour
An update about the deleted locations should be sent to the Live Render.

Actual behaviour
No updates are sent.

    We're sorry to hear that

    Please tell us why