Problem summary
When using the Geolib3-MT runtime (or derived runtimes), deleting a child and creating a new one with the same name within a single Op cook call incorrectly retains the deleted child's sibling order.
Customer reported version
Katana 5.0v4
Customer reported platform
RHEL7
Steps to reproduce
1) Open Katana and load the attached scene file
2) Fully expand the scene graph
3) Make sure the render flag is set to the second OpScript node
4) Open the Render Log tab and start a Preview / Live Render
Expected behaviour
The Renderlog prints the output as StringAttribute({"primB", "primA", }) which is a result of the OpScript within the first node.
Actual behaviour
The Renderlog prints the output as StringAttribute({"primA", "primB", }) which is the state before the OpScript within the first node has run.
Workaround
Unknown.
Reproduced by support
This bug has been reproduced in:
Katana 5.0v4 - Windows 10, CentOS 7
Katana 3.5v1 - Windows 10, CentOS 7
Unable to reproduce bug in:
Katana 3.2v6 - Windows 10
Earliest version tested
Katana 3.5v1 - The Geolib3-MT feature did not exist before this version.