The material of the cube is translucent and I am not sure it should be.
if you switch it to opaque you do not have that effect.
If you import the file in UE 5.1 and 5.2 you do not have that issue (the material is opaque there). If you want to try, note that starting 5.1 glTF should be imported directly with engine and you should not use the datasmith import button.
Also, if you created yourself the glb file in a third party tool (blender or else) I would recommend to merge all the leaves and stems of the middle ivy (like it is done for the other ones) as it is creating many assets and actors in UE and that is not optimal.
I think there are some extension to support mesh instancing but UE does not support them yet.
The reason I use UE 5.0.3 and DataSmith:
For now I’m using UE 5.0.3 because in 5.1 my Revit models won’t update without crashing. Haven’t tested this yet with 5.2.
And DataSmith imports my models organized in Sub-folders.
I highly recommend you move to “Interchange” (default import into UE) when you will use 5.1 and 5.2 as we are putting all the new glTF import features there and not touching Datasmith glTF anymore.
But I can show you how to make a small blueprint that allows you to add some extra steps to your import pipeline so that you get your assets in different sub-folders when you import with Interchange.
So the Datasmith glTF importer will eventually be discontinued?
What about the default DataSmith workflow (like between Revit and UE)?
Is DataSmith import still the recommended workflow, or will the “Interchange” importer replace DataSmith from 5.1 onward?
This would be appreciated, would very much like to know how to do this.
Datasmith for gltf/glb file is going under interchange in 5.1.
Datasmith functions to import udatasmith file will stay. Same for direct link. So keep using your usual pipeline for now.
Those translation and functions will be integrated in some “interchange datasmith” in the medium term.