Mutable RemoveMesh node with data from DataTable

Hi,

We are trying to use Mutable plugin to avoid clipping using the RemoveMeshNode with data from DataTables.

However we are having trouble with the most basic example of our idea.

We have a DataTable (CustomizableObjectConfigTable) based on a struct (CustomizableObjectConfigStruct) with two variables:

1) SoftObjectPointer SkeletalMesh called BaseMesh.

2) SoftObjectPointer SkeletalMesh called RemoveMesh.

The table has two rows and each row contains the same value for both the BaseMesh and RemoveMesh fields, like this:

Row 1 BaseMesh: Mesh_1 RemoveMesh: Mesh_1

Row 2 BaseMesh: Mesh_2 RemoveMesh: Mesh_2

Then, in our customizable object (Test_CO):

1) We use a table node with the aforementioned DataTable to create a MeshSection and the BaseMeshComponent for the BaseObject using the BaseMesh pin from the table node.

2) We use another table node with the same DataTable and connect it to a RemoveMeshNode which we connect to the BaseObject Modifiers.

3) We match RemoveMesh node "Required tags" with the Mesh Section "Enable Tags".

[Link Removed]

And this does not work as we would expect.

As for each row we are setting and removing the same mesh we expected to see that the whole BaseMesh is removed by selecting either of the two rows, but this is not the case.

If the first row is selected (more precisely, the first parameter available) it works properly and in the preview nothing is visible, but if the second row is selected the BaseMesh of that row is shown, no mesh removal is performed.

With both the debugger tool and debugging the code we can see that when compiling the CustomizableObject a mesh without indices and vertices is created for the RemoveMesh operation with the malfunctioning row.

[Link Removed]

Furthermore, if we try instead to connect directly the BaseMesh pin to the RemoveMesh node, the problem is exactly the same.

[Link Removed]

We are surprised by this behavior, as reading the documentation we wouldn't have expected this outcome. We would appreciate some help with the issue or guidance as to how to set up the solution properly.

The whole idea is to have a table with different base meshes each one with their n RemoveMesh meshes and through an enum parameter based on the type of an equipment selected use the proper RemoveMesh for the selected BaseMesh.

Steps to Reproduce

1) Open Test_CO located in Mutable folder.

2) Select Row_01 for MeshData paramenter in Preview Instance tab.

3) See that using this Row_01 the whole BaseMesh has been removed and nothing appears in the preview viewport.

4) Select Row_02 for MeshData paramenter in Preview Instance tab.

5) See that using this Row_02 the whole BaseMesh appears in the preview viewport, no mesh removal happened.